Ecobee automation after Groovy/Webcore retirement

[MarkTr]

Quoting my reply from the other thread to bring it into context here, along with @Terri_Baker 's comments about IFTTT:

@Terri_Baker

I use Ecobee also and have been in contact with Ecobee support since the transition to Edge was announced. As of the last update recieved Ecobee C2C connection will continue to work with basic features. They currently have no plans to add support for comfort settings to Smartthings saying IFTTT can be used for this. I already have an IFTTT account so tried it and it works almost as well as the Ecobee Suite smartapp that will soon end. Only thing I had to do was create a few virtual switches in ST. Hope this helps.

@MarkTr

I’m doing the same thing, but replacing Ecobee Suite helpers instead of WebCoRE pistons, and moving to the SharpTools.io rules engine. Sharptools is between WebCoRE and IFTTT in terms of abilities, but much closer to WebCoRE. I don’t think there’s any limit on number of rules you can create on a free account; a paid account gets you more features, including variables, which I haven’t found that I need so far.

I’m still running the Ecobee Suite handler for the thermostat while I rebuild my automations; I think when I re-add it as a stock device, I’m going to lose a lot of the capabilities that are available to my SharpTools rules.

With the helpers I had the comfort modes set to hold indefinitely; now I suspect they’ll only hold until the next scheduled change, but it’s so long since I’ve used the built-in scheduler that I have no idea what that looks like. My hope is that even if the modes are out of whack, between school runs and at least one person working from home most days we’ll be coming and going often enough that we bump it back into the desired mode pretty quickly anyway.