[FEAT] Configurable Device Tracker Reset Duration
joeblack2k opened this issue · 4 comments
Feature Request: Configurable Device Tracker Reset Duration
Problem:
Currently, the device tracker in Double Take sets the "home" state for 30 minutes before changing back to "away." While this default behavior works for many scenarios, there are cases, such as a doorbell application, where users often return within a shorter timeframe, making the 30-minute duration less suitable.
Solution:
I propose adding a configuration option in Double Take that allows users to set a custom duration for the device tracker to reset its state. Specifically, it would be beneficial to have the ability to configure the duration after which the device tracker state transitions from "home" to "away" after the last facial recognition detection. For example, having an option to set the reset duration to 10 seconds or any other desired timeframe would greatly enhance the software's flexibility and adaptability to various use cases.
Additional Context:
In my specific use case, the doorbell application, users typically return within a minute. To address this, I have implemented a workaround in Home Assistant by setting the MQTT topic homeassistant/sensor/double-take/joeblack2k/ "camera" state to "none" after 10 seconds when there are no new detections.
However, having this functionality integrated (setting camera to none in x seconds/minutes preferably configurable) into Double Take itself would streamline the process and make the user experience more intuitive and efficient. (included screenshot)
Thank you for considering this feature request. I believe this customization option would significantly improve the usability of Double Take for users with specific use cases like mine.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.