-
-
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 (motion) events not working with Dahua DH-SD22404T-GN-W and anpviz #37545
Comments
onvif documentation |
I'm having the same issue, my cameras are displaying the same sensors. When checking in onvif device manager I clearly see the motion alarms firing. |
I have this issue with the reolink 243-5MP also. I see the events appear in "OVNIF Device Manager." They show up as the |
Same issue here with an ONVIF Profile S camera (Imou/Dahua LOOC IPC-C26E). Entities are created, but no state update of the various entities. |
I see the events in ODM after setting ODM to pullpoint only after restarting ODM (to be sure it is using pullpoint). I don't see the event in home assistant onvif integration. Camera is Dahua IPC-HDW5231R-ZE. Happy to do further debuging, testing, etc |
I have the same problem: ONVIF camera integration with LOOC IMOU camera seems to be okay but sensors never update in Home Asistant
|
since upgrading to 115.2 (was on 114.4 iirc) events are now working. Not precluding intermediary releases, but this is now fixed for me. |
I can confirm the above. I'm now on 0.115.3 and events, like motion sensor, are now working for my ONVIF camera. @UmbraMalison, @loeffen As we have basically the same camera, do you have a sound/noise sensor listed as event? I know this camera is capable of detecting audio, but it seems it is not passed through ONVIF. |
yes, have you enabled audio in the web interface of the camera? |
Ah, thanks! I see you camera is actually a different model, my bad. But it is good to see that such option is passed through ONVIF. I will investigate further, thanks! |
yeah, maybe a reboot might do it. there's some process that the onvif integration goes through to scan the events available to it, I don't know when that happens (but likely on startup, or on creation of the integration). potentially if your camera isn't providing an event at the time of "scanning/probing" then it wouldn't have been seen by the integration. i'm 100% speculating. I have seen though that my other identical camera does not have field detection, as I have not enabled IVS intrusion, and i've also seen that IVS tripwire doesn't trigger in the onvif integration - only IVS intrusion. So potentially on the sound events, i'm only seeing either Input Abnormal event or Intensity Change event. or maybe both! |
Dahua firmware doesn’t send an initialization event for sound or any of the IVS features. Go walk in front of your camera and make noise, then go back to HA and the sensors will be there. |
Same issue here, any news?
|
Same problem:
SOAP-ENV:Bodytev:PullMessagesResponsetev:CurrentTime2020-12-19T22:26:38Z</tev:CurrentTime>tev:TerminationTime2020-12-20T20:24:57Z</tev:TerminationTime>wsnt:NotificationMessagewsnt:SubscriptionReferencewsa5:Address</wsa5:Address></wsnt:SubscriptionReference><wsnt:Topic Dialect="http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet">tns1:VideoSource/MotionAlarm</wsnt:Topic>wsnt:ProducerReferencewsa5:Address10.0.10.31/onvif/event/alarm</wsa5:Address></wsnt:ProducerReference>wsnt:Message<tt:Message PropertyOperation="Changed" UtcTime="2020-12-19T22:26:37Z">tt:Source<tt:SimpleItem Value="00200" Name="VideoSourceConfigurationToken"></tt:SimpleItem><tt:SimpleItem Value="0" Name="DetectWindow"></tt:SimpleItem></tt:Source>tt:Data<tt:SimpleItem Value="1" Name="State"></tt:SimpleItem></tt:Data></tt:Message></wsnt:Message></wsnt:NotificationMessage></tev:PullMessagesResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>'
System is running on VM: Supervisor: Version 2020.12.7 |
........................................ tt:Data <tt:SimpleItem Value="1" Name="State"></tt:SimpleItem></tt:Data> .......................................
try:
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Same issue here but with HA core 2021.6.6. Thanks |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Same issue for ANPVIZ_IPC-0350 |
Same issue for P3SB-8MP-EU |
UNV Camera. Такая же беда. |
Same issue with Milesight cameras MS-C5375-PB, MS-C5383-PB e MS-C5375-EPB. Works with Safire SF-IPB025WA-4E |
Has anyone fix it? |
Please give it another try after 2023.4.5 is released. It should work with a few more cameras. It will not fix all of them though as each one has to be examined separately as not every vendor implements the onvif standard in the same way. |
Hi @bdraco, even after the update the sensors remain "unavailable" :-( `
|
There are at least 3 problems going on here
If you fall in 1 and need a custom rule you'll see Open a feature request at https://community.home-assistant.io/c/feature-requests/13 You'll need to post the following:
If you leave out any data we likely will not be able to add support for that camera. |
Hi, in the debug logs I don't find |
It might be case number 3 and the camera doesn't send events via pull point. I have a few of them that have never worked until #91485 |
If I can help for some tests let me know, thanks |
If you can test #91485 that would be awesome |
@bdraco sure, but please tell me what I have to do :-) |
This comment was marked as outdated.
This comment was marked as outdated.
I put the changes up at https://github.com/bdraco/onvif
Restart |
I'll try tomorrow, It's too late now in Italy😅, tks Hi @bdraco, I installed your component "https://github.com/bdraco/onvif" , the motion sensors are back available and it seems that work correctly even if with same false alarms for the external cameras. |
It looks like the problem is that if the device management services gets WSA it times out on these cameras. |
I don't think its the WSAs |
I opened #91866 to guard a few more places to retry when it does timeout |
#91866 will fix a few of the cameras here but I have no way of knowing which ones. If there is still a problem in 2023.5.x, please open a new fresh issue with ONE camera per issue with the name and model of the camera in the report so we don't end up closing it prematurely when we fix one. It would also be helpful to include a link to purchase the camera Make sure to include debug logs and diagnostics for the camera https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics |
The problem
ONVIF integration does not receive events from my onvif camera.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
Onvif manager is receiving motion detection and alarm events from my camera but binary sensors created in home assistant do not change state. In debug logging I also see no trace of the events:
reboot event is also not coming in.
The text was updated successfully, but these errors were encountered: