core: ONVIF integration - Unable to add camera
The problem
After updating too 0.117, within ONVIF integration occur an error, so my existing 2nd camera could not be included again. I tried to delete the entity and start automatic inegration again, but the error message will always be:
Logger: homeassistant.components.onvif Source: components/onvif/device.py:121 Integration: ONVIF (documentation, issues) First occurred: 8:16:19 (11 occurrences) Last logged: 8:26:35
Couldn’t connect to camera ‘IPCAM’, but will retry later. Error: Unsupported URL protocol ‘urn’
Environment
arch | aarch64 |
---|---|
chassis | embedded |
dev | false |
docker | true |
docker_version | 19.03.11 |
hassio | true |
host_os | HassOS 4.15 |
installation_type | Home Assistant OS |
os_name | Linux |
os_version | 4.19.127-v8 |
python_version | 3.8.6 |
supervisor | 2020.10.0 |
timezone | Europe/Berlin |
version | 0.117.2 |
virtualenv | false |
- Home Assistant Core release with the issue: 0.117
- Last working Home Assistant Core release (if known): 0.116.x
- Operating environment (OS/Container/Supervised/Core): Linux/19.03.11/2020.10.0/4.15
- Integration causing this issue: Couldn’t connect to camera ‘IPCAM’, but will retry later. Error: Unsupported URL protocol ‘urn’
- Link to integration documentation on our website: ----
Problem-relevant configuration.yaml
[...]
:ffmpeg
Traceback/Error logs
Logger: homeassistant.components.onvif
Source: components/onvif/device.py:121
Integration: ONVIF (documentation, issues)
First occurred: 8:16:19 (11 occurrences)
Last logged: 8:26:35
Couldn't connect to camera 'IPCAM', but will retry later. Error: Unsupported URL protocol 'urn'
Additional information
maybe a typo in definition file, e.g urn instead of url
Thanks for your great work !!! Regards, Andreas
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 28 (2 by maintainers)
Fixed for me with the update to 2012.3.2
System Health
I have been looking at the history of this component by copying previous versions as custom components. This allowed me to see that the last working commit was #32675e0 and the component stopped working from the following one, #5a39731.
I hope this will help narrowing down the issue.