Bug: C310 Motion sensor stops working or becomes unavailable

Describe the bug Motion sensor stops reporting state change after some time. (daily). Stream still works. Sometimes motion sensor in HA reports unavailabe and somtimes it just stays in off state. Motion is still detected on camera and recordings work on Android Tapo app.

Reseting motion detection on camera or rebooting camera does not help. Only HA restart recovers motion detection state change.

I have explicitly opened ports on firewall 2020,554,443,1024 but result is the same.

Log No log entries.

**Camera (please complete the following information):**
C310

**Using stream component**
Yes

**Camera works through onvif component OR different cameras work in general**
Camera and motion detection works in Android Tapo app.

**Camera has all attributes filled out properly in developer tools**
yes

**HASS Environment**
Supervised HA OS (RP 4)

[JurajNyiri]

That confirms my belief that the Home Assistant event manager is not able to recover properly.

logger:
  default: critical
  logs:
    custom_components.tapo_control: debug
    homeassistant.components.onvif: debug

Lets add debug for it and observe how it behaves when it stops working.

This is an example of successful recovery on camera reboot:

2021-04-23 21:40:15 WARNING (MainThread) [homeassistant.components.onvif] Failed to fetch ONVIF PullPoint subscription messages for '28f39a982d2634f6aa21be4917158645_tapo_events': [Errno 61] Connect call failed ('192.168.100.70', 1025)
2021-04-23 21:40:19 DEBUG (MainThread) [custom_components.tapo_control] Finished fetching Tapo resource status data in 68.889 seconds
2021-04-23 21:40:20 DEBUG (MainThread) [homeassistant.components.onvif] Restarted ONVIF PullPoint subscription for '28f39a982d2634f6aa21be4917158645_tapo_events'
2021-04-23 21:40:29 DEBUG (MainThread) [custom_components.tapo_control] async_update_data - entry

Lets see what does it do when it stops receiving events. Once we have that information we can move forward and create a bug report on Home Assistant and/on workaround it via integration somehow.

[rkkoszewski]

I’m having the same issue with a Tapo C110. In my case restarting HA does not solve the issue. It actually shows up after restarting HA. Maybe it stops working earlier, but the sensor shows as “Clear” and after HA restart it shows as “Unavailable”. Any further restarts of HA (Even full OS reboot) have no effect and do not fix the issue. Disabling “Enable motion sensor” and then enabling it again seems to make the motion sensor work again (No HA restart necessary). I’ll try to play with the integration’s Debug options and how OVNIF is working here (Smells to me like a subscription to the motion event expires and is never refreshed, but I haven’t yet looked how the integration works). I’ll report back.