Is there a way to replicate this behavior in the current implementation of the Ecobee device?
“Away For Now” does a temporary hold with the away temp settings until the next schedule/comfort setting runs. “Home For Now” does the same thing but sets the temp to the Home comfort setting until the next schedule/comfort setting runs.
I know there are Hold options available in the Ecobee device, but it doesn’t seem to work the same way.
I don’t think so. There isn’t really any extra functionality that isn’t already available in the default templates. This will require updates to the Home Remote’s ecobee integration.
Okay. I think there may be a way to “hack” a solution. I noticed that Ecobee supports “ThermostatPreset” but I don’t see any way to see what values are available. Is there a way to list what is available?
I might be able to simulate what Away for now/Home, for now, do by setting the schedule to "Home or “Away” then setting the thermostat to a temporary hold immediately.
I ended up combining ThermostatHoldState.PermanentHold with the Current Program (available in HomeSeer) and that seemed to work.
Basically, I would set the program/schedule and hold state at the same time and that seemed to simulate what I was looking for.
Additional Note: I noticed if I set the Away For Now from Ecobee, the hold state is: PermanentHold in Home Remote. But if I set PermanentHold from Home Remote, it’s registered as TemporaryHold (wondering if it’s because I’m doing a program change AND the hold).
One additional observation: I noticed that the set points aren’t updating when I do a schedule change and hold
Correction: Looks like all my issues were because I was mixing HomeSeer>Ecobee and Home Remote>Device>Ecobee. When I switched everything to Home Remote>Device>Ecobee everything is working as expected.