ONVIF Motion Events broken

[ricarva]

The problem

Motion Events for ONVIF cameras were working correctly in my setup (Reolink cameras) on HA 117.1, but the update to 117.2 broke this functionality: the motion sensor has since become "Unavailable".

Environment

• Home Assistant Core release with the issue: 117.2
• Last working Home Assistant Core release (if known): 117.1
• Operating environment (OS/Container/Supervised/Core): Home Assistant OS
• Integration causing this issue: ONVIF
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/onvif/

Problem-relevant configuration.yaml

Configured through UI, no YAML.

Traceback/Error logs

No relevant log entries.

Additional information

Should be connected to commit #42651

[probot-home-assistant]

Hey there @hunterjm, mind taking a look at this issue as its been labeled with an integration (onvif) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[hunterjm]

This is a known regression from 0.117.0 to 0.117.2 in order to fix a memory issue. I’m looking into restoring the functionality in 0.118.

[ricarva]

@hunterjm, hi. Any ETA on the fix for this? I'm asking since it did not drop with 0.118. Thanks in advance.

[hunterjm]

@ricarva - I didn't get around to re-enabling in time for 0.118. Still looking into it.

[ricarva]

@hunterjm thanks for the update, Jason!

[gomble]

hello will this be fixed in further updates?

[ricarva]

@hunterjm Jason, Happy New Year!

Any progress on this issue? Thanks!

[timdonovanuk]

Also: #42784, #37545, #36145

As a workaround, you can bypass the broken ONVIF motion sensor integration and use a manual REST integration to pull the camera motion state. On my camera (C1-Pro) the state is at: http://192.168.1.5/api.cgi?cmd=GetMdState&user=admin&password=password

So a rest sensor, something like this should work:

binary_sensor:
  - platform: rest
    resource: http://192.168.1.5/api.cgi?cmd=GetMdState&user=admin&password=<password>
    name: Camera Motion Sensor Occupancy
    scan_interval: 5
    value_template: "{{ value_json[0].value.state }}"
    device_class: motion

[catalin2009]

        I found a solution  (possible bug) for this in the file parser.py from onvif integration.
          This could be a solution also for  #37545, #37878, #42784, #36757, #36145


             My NVR ONVIF reports data movement event state like this: (see my previous message from Dec 20, 2020 on #37545):

........................................
tt:Data <tt:SimpleItem Value="1" Name="State"></tt:SimpleItem></tt:Data>
.......................................

         In Onvif integration from https://github.com/home-assistant/core/tree/dev/homeassistant/components/onvif
         The file parser.py compares onvif event data state with a value equal to "true":

---

try:
source = msg.Message.value_1.Source.SimpleItem[0].Value
return Event(
f"{uid}{msg.Topic.value_1}{source}",
f"{source} Motion Alarm",
"binary_sensor",
"motion",
None,
msg.Message._value_1.Data.SimpleItem[0].Value == "true"

             As my NVR reports "1" for movement, I simply replaced value "true" with "1" , like this: 

---

try:
source = msg.Message.value_1.Source.SimpleItem[0].Value
return Event(
f"{uid}{msg.Topic.value_1}{source}",
f"{source} Motion Alarm",
"binary_sensor",
"motion",
None,
msg.Message._value_1.Data.SimpleItem[0].Value == "1"

       To modify parser.py I installed ONVIF as custom_component by creating custom_components folder in config folder 
       and by copying there the onvif folder from github. I modified parser.py in this folder. So onvif now works from 
       custom_components, not from original integration.

       Now the events work.
        I hope this helps somebody.

[github-actions]

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.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mathmaniac43]

I am on HA version 2021.5.2 and this is still not working. Please do not close the issue.

[gomble]

Its not working with 2021.5.3, Dont close the issue

[simonyel]

Still not working in 2021.7.4

[github-actions]

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.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.