Closed michaeltryl closed 11 months ago
Verify through official HA Onvif integration. If it works there and not here we can reopen this. This integration uses the functionality of official Onvif integration.
it works through Onvif integration
Please provide a screenshot where it is visible that the motion sensor went to off state in onvif integration and did not in this integration at the same time. This integration reuses most of the code inside onvif so I am not sure how that could happen. Cameras are also buggy with onvif reporting, so I am making sure there is an actual bug before we reopen.
This screenshot shows that the tapo integration also does not always register that there is movement, which onvif did
What camera is experiencing this issue?
Please provide screenshot at the same time. This does not prove that there is a bug in this integration, it could be camera issue. We need to see it working in onvif and not working in Tapo at the same time.
these two screenshots were taken very few seconds apart, so it clearly shows that the tapo integration has not detected movement at 14.36.08 just like onvif did. if not, you must tell where you want the screenshot from. but the two I have sent here are taken directly from the history of home assistant.
And it is tapo c310 camera
Are you using HTTPS to access ha / do you have webhooks enabled in configuration of Tapo integration?
i have nabu casa, so yes i think i use https, but not local in my home dont know what webjooks is, so i would say i not use them :-)
Webhooks are explained in FAQ. Please check the configuration to see if the option is turned on or off. Also enable debug logs and post the full log please that will tell me what I need to know about webhooks.
logger:
default: critical
logs:
custom_components.tapo_control: debug
Dont know what is happende, but now it works perfekt again. sorry for this post :-)
Description
When I turn on my camera, the binary_sensor for motion does not always go off. When the camera is switched on and detects movement, it is also not always the case that the sensor goes off again when there is no movement.
Reproduction Steps
none
Expected behavior
The sensor must go off when there is no more movement. It would be nice if it goes off when the camera is switched on or you can turn it off via an automation
If applicable, add error logs.
No response
Device Firmware
1.3.5
Using stream component
Yes
Does camera work via official integrations?
No
Camera has all attributes filled out in developer tools
Yes
HASS Environment
rasberry pi 4
Search for similar issues
Yes
Additional information
dont know if i use Using stream component it does not have an official integration