[RELEASE] Universal Ecobee Suite, Version 1.8.01

SmartThings staff surely can’t monitor every single thread for problem reports. They will only respond to emails sent to support@smartthings.com.

I just did a fresh install and still don’t have the option for Auto in automations. I’ll look at live logging again and report back. Below are the settings available on the thermostat. Maybe I am missing something? This is the Ecobee with Alexa Voice.

Here are the logs for the ESM

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:53 PM: trace Updates sent (6 / 1830ms)

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:53 PM: info Polling 521728949298 completed

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:53 PM: info 0 updates for 0 thermostats

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:52 PM: info Requesting ( equipmentStatus settings program events audio runtime extendedRuntime ) for thermostat Ecobee (521728949298) - [false]

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:52 PM: info Polling 521728949298

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:52 PM: trace Checking for updates...

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:23 PM: trace Updates sent (3002 / 3867ms)

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:20 PM: info Polling 521728949298 completed

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:20 PM: info 179 updates for 1 thermostat (Ecobee)

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:20 PM: info Requesting ( equipmentStatus settings program events audio location alerts runtime extendedRuntime weather ) for thermostat Ecobee (521728949298) - [true]

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:20 PM: info Polling 521728949298 (forced)

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:20 PM: trace Checking for updates...

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:14 PM: trace ====> getEcobeeThermostats() entered

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:14 PM: info getZipCode() returning 85209

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:14 PM: trace ====> getEcobeeSensors() entered. thermostats: [9cd6a651-c964-43f5-81fd-8b8b74c49e92.521728949298]

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:14 PM: info Got valid sunrise/set data: [sunrise:Thu Sep 30 13:20:00 UTC 2021, sunset:Fri Oct 01 01:13:00 UTC 2021]

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:15 PM: debug Ecobee Suite Manager, version 1.8.53 on SmartThings - initialization complete

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:15 PM: trace Spawning the poll scheduled event. (thermostats.size(): 1)

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:10 PM: debug getChildDevices(true), children=1

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:21:09 PM: debug getChildDevices(true), children=1

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:20:48 PM: trace No updates

[9cd6a651-c964-43f5-81fd-8b8b74c49e92](https://graph-na04-useast2.api.smartthings.com/ide/logs#9cd6a651-c964-43f5-81fd-8b8b74c49e92) 3:20:48 PM: trace Checking for updates...

Here are the logs for the Ecobee device

6f318dd4-9f83-46c9-ad22-d7de4d1f0bd3 3:25:31 PM: info refresh() - calling pollChildren (forced), deviceId = 521728949298

6f318dd4-9f83-46c9-ad22-d7de4d1f0bd3 3:25:27 PM: trace Ecobee Suite Thermostat, version 1.8.22 on SmartThings updated

I don’t need to see the logs unless there is an Error reported.

Can you see what the current value of the attribute supportedThermostatModes is for your thermostat? It should contain “auto”.

If not, try this:

  • Turn on Live Logging, and watch the ES Thermostat device
  • Turn OFF the Auto Heat/Cool threshold setting at the thermostat
  • Wait for TWO refresh/poll cycles (You’ll see entries that say “Updated X objects (YYms)” for each cycle)
  • check that the attribute autoMode changes to FALSE
  • check that the attribute supportedThermostatModes does NOT include “auto”
  • Turn ON the Auto Heat/Cool threshold setting
  • Wait for TWO more refresh/poll cycles
  • check that the attribute autoMode changes to TRUE
  • check that the attribute supportedThermostatModes now includes “auto”

In the IDE I see supportedThermostatModes twice the second says auto

I am at a loss for why the SmartThings device doesn’t show “Auto” in the list of available Modes. At this point, I suggest opening a ticket with SmartThings support…

That said, if you could send me a screen shot like above, but for the thermostat running the “stock” SmartThings Ecobee device driver, perhaps I’ll see something different. My own SmartThings environment was retired this summer when my hub failed…

I do not see any information for the stock ecobee device in the IDE since it is a placeholder. If someone can tell me where to find it I’d be happy to send it.

At this point all I can do I provide the DTH from github
Stock Ecobee DTH

I did a bit of testing on this, as I am having the same issue.

My Location Mode in ST is changing (i.e to Home or Away) with no problem based on the presence of my device. But, once Away is activated, Ecobee Suite Manager is not changing the thermostat mode to Away. @storageanarchy, I am unsure of how your (awesome) smart app gets notified from a Location Mode change in ST. But, I just wanted to check and see if you are sure this is a ST issue? If you are, is there any information you might be able to give me to relay to the ST Tech Support that could help them understand the issue in a bit more technical detail?

Unfortunately, the first thing that ST Support is going to say is that they don’t support 3rd party Smart Apps, as I have run into this anytime I have had an issue with them. As far as they are concerned the presence and location mode functions are working as they should and they will likely point the finger at the Smart App.


  1. Other users have reported Mode Change issues using standard SmartThings automations
  2. my code has worked fine for more than 4 years - it uses the standard (and ONLY) means of tracking mode changes (it subscribes to the location.mode changes).
  3. the only code that changed recently was the SmartThings hub firmware
  4. the issue has occurred only for users who have recently upgraded their SmartThings firmware.
  5. the SAME EXACT CODE works fine on Hubitat, using the same exact methodology

it is thus highly unlikely my code is the issue.

Thanks for your insights on this. I hope my question wasn’t taken as a question to the integrity of your code, as your Smart App has been rock solid since I started using it a couple years ago. I was merely asking if there was any chance that changes they make to the ST App (with regards to how their app is designed) could possibly require changes on how a Smart App connects to it.

Yup - I understood your question and didn’t take it as a criticism; I merely wanted to give you sufficient context to understand why this is most likely a SmartThings problem.

Like I said, there is only 1 way to get location mode changes, and SmartThings can’t change this unless they want to break EVERY application that uses location.mode. And if SmartThings automations are breaking in addition to Ecobee Suite, the suspect is SmartThings…especially since they have broken this multiple times in the past…

Do you use the Ecobee Suite Manager? If so, what options do you have under automations?

1 Like

I am also suddenly having the same issue with mode changes. I’m using Ecobee Suite on SmartThings but also have Hubitat and they’re connected via HubConnect. I’ve noticed that a location change in ST isn’t always syncing with Hubitat like before so it sounds like something has broken on ST’s end.

Not sure what has happened, but over the past week or so ago this has stopped working for me. I was just using the Mode Change Helper to change the ecobee programs based on location mode. I have since added duplicate devices via the smartthings app and control those in the “automations” section and I can control them just fine. Seems that adding the “supported” devices and then controlling them with the built-in “automations” seems to be the way to go?

Modes should still be working, but I suspect that SmartThings has finally EOL’d the operation of “Routines” - to replace Helpers that used routines, you will indeed need to create some virtual switches, as you describe…