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
Binary sensor in ONVIF integration not available after last update with Bosch FLEXIDOME IP turret 3000i IR #91089
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 |
Please post debug logs using the troubleshooting steps here https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics |
@bdraco I hope i did everything right... config_entry-onvif-1b56b8f1e3dba44312f93d9deec90f3b.json.txt |
|
It looks like the camera is sending an invalid time stamp which is tripping up the XML parser |
Ok, thanks, what can I do? I did various tests such as disabling and changing the NTP invert month and day I also updated the camera to the latest firmware but the problem remains... |
The expected datetime format is It looks like your camera sends the datetime as There is a This is likely a bug in the firmware of the camera. |
I opened a PR to zeep to handle this mvantellingen/python-zeep#1370 I have other PRs waiting so it might be a few months before they merge the workaround. |
I'd try to get the camera vendor to fix their firmware in the meantime |
Please try 2023.4.5 #91485 will add support for webhooks which might work around this problem if 2023.4.5 doesn't fix it |
Hi, sorry but I can only answer now, thanks for all the support and interest you are giving me, anyway even after the last update 2023.4.5 the entities still doesn't work... |
Tried but the problem remains :( |
I think we are going to have to wait for the vendor to fix the firmware or mvantellingen/python-zeep#1370 to merge and release the workaround |
I think the vendor's firmware is ok from a certain point of view because everything worked until a month ago, I ran an update after finding the problem... hopefully the next updates will fix something, thanks again |
Can you downgrade the firmware to the previous version? |
i’ve just do the downgrade, it works… |
This version should work better with cameras with broken timezone handling. |
upgraded to 2023.4.6 and the problem reoccurred, performed the above but the problem remains... |
I'm not having any luck figuring out a solution here as the zeep logging doesn't give another trace data. I ended up ordered the camera to see if I can come up with a workaround |
Ok, thank you! |
There are some more fixes in 2023.5.x from other camera I received over the last few weeks. That might help, but if not the debug logs should give a lot more information |
Hi, I tried update 2023.5.0 The problem apparently seemed solved because it sees the "digital input" entity (the entity that interests me the most) but in reality it doesn't read it correctly, because it doesn't see the change from on to off In addition to this, it asked to reconfigure my 2 Hikvision ipcams, I re-enter th Back to 2023.3.5 and all back to work Attached are the debugs config_entry-onvif-1b56b8f1e3dba44312f93d9deec90f3b.json.txt |
It looks like you still have the custom version in there
Can you try taking it out and try again? |
Ok, how do I get it off like you say? However, I tried again to delete the bosch camera and reintegrate it, the entities disappear as in previous updates regarding hikvision continues authentication error |
First observation when testing the 2023.3.5 package with that system:
|
Some AXIS and Bosch (#91089) cameras report they do not support PullPoint but they really do. The only way to know is try.
It works as expected with the 2023.3.5 code running on top of 2023.7.1. The renew gets rejected with the new code which explains why the updates stop flowing but I haven't figured out why yet. It might be the WSAs |
#96377 gets pull point going for the camera, but it ends up in a failed state. Working though that problem now
|
The camera rejects the request with a 401 with the newer code |
Here is the old code
No 401 |
It looks like the WSA are being duplicated !
|
I was really hoping it would fail with one of my local cameras but I can't get it to fail even with the duplication
|
|
|
I copied the WsAddressingPlugin from zeep and modified it to not add the WSAs if they are already present and called it WsAddressingIfMissingPlugin home-assistant/core#91089
I had to make a new WSA plugin to workaround the problem. The lib bump in #96560 fixes this. I added a workaround for the non-compliant time stamps in a previous version https://github.com/hunterjm/python-onvif-zeep-async/blob/async/onvif/types.py#L8 With both of those changes webhooks also work as well I verified it on test test system you provided. thanks for that. |
Leaving open until #96377 merges |
Hi @bdraco sorry for the delay but complex week at work. Perfect, thanks a lot for the support! Forgive my ignorance but so to make it work in my personal system am I waiting for the 2023.7.3 update or do I have to install something in particular? |
You can wait for 2023.7.3 or install https://github.com/bdraco/onvif as a custom component |
Ok, being quite busy with work these weeks, think at this point of waiting for the 2023.7.3 version. Do you still need the equipment under test or can I remove everything? Thank you! |
Let's keep it up until you confirm it's fixed on your production. With onvif it's always good to be extras sure since the potential combinations are nearly infinite |
Just update to 2023.7.3 It works very well! |
Awesome. Thanks for confirming and the test system 👍 |
The problem
Hi after the last update 2023.4, the binary sensors that are part of the ONVIF integration of my IP cams (Bosch) are no longer available (digital input, really triggered, motion detection)
What version of Home Assistant Core has the issue?
core-2023.4.1
What 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
https://www.home-assistant.io/integrations/onvif/
Diagnostics information
config_entry-onvif-1b56b8f1e3dba44312f93d9deec90f3b.json.txt
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: