Skip to content
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

c320ws motion detection works after restart but stops getting events after 12-24h #332

Closed
allankosowan opened this issue May 5, 2023 · 5 comments · Fixed by #334
Closed

Comments

@allankosowan
Copy link

Description

I was previously having trouble with the camera detecting motion events since maybe March. I believe it was the onvif subscription existing bug. No amount of restarts of camera nor HA would resolve it. But I upgraded to tapo integration 5.1.2 and motion detection worked again.

But I have a new issue. The camera does work for 12-24 hours with motion events triggering recordings via automations, but then stops triggering events.

Reproduction Steps

  1. Restat HA
    2.observe motion detection events for several hours while also receiving phone notifications from tapo app
  2. After a while. Detection events stop being recognized while tapo app continues receiving them.

Expected behavior

Detection events should continue to be received in HA.

If applicable, add error logs.

No related logs. I enabled tapo integration debug logs and will add if anything shows up.

Device Firmware

1.3.0

Using stream component

Yes

Does camera work via official integrations?

Yes

Camera has all attributes filled out in developer tools

Yes

HASS Environment

windows VM running HAOS

Search for similar issues

Yes

Additional information

No response

@JurajNyiri
Copy link
Owner

Specify firmware, integration version and Home Assistant version please.

@JurajNyiri
Copy link
Owner

JurajNyiri commented May 5, 2023

Issue is in core/onvif, might be fixed by #333 .

@allankosowan
Copy link
Author

Specify firmware, integration version and Home Assistant version please.

Firmware 1.3.1
Tapo integration 5.1.2
HA 2023.4.6
Supervisor 2023.04.1
Operating System 10.1
Frontend 20230411.1 - latest

@JurajNyiri JurajNyiri mentioned this issue May 5, 2023
@JurajNyiri
Copy link
Owner

Issue has now been fixed in 5.2.0.

@allankosowan
Copy link
Author

So far so good. Using version 5.2.1 and it survived overnight without dropping motion events. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants