Hot fix 1.1.3.116 has been released and is reported to fix webcore I was hoping to somehow get more focus on porting webCoRE for Hubitat and identifying the Hubitat variants of some of the incompatible SmartThings functions in the code. So I have started this thread to serve as a single source for …

Well, this both did and did not work! :slight_smile: Making these changes broke my webcore (the GUI dashboard where you configure new pistons. It would not load and did not see my hub. However, after removing these changes, I still had to log out of the dashboard to get it to work again. After …

If I wanted to change the hubitat Mode to away when Ecobee changes to away, what variable would I use? Also, if I wanted to notify me that the Ecobee temperature has gone up or down, what variable would I use in webcore? currentProgram doesn't seem to work. Any ideas what might work. Since we do…

Are you using the built-in Ecobee integration to HE? If so, the current Comfort Profile is not exposed so therefore you cannot use that in webCoRE either. I left my Ecobee connected to ST for just this very reason. You can see if the temp has gone up or down by using the Temperature from the Ecob…

No, I am using the Ecobee Suite Manager because I can use more variables in Webcore like setThermostatProgram that isn't available with the HE one. I am just not sure what variable would change the Mode.

The current program is listed under "Current Program" or "Current Program ID".

[image] mattw01/Ecobee-Suite Free SmartThings support for Ecobee thermostats. Contribute to mattw01/Ecobee-Suite development by creating an account on GitHub.

[image] Ryan780: The current program is listed under "Current Program" or "Current Program ID". currentProgram doesn't work. That is what I tried.

Are you trying to use the device attributes as a trigger? They are not subscribed to like other "events" so I'm not sure you can use them as a trigger. You can use them as conditions though. I do. [download%20(13)]