home-assistant[bot]
commented
1 week ago Hey there @hunterjm, mind taking a look at this issue as it has been labeled with an integration (onvif) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `onvif` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign onvif` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
onvif documentation onvif source (message by IssueLinks)
The problem
Two tplink cameras, model TL-IPC633P-A4 V4.0, TL-IPC43AN-4 V6.0. Both of then have same onvif protocol v2.01 ipc43an can be configured via onvif UI integration, but the other just shows unknown error, tested with port 80 and 2020, same error Both cameras work well in ODM, attach related screenshot for ref
What version of Home Assistant Core has the issue?
System Information version | core-2024.7.1 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.54-haos arch | x86_64 timezone | Asia/Shanghai config_dir | /config
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1528 Downloaded Repositories | 21Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 13.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.11.2 agent_version | 1.6.0 docker_version | 27.2.0 disk_total | 468.7 GB disk_used | 111.7 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (19.0.0), ESPHome (2024.4.2), File editor (5.8.0), Frigate (0.13.2), Grafana (10.0.0), Jellyfin Server (1.4.0), MariaDB (2.7.1), Mosquitto broker (6.4.0), NGINX Home Assistant SSL proxy (3.11.0), Node-RED (16.0.2), Plex Media Server (3.6.0), Samba share (12.3.2), Traccar (0.23.1), Zigbee2MQTT (1.34.0-1), chrony (4.0.1), go2rtc (1.9.4), TeslaMate (1.3.0)Dashboards
dashboards | 3 -- | -- resources | 8 views | 19 mode | storageRecorder
oldest_recorder_run | October 8, 2024 at 07:17 -- | -- current_recorder_run | November 9, 2024 at 10:25 estimated_db_size | 2771.73 MiB database_engine | mysql database_version | 10.11.6Xiaomi Miot Auto
component_version | 0.7.22 -- | -- can_reach_server | ok can_reach_spec | ok logged_accounts | 1 total_devices | 161What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
onvif
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response