That’s weird… I just checked my code, and it never sends an attribute change without first checking that the new value is in fact a new value (by calling isStateChange(…) before sendEvent(…) ). So something else has to be generating the double events. I have long suspected that SmartThings will randomly send 2 events without reason or detectable cause (so I can’t fix it).
FWIW, I have in the past tried to prevent these by checking if the event I recieve is a duplicate of a prior one, but as you note the two events seemingly arrive so close together that there isn’t even time to do the comparison…
If these become consistent and not random, please let me know and I’ll see if I can get help from SmartThings to resolve the issue…
Hello. I’m having a persistent issue where at least one, if not more, of my thermostats go into a “HUB_DISCONNECTED” state on SmartThings. I know SmartThings is having an issue with Device Health and that this is the primary cause, but the issue with my Ecobee Thermostats continues to persist which makes me wonder if there is an attribute within the Thermostat DTH that is contributing to the cause. Sometimes the issue will correct itself if I reboot my SmartThings V2 Hub, but the inverse can happen where all of my Ecobee Thermostats (3) are in an “ACTIVE” state and then at least one will go into a “HUB_DISCONNECTED” state after a reboot. Also, the “HUB_DISCONNECTED” state is cosmetic as the thermostat device(s) still function in SmartThings and report properly, but show as “Unavailable” in the SmartThings app (iOS).
As long as they keep working, rest assured that it is the SmartThings bug.
If you’d like, you can try commenting out the line at the top of Ecobee Suite Thermostat and Ecobee Suite Sensor that says "capability "Health Check" (delete it or put two slashes in front of the line like this: // capability "Health Check".
Thank you, sir. I rem’d out the Health Check capability which at least solves the “Unavailable” issue in the App, but I have one thermostat that is staying in a “HUB_DISCONNECTED” state even after rebooting my hub several time.
Another issue cropped up at approx. 3:30 PM CDT. The following error started appearing in Live Logging for the Ecobee Suite Manager SmartApp:
This is appearing at every poll interval. I can’t correlate the start to anything that has happened on my side (IE: hub reboot, Thermostat DTH mod by rem’ing out Health Check, etc). Shortly after I started seeing this I received a notification from SmartThings Support that the system wide Device Health issue had been solved. I’m not sure if there’s a correlation there or not, but my Device Health issue(s) still exist.
Update: Problem solved. I re-authenticated the Ecobee Suite Manager and all sensors are now “ONLINE”, one of the two thermostats that were “HUB_DISCONNECTED” is now “ONLINE”, and the error in Live Logging has stopped. I still have one thermostat that persists in a “HUB_DISCONNECTED” state regardless of what I do.
Since this is Hubitat I don’t think calling SmartThings will help. But I bumped up logging last night to catch the even and darn the logging buffer on the Hubitat rolled out the duplicate events from this morning. What I will do is watch it closely over next couple of days and try to catch the details you may need to debug.
Use “Import”. Hubitat will remember the source location for Apps, and I’ve coded in the source location in the two Drivers - so all you have to do is open each file, Import, and Save…
Please understand that I have no way to look at your installation of SmartThings or Ecobee Suite Manager, so I need you to be my eyes and describe the situation for me so that I can help you.
Let’s start by describing what you are trying to accomplish, and how you have configured things to make this happen, and what isn’t working as you expect it should?
Then I’ll need the following:
What date and time did this failure occur?
Ecobee was down at times yesterday - first for some issues, then for some maintenance. If Ecobee’s servers are unavailable or unreachable, my Ecobee Suite can’t make the thermostat do anything. It will try to replay any failed commands once the servers are available again.
a. Were you able to use the Ecobee Mobile app to control the thermostat at the time it was “failing?”
b. Did you check https://status.ecobee.com/ to see if there were any issues at the time of your failure?
SmartThings also has been suffering some outages since July 27, and there are issues that are not yet resolved, according to an email I received from them this morning.
a. Did you check https://status.smartthings.com to see if there were any outagees there at the time of your failure?
What are the version numbers of ES Manager and ES Thermostat that you are using?
Which ES Helper are you using?
a. What version is it?
b. How is it configured - could you send me a screen shot of the configuration pages?
Have you looked at the Live Logging for ES Manager, ES Thermostat, and the Helper(s) to see if any Errors or Warnings are flagged when it “fails?”
a. If so, can you send me (PM) the relevant log entries?
Smart Mode 1.7.16: The status message (Off - Hold: Home) is being appended and not replaced resulting in multiples of it in the name
Thermal Comfort 1.7.13: New instances don’t show the notification configuration section. Existing instances error and can’t load the configuration section.
java.util.NoSuchElementException: Cannot access first() element from an empty List @line 208 (doCall)