Open dduff617 opened 5 years ago
I just tried a few repeats of similar experiment with just changing set point by a few degrees (instead of changing to eco mode) and the plugin seemed to detect the change pretty quickly, so I think this suggests the problem is not item 3.
The plugin also detects home vs away very quickly.
I tried putting one of my thermostats in eco mode using the Nest app. Watched in Indigo to see how long it would take the plugin to detect the change. After about ten minutes of waiting, the app had still not detected the change, so I hit "send status request" in the Indigo app a few times. Still after several additional minutes, the plugin had not detected the change (or was not recording it correctly?). the thermostat in Indigo still displayed set points that were in effect before entering ECO mode as being in effect, vs. the Nest app, which showed that set points were actually 50 / 90 degrees-F.
I looked at state info in Indigo to see if there were any other signs that could be interpreted to mean anything like "ECO mode is on". I see ecotemperature{high, low}_{c, f} states, but they all have values of 0.
Sorry this is not the neatest of bug reports, as it possibly implicates multiple different problems - 1. plugin support for eco mode generally. 2. support for thermostat-specific vs. global modes and mode changes. 3. plugin tracking of device state changes generally.