-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ONVIF integration problem with Hikvision DS-2CD2432F-I camera - "Failed to set up" #91471
Comments
Hey there @hunterjm, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) onvif documentation |
https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics Please provide diagnostics and logs as requested in the template |
|
So... I push Reload button, then enable debug logs. And wait for error. Logs below
|
It possible this is already going to be fixed by #91473 but we need to wait for 2023.4.5 to see if thats the case |
ONVIF "fails to setup" HikVision DS-7104HQHI-K1 on Home Assistant 2023.4.1. The issue is not always reproducible. For example, the last time I tried to debug the issue, downgrading to 2023.3.6 and upgrading again to 2023.4.1, the cameras started working and I abandoned the investigation. Now I rebooted the system, "fails to setup" returned and Home Assistant, docker or system reboots do not help anymore. Do not see anything suspicions in the logs, attached: |
The server rebooted by itself (the bluetooth adapter is a little bit buggy and causes kernel crashes, probably it is the reason). Now the cameras are recognized again. Logs attached. |
There is currently a problem where we can run the camera out of subscription slots because the subscription is 24 hours and if hass is restarted without removing the subscription you have to power cycle the camera to get it working again I'm working on a solution in #91485 but I may not have time to finish it before 2023.5.x |
In my use case both the recorder and hass were power cycled together. Unless hass makes many retries and exhausts the slots this way - I am doubtful that this would explain my problem. |
If you have more information about what you think the source of the issue is, please share. |
Except the logs above - sorry, I do not have additional information. Will watch the behaviour |
Please try 2023.4.5 |
Works so far, thank you very much |
The latest update broke ONVIF for me too. It basically fails to initialize and just keeps on retrying. This is annoying since the initialization turns the torch light on the cameras. Had to remove the integration for the time being. |
Please post the version you are using. Latest is not helpful. |
2023.4.5 |
Thanks. Please post logs |
Logger: homeassistant.config_entries Config entry 'Garden camera - 00:12:42:4B:8A:8D' for onvif integration not ready yet: Could not connect to camera 192.168.0.42:8899: All connection attempts failed; Retrying in background I had those cameras for a year connected. After update to 2023.4.5 they broke. Basically looped initialization. So i had to remove the entities. This is what I get when i add them back via the UI. Cameras have static local IPs and show the rtsp stream when viewed through camera entity. So nothing changed about my setup, which had been working for over a year. |
https://www.home-assistant.io/docs/configuration/troubleshooting/ Please follow the steps to get the debug logs |
Here is the log: Interesting observation - it looks like the cameras which can update time from the network still do work, for some reason only 2 of my 6 cameras can update the time, others return "invalid tz" error and they also broke with 2023.4.5. |
This version should work better for cameras that have broken timezone handling
#91661 (comment)
… On Apr 20, 2023, at 8:16 PM, Alexey Kardashevskiy ***@***.***> wrote:
Here is the log:
home-assistant_onvif_2023-04-21T06-14-28.043Z.log <https://github.com/home-assistant/core/files/11292770/home-assistant_onvif_2023-04-21T06-14-28.043Z.log>
2023.4.3 does not this problem (but I cannot downgrade as a bunch of interface items dissappear here and there)
—
Reply to this email directly, view it on GitHub <#91471 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFB7CGGW43MEX3VRDLBHULXCIQ5BANCNFSM6AAAAAAW7TLUN4>.
You are receiving this because you commented.
|
This version should work better with cameras with broken timezone handling. |
It does work indeed, thanks! Should I keep onvif in custom components or a future upgrade will pick it up? |
while on the topic, is there any workaround to try with these cameras about the clock? for example the timezone on a server (my ntp is proxied by dnsmasq, the cameras are not allowed to the internet) or in the camera (the android app does not allow changing that and I do not have old windows) or something? It is Hikvision. |
changes pushed to the custom component as well last commit is
|
The problem
When I update HA to last version my Hikvision camera DS-2CD2432F-I has stopped to work with ONVIF integration.
Camera integration has state "Failed to set up". No errors or warnings in logs. Other cameras HickView DS-I400 working normally, except this one. Moreover, the mac-address of the camera HA recognizes normally.
HA reboot doesn't help. Reloading the integration - too. HA waits a very long time and then writes "Failed to set up".
The camera itself is available both directly through its web interface and through the NVR-interface. The camera has not been updated or reconfigured.
What version of Home Assistant Core has the issue?
2023.4.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
ONVIF
Link to integration documentation on our website
https://www.home-assistant.io/integrations/onvif/
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
The text was updated successfully, but these errors were encountered: