Closed jimmyz5150 closed 4 days ago
JurajNyiri
commented
4 days ago This functionality is controlled via native onvif integration and that is ultimately controlled by the camera. You can create an automation that will set/unset a helper boolean entity that will achieve a longer delays for activity.
Same applies to jpeg still shots - if you want them, make an automation that will take a snapshot and store it in HA.
jimmyz5150
commented
4 days ago Well thanks for the discussion? Native, do you mean having to have Tapo app to do it? Defeats HA On Monday, November 18, 2024 at 10:49:56 AM EST, Juraj Nyíri @.***> wrote:
This functionality is controlled via native onvif integration and that is ultimately controlled by the camera. You can build an automation that will set a helper boolean entity that will achieve a longer delays for activity.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
JurajNyiri
commented
4 days ago There is a discussion on this github if you would like to discuss, or get help creating an automation - https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/discussions
By native onvif integration, I mean https://www.home-assistant.io/integrations/onvif/ . This integration reuses that part of onvif integration to get motion data information. Data that camera reports is reflected inside HA 1:1 and that will not be changed to return incorrect data.
If you would like to do anything more with it, for example, build in a delay, you can very easily do via helper entity and an automation, as previously described.
jimmyz5150
commented
4 days ago Thank you for elaborating on it. Appreciate it On Monday, November 18, 2024 at 12:54:27 PM EST, Juraj Nyíri @.***> wrote:
There is a discussion on this github if you would like to discuss, or get help creating an automation - https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/discussions
By native onvif, I mean https://www.home-assistant.io/integrations/onvif/ . This integration reuses that part to get motion data information. Data that camera reports is reflected inside HA 1:1.
If you would like to do anything more with it, for example, build in a delay, you can very easily do via helper entity and an automation, as previously described.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Is your feature request related to a problem? Please describe. TAPO C310 Motion detection is very short while displaying feed when a card has conditional trigger (dashboard card only visible when triggered) Is it possible to extend motion trigger length when motion is detected. Real example: When motion is activated it will trigger several times during 1 event. Condition card pops for only 3 seconds multiple times.
Describe the solution you'd like Is it possible to create a timed length slider bar entity that gives say 5 sec to 30 sec ( like the Microphone Volume slide entity) to keep feed stream active and alive. Or maybe jpeg still shots?
Describe alternatives you've considered Possibility of a condition template, haven't figured out.