You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2022. It is now read-only.
It would be nice if we could mimic the behaviour of the Auto-Assist feature for "openWindowDetection"
Expose switch for the Open Window Thermostat Feature using 2 modes (enabled, disabled) and 2 states (on, off)
If Zone contains the "openWindowDetected" flag, then expose its status to the already exposed Window Sensor and set the switch ENABLED in state OFF (maybe before check status returned by API call)
Now the user can activate the switch manually or via automation (preferably; based on sensor state) to state ON
Trigger API Call "Activate OpenWindow"
Now tado's setting for the Zone's Shutoff duration starts to be counted down (1-3600 secs, depending on the Setting in tado's App)
Poll if any change from App / WebApp / (Auto-Assist) was done - just for being safe
After the count down has finished the thermostat is set to normal mode OR...
The user deactivates the switch manually / via automation to state OFF
Trigger API call "Deactivate OpenWindow"
Switch is disabled
Thank you,
Joachim
The text was updated successfully, but these errors were encountered:
I guess it's almost what you can see in my PR #34. The difference is that I do not bother with the Tado detection but much rather rely on one or more sensors. Since the behaviour cannot be mimicked with one switch since that would not allow having two or more sensors (doors and windows) controlling the thermostat since closing one of two open windows would re-activate the heating although the other window is still open. I am not sure if my PR covers your use-case 100% but I am sure that we can accomplish this.
Hi Lukas,
It would be nice if we could mimic the behaviour of the Auto-Assist feature for "openWindowDetection"
Thank you,
Joachim
The text was updated successfully, but these errors were encountered: