-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[tado] openWindowDetected not available in API response #17558
Comments
Ok. I will have a look at it. |
@eengnr thank you for posting your JSON results.
Hmm. The tado API supports two different JSON properties -- namely
On my system, when the window is opened, the First, for general understanding: what devices do you have? In my understanding However we may perhaps debate whether we should (also) add a separate channel for the "open window heating/cooling override activated" function, which might depend on the
|
Ok, this is interesting, thanks for checking it! I have the V3 bridge with the "included" subscription, i.e. my thermostats turn off when the open window is detected. A seperate channel with this information would be nice as well! And I think it's enough to either have it as ON/OFF or to have the expiry time in case it is set. |
Probably the channel should supply a numerical duration in seconds (quantity type). The user can link either/both Number:Time resp. Switch items to that channel; and OH will automagically display zero seconds as |
Hi, I recently added an item to the "Open Window" channel in the tado° binding. But it keeps staying "OFF".
I checked the API response via the webapp/curl and it seems that the
openWindowDetected
property does not exist (anymore?). Only theopenWindow
is there.This is the API response for
.../zones/[id]/state
when an open window is detected:And this if no open window is detected:
Only
openWindow
is available in both cases.Environment
Perhaps this needs to be corrected in the binding? Thanks!
The text was updated successfully, but these errors were encountered: