Ecobee built-in integration, my thermostats missing auto and heat

I installed 6 x ecobee light thermostats and all of them are missing auto and heat devices:

supportedThermostatModes : [off, cool]

I've tried manually adding heat by switching to a virtual thermostat and go back to Ecobee, but it did not work and I got something like your thermostat does not have a heat function on debug logs. Same as when I send a heat comment.

Thermostat heats normally, connections are fine, and it is not API as I've additionally tried Ecobee Suite, and all worked fine except CPU load, and that one creates so many tasks and everything slows down and fails with 6 thermostats. So i had to go back to the built-in Ecobee integration, which at least works fine.

Anyone have any idea how to enable auto and heat?

I have 3 different Ecobees and one of them is the v3 Lite and it shows all the correct modes.

Are you getting any errors from the app after authenticating?

Maybe @bobbyD can look at your engineering logs for clues.


I have ecobee v3 light too, all 6 of them. Auth was fluent and everything works well except missing state modes.

I have many of these errors on the logs of the Ecobee Integration app, and I am not sure if they are related:

java.lang.NullPointerException: Cannot invoke method multiply() on null object on line 1052 (method setHold)

One other difference may be that I am not using a furnace, so I am using a cold and heat pump for HVAC air conditioning. So the 0B wire is connected instead of W. I have no idea if Hubitat cares, just a side note, not if it makes a difference. The ecobee hardware itself can switch between heating, auto, and operating modes. It is only Ecobee integration that does not have these modes.

Bumping this thread. Just switched over to Ecobee from Nest, installed Hubitat native Ecobee integration, and I'm only able to select "Off" or "Cool" modes when building a rule (rule is to switch thermostat off if I open any of my windows, back on, or rather to Auto, when I close all windows). Super frustrating.

I know there is a community app called Ecobee Suite Manager. I installed it at one point, realized it provided way more than I needed, and also read several posts indicating it was very resource-intensive, so I uninstalled it. I'm doing very basic stuff - I wish the native integration would provide the functionality I need.

Any thoughts on how to get the full, proper set of modes available in the device? I have uninstalled/re-installed the integration & device several times - always the same result.

There is the problem though. Most of the time the built in integrations are rather generic with functionality and don't go well beyond what is needed for the device to work. Ecobee Suite is a fantastic integration and generally not to bad on hub resources if you run it with the right setup. Mainly set the polling to every min. It seems counter intuitive, but it keeps the number of changes per poll to a minimum. Think of it like trying to create a flat line for the load caused by it vs very spiky load with allot work occasionally.

That said i do wish there was a Ecobee Suite Lite that got rid of allot of the extra fluff, but who determines what that is.

I have used Ecobee Suite for years. Though comparatively it does create more load, so do all other Lan integrations. Set it to every min and see how it works for you. Also though the app/device stat pages provide some idea of load, they aren't really 100% accurate so they may make Ecobee suite look worse then it actually is.

Thanks for the feedback. So, now for a dumb question...

I couldn't figure out when I installed the Ecobee Suite Manager app how to actually add my thermostat device. After installation, it didn't show up in my apps, so I couldn't figure out how to create a thermostat device. Does the Ecobee Suite Manager need to be installed ON TOP OF the native integration, meaning do I need to have the native integration to create a Thermostat device, and then utilize the added capabilities of Ecobee Suite Manager? Or have I missed something?

If you haven't already make sure you have HPM to manage ding the initial install of the code for community integrations and Smart Apps. It just installs the app though. Then you need to go click on the "Apps" option in the UI on the left and then click on the "+ Add User App" button in the upper right. Then you should be able to install and complete the setup of Ecobee Suite Smartapp.

You do not need both. When you setup Ecobee suite you should have to go through a process of authenticating to the Ecobee Cloud. When you do that it should create your thermostat and additional sensors if you have any. One thing you may want to do is there is a option to enable the core thermostat as a sensor as well since Ecobee reports a average and a actual thermostat temp. That would be a additional step.

Seting up those items would be in the location shown below in Ecobee Suite. Not much there, but that is how you setup your sensor devices in Hubitat after getting the integration online.

Thank you! I knew I was missing a step ("Add User App"). All good now. Appreciate the quick response.

Just installed the Ecobee Suite Manager and very glad I did. Didn't realize it had all those pre-built "helper" apps - I've used several of them to replace what would have been rules I would have had to write. Made things very simple, so definitely worth the extra resource utilization IMO.

Only missing helper app is a location trigger for the thermostat utilizing the Hubitat app geofence (although I've read it's not 100% reliable - I guess I'll find out). Still had to write those arrive/leave rules myself. The Ecobee Thermostat (& sensor) occupancy sensing has always bothered me - it doesn't really register "vacancy" for a couple hours which, on a warm day, could mean the A/C is needlessly running for up to two hours after I leave the house. That's the one thing I miss about Nest - the native geofencing in the app, which Ecobee only provides in Android (I'm on iOS). I'm hoping the geofencing via the Hubitat app works - will be testing later today.