I have to re-validate my Ecobee account everyday with the native integration.
Happens to me too. Not everyday though. It’s been stable for the last month though.
It also was happening to me with the non native ported driver as well.
Next time it happens I’ll have to take some logs.
Still happening everyday, the Ecobee Integration is not useful in this condition.
Just to put out another data point, I only had to validate my ecobee account during initial setup of the integration. I have two Ecobee 4's connected to Hubitat.
I am not trying to downplay your issue, just want you to know its not system wide.
Curious. I've had an awful lot of trouble with things others do not.
Thanks for reporting this. I went and took a closer look at our process for refreshing the token and it looks like if it fails on the first try, the second try blows up and you have to reauthorize. We will put in a fix for that and see if that fixes your issue as well.
Ah, glad to know I'm not crazy. Thanks Chuck
This probably explains why when mine stopped working it was always around the same time that they announced an outage on their service monitoring feed. Good to know it was actually an issue.
Once again my ecobee integration is not working.
Some logs from the Ecobee integration
app:15832018-10-07 22:40:43.778:traceenableOauth response data: null
app:15832018-10-07 22:40:21.522:warnsendCommandToEcobee failed due to authToken=null
app:15832018-10-07 22:39:39.521:warnsendCommandToEcobee failed due to authToken=null
And some logs from the thermostat if I try to set the heating point
[dev:1666](http://hubitat.localdomain/logs#dev1666)2018-10-07 22:40:26.535:debugrefresh, calling parent poll
[dev:1666](http://hubitat.localdomain/logs#dev1666)2018-10-07 22:40:19.305:debugsetHeatingSetpoint- setpoint:21
[dev:1666](http://hubitat.localdomain/logs#dev1666)2018-10-07 22:40:09.877:warndebug logging is: true
[dev:1666](http://hubitat.localdomain/logs#dev1666)2018-10-07 22:40:09.872:debugupdated...
Now if I go into the ecobee app I have to re authenticate.
Noticed ecobee had issues this week. It seems like whenever this happens its usually around the same time as when ecobee has cloud issues.
I am now having to re-authorize for Ecobee integration too. 
Look forward to a fix.
The thermostatoperating state of my ecobee doesn't seem to be updating at all. I confirmed that the stat is connected and just in case I re-authorized anyway but it still says idle even though my heat has been on for about 6 minutes. I hit refresh, that doesn't seem to change anything. I can confirm that status is listed correctly in the ecobee and ST app.
A new error for the required re-authorization.
warn sendCommandToEcobee failed due to authToken=nullFor posterity, I found these errors this morning.
Looks like ecobee api went down. We'll see how it reacts.
error Unhandled exception java.net.UnknownHostException: api.ecobee.com: Name or service not known in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true
info HttpResponseException groovyx.net.http.HttpResponseException: Internal Server Error, 500 polling ecobee pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true, [status:[code:14, message:Authentication token has expired. Refresh your tokens. ]]
error groovy.lang.MissingPropertyException: No such property: status for class: java.io.StringReader (poll)
info HttpResponseException groovyx.net.http.HttpResponseException: Service Temporarily Unavailable, 503 polling ecobee pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true, { "errors": [{ "status": "503", "detail": "Servers are undergoing maintenance and are currently unavailable. Please check back later" }] }
error Unhandled exception java.net.UnknownHostException: api.ecobee.com: Name or service not known in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true
error Unhandled exception java.net.UnknownHostException: api.ecobee.com: Name or service not known in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true
error Unhandled exception java.net.UnknownHostException: api.ecobee.com in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true
error Unhandled exception java.net.UnknownHostException: api.ecobee.com in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true
error java.net.UnknownHostException: api.ecobee.com: Name or service not known (setHold)
error java.net.UnknownHostException: api.ecobee.com (setHold)
info HttpResponseException groovyx.net.http.HttpResponseException: Internal Server Error, 500 polling ecobee pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true, [status:[code:14, message:Authentication token has expired. Refresh your tokens. ]]
error Unhandled exception java.net.UnknownHostException: api.ecobee.com: Name or service not known in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:trueSince 1.1.6 I have not had any issues with the integration. Just checked again today and the connection is still valid.
I re-authed again, and I'm still getting these errors whenever any automation attempts to do anything with the thermostats.
errorUnhandled exception java.net.UnknownHostException: api.ecobee.com in ecobee polling pollAttempt:1, isThermostatPolled:false, isSwitchesPolled:true
errorjava.net.UnknownHostException: api.ecobee.com (resumeProgram)I get this entry every hour. Even after just reauthorizing. This says Token expired. Did it really or should I ignore this until PollAttempt count climbs?
My ecobee is the last device I have on my ST hub. I figure since it's a cloud integration and not local, it doesn't really matter if it's on Hubitat or not. If my internet is down, Hubitat wouldn't be able to control it anyway. And until Hubitat gets Google Home integration, I can't shut off ST anyway.
I'm not getting the re-authorization issues, but i upped my polling time up to 5 minutes and that seemed to solve it. Still not getting any updates in Hubitat for operations state though, even if I force refresh.
Just wanted to drop in here an update, mine has been working reliably lately.
Your ThermostatOperatingState is updating correctly when heat or air is running?
I'm still curious to hear if your Ecobee's ThermostatOperatingState is actually updating. Mine still isn't.
