There is no way under ST to call ecobee to resume or set a specific climate/comfort settings from a routine as the ecobee thermostat is probably the only one thermostat that has this capability. ST routines were designed for the generic thermostat capabilities, not for the ecobee which has more advanced features.
FYI, even the Nest doesn’t expose its own schedule…And, the z-wave/zigbee thermostats are quite ‘dumb’ in terms of scheduling as they require external HA scripts.
However, using my smartapps, you can bypass the ST location mode and use any ST presence & motion sensors to achieve what you want to do.
In the configuration section of My ecobee device in the ST community wiki, I’ve written the following:
Most of my Ecobee smartapps have been developed with this principle in mind: ecobee is responsible for the basic scheduling (as it’s more reliable and also accessible from the physical thermostat anytime) and ST is responsible for managing exceptions to the schedules that you define (i.e., ‘Away’ or ‘Home’ mode switch as an example).
Under the following section 3c), I mentioned different smartapps to be used listed by their complexity (according to the use cases you want to achieve):
If you don’t want to use ecobeeChangeMode , you can use ecobeeAwayFromHome and ecobeeResumeProg which allow you to set your thermostat to Away or Home based on several conditions amongst others presence and motion detection.
For more details on ecobeeResumeProg, refer to
P.S. If the above smartapps don’t meet your requirements, you can always use your favorite rule engine (CoRE, webCoRE, smartRules) to customize your HA script for your own use case. The methods that you can call are resumeProgram(), away(), asleep() and home() in the DTH to switch to the ecobee Away, Night, or Home climates respectively.