I'm using the Ecobee integration - 4 thermostats, 9 sensors.
I notice that the thermostat state never updates on any of the thermostats, so there is no way to tell if the HVAC is heating, cooling, or idle.
On all 4 of my thermostats the "thermostat" variable always says "Right Now: Idle".
Is there anything I can do to get this to update??? Without being able to see cooling/heating cycles I can't use things like Keenect...
Did you set a data poll rate after installing the integration?
I set it at 2 min when I installed it.
I just changed it back to not selected to see if it would do anything different (hasn't been that way long enough to tell).
Should be set to 5 minutes. Just for a test I set mine to 1 minute and then raised the temp by 1˚ and it does update from "Right Now: Idle" to Idle to "Heating to 68˚F"
I was trying to use it to turn a humidifier on when the heater turned on. so that it could get a head start and lesson the drop in humidity. Mine will update but change does not get pushed by ecobee as it changes it only updates during a poll for me that's about a 5 minute delay
I'll try changing it to 5 minutes and see what happens. I would have thought having it set to 2 minutes would have worked the same (just faster) though?
If you change to 1 minute, you should be able to see an update, but the recommended refresh is not less than 5 minutes.
Is the Humidifier attached to the furnace? I have an flow-through humidifier on my furnace and the Ecobee native control over it is fantastic. Our house stays at exactly the correct humidity throughout the Winter.
I had to use an app and driver ported from ST. It's the HE version of Sandood's Ecobee Suite. The native integration never updated the thermostatOperatingState for me.
Should. I'm using the native integration. Maybe just needed to be installed and re-installed? Anyway, you have a solution that works for you. Just suggesting for someone else reading this.
On a side note, this testing got me to look at my Ecobee web portal which I have not done in a long time. Honestly the thermostat is a set and forget thing for me. I spend very little time thinking about it. Anyway, my thermostat has finally paid for itself in savings. Took three years because we don't have A/C, so the cost saving only come from out heating months.
I forced my heat on, and at 1 minute the status DID change. So it must have been a timing thing before... I didn't change anything else.
I was looking specifically for a speedy update to thermostatOperatingState because I have ceiling fans and one floor fan that I have to run in the summer when the AC is on or the house doesn't cool as efficiently (downstairs is freezing upstairs is hotter than hell). That's the reason I've tried to integrate all my fans into my home automation, first ST and now HE. When I first installed HE I did a test with the native integration and it never updated thermostatOperatingState unless I changed the temp setting on the thermostat. If it was recovering to an already set temp, there was no update in HE. Now, this was a couple months ago. Maybe the native integration has changed, but I haven't seen anything in the release notes. I should point out that the temp is always right in HE...just not the current operating state (heating, cooling, idle).
Mine always changed when I changed the temp of the thermostat. When it wouldn't update correctly was when it was recovering to a temp that had already been set. I did a LOT of testing around this when i got HE because back when I had ST and a Honeywell thermostat I suffered from the same thing. Took 3 months and conversations with the integration specialists at ST and 4th or 5th level support at Honeywell before I finally got Honeywell to admit it was their bug. I think it's still not fixed.
Now that you mention it that is correct, mine would change right away if I changed the set point temp and caused the heat to go on but if temp dropped and kicked on on it own it would not update until the next poll.
I wish, it's console model controlled by a smart outlet and a few rules
Pulling this thread back from the dead. I have three Ecobee4 devices running the built-in HE Ecobee Integration app with SmartTools for dashboards. Coming from SmartThings + ActionTiles the tile would update it 'thermostatOperatingState' and 'thermostat' often after a temperature setpoint change but always on a poll/refresh if the unit was running. The debug does not give much information on the poll and always shows the unit is 'idle'.
Is this working for anyone else?
Looks like my Ecobee thermostats stopped updating at 1:45pm on 9/29. I have not started troubleshooting it yet. But prior to this time, everything was working fine.
UPDATE: I was able to get my Hubitat Ecobee integration working again by disabling 2FA on my Ecobee account, and then logging back into Ecobee via the Hubitat Ecobee App. As long as 2FA was enabled, I could not get the Hubitat Ecobee integration working.
I don’t have 2FA enabled and the DH is sending and receiving commands. I specifically am not seeing the operational state change. When the unit is actively cooling or heating it should not indicate “idle” as shown in my post. Do you see that changing with your configuration?
Those updates are handled by Hubitat polling Ecobee every 5 minutes (default.) Do you have the polling feature enabled?
Yes, the polling is active and working. This isn’t a question of authoritative or non communication. It is ONLY about the driver not updating the operating state “cooling” or “heating” when it actually is signaling the HVAC to run. This works fine with SmartThings and still does.
The Hubitat DH if proper should poll immediately after any configuration change for this state and then at the poll rate you show above.
Well, auto magically they started working today. I was surprised to see the SharpTool icon show (Cooling) - so looked this AM and the DH had updated 'thermostatOperatingState' and 'thermostat' properly. 
Download the Hubitat app
