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
Thank you for this great API, it has proven to be very useful. After a couple of weeks a few questions have come up, and I'll put the most pressing ones for me on the top of the list:
How can I detected that the Heat Link has been put into MANUAL mode? Obviously I am in Europe with a 3rd gen thermostat (fw 5.1.5). The Nest web UI displays "MANUAL" and allows to disable it with a click. For those that do not have a heat link: If its button is pressed, then any input from the thermostat will be ignored, and the button is a simple heating on/off switch.
What is the meaning of auto_away == 2? Note that Nest Sense is in my case still in "Learning Mode" for Auto-Away.
When in range mode (although I only have heating and no AC ), there appears to be no way to see the current target temperature in the API. Is that correct? All I see are the standard values for the range, i.e. the auto-away temp and some meaningless upper bound (since I have no AC).
The "last connection" seems to return the last time the API was used, which in my case means it more or less always returns the current time. Not really useful...
I am graphing the data with a 30 minute schedule (using rrdtools), and I see that the Nest temperature readings are reported in 0.5 C intervals only, which is quite a rough scale.
We do have a) device away status (summary of auto-away and manual-away) and b) location away status (set when non of the devices detect activity), correct?
I'd appreciate any comments or pointers - thank you!
The text was updated successfully, but these errors were encountered:
Thank you for this great API, it has proven to be very useful. After a couple of weeks a few questions have come up, and I'll put the most pressing ones for me on the top of the list:
I'd appreciate any comments or pointers - thank you!
The text was updated successfully, but these errors were encountered: