[RELEASE] Ecobee Suite, version 1.9.00

simon4 · December 16, 2025, 1:05pm

I ran into an issue where setmode failed this morning. This then cascaded in a failure to setHeatingSetpoint. I posted details in GitHub:

github.com/SANdood/Ecobee-Suite

No retry or queue mechanism when setMode() fails despite API being connected

opened 12:52PM - 16 Dec 25 UTC

simondsmason

## Issue Description I ran into a weird issue this morning. I came downstairs …and it was cold. My Ecobee was off when it should have been on. When I checked the logs I see that the attempt to change mode to heat failed. Looking at the code I noticed that when `setMode()` fails to change the thermostat mode (e.g., from 'off' to 'heat'), the driver and parent app do not implement any retry mechanism or queue the failed command for later execution. The failure is logged but no corrective action is taken, leaving the thermostat in an incorrect state with no automatic recovery. ## Steps to Reproduce 1. Thermostat is in 'off' mode 2. `setThermostatMode('heat')` is called 3. Parent app's `setMode()` sends API request to Ecobee 4. API request fails (returns non-zero status code, but API connection is still 'full') 5. `setMode()` returns `false` to driver 6. Driver logs error and sets `changed = false` 7. **No retry is attempted** 8. **No queueing occurs** (queueing only happens if API is not fully connected) 9. Calling app/controller receives no indication that the command failed 10. Thermostat remains in incorrect state Options would be to update the driver to include a retry mechanism. And/or add in pushover or something to indicate that the API had not done what it was told to do? Also this brought up a second issue of sending set points out when the system is not in a mode to receive it which I will post separately.

github.com/SANdood/Ecobee-Suite

setHeatingSetpoint fails (or is ignored) when thermostat is in 'off' mode

opened 12:58PM - 16 Dec 25 UTC

simondsmason

Related to the issue where my Ecobee apparently ignored the setThermostatMode co…mmand this brought up a second issue: When the Ecobee thermostat is in 'off' mode, attempting to change to 'heat' mode via `setThermostatMode('heat')` fails silently. The thermostat remains in 'off' mode, and any subsequent setpoint change commands are ignored because Ecobee ignores setpoint changes when the system is in 'off' mode. In theory the system should not be in OFF mode when a set point is changed but that was not the case on my system this morning. ## Steps to Reproduce 1. Thermostat is in 'off' mode 2. Hubitat Thermostat Controller calls `setHeatingSetpoint(71)` 3. Driver calls `setThermostatMode('heat')` 4. Parent app's `setMode()` sends API request to Ecobee 5. API request fails (returns non-zero status code) 6. Thermostat remains in 'off' mode 7. Driver then calls `setHeatingSetpoint(71)` 8. Setpoint change is sent via `updateThermostatSetpoints()` → `parent.setHold()` 9. Ecobee ignores the setpoint change because system is still in 'off' mode Possible solutions - add code in to set point code to check that it is in an acceptable mode? Resolve an issue when it is out of alignment?

I don't know if I have seen this before but it would be good to trap these things and try to resolve as it could mean frozen pipes.