I don't know how feasable this is, but I'd like to sugget adding the ability to populate setpoints in thermostat scheduler with rule machine global variables. I have been able to do it using a rule, but having thermostat scheduler directly accept the variable would be great. My use case it that I have a setpoint reset based on outside temperature so as it gets hotter the cooling setpoint goes down.
Variables are specific to Rule Machine and rules. They are not available in other apps. This is not a feature request that we would implement.
With the announcement of Hub Variables, which are supposed to be available to other apps, might these be made to work with the Thermostat Scheduler. I would like to see this feature, as well, since I have to use different heat/cool ranges for summer and winter.
We'll get there.... For first release we're just changing Rule Machine from Global Variables to Hub Variables. Assuming that all goes as planned, then we'll begin the process of incorporating Hub Variables into other apps.
5 Likes
Any update here? I'd REALLY love to be able to set thermostat schedules based on a global variable. My use case is Winter Credit mode with my local electricity provider, Hydro Québec. I have a NodeRed instance running on a device in my network, which parses for a particular email I get from Hydro Québec when they announce a Winter Credit period the next day. This triggers a Maker App API, which sets a switch. At midnight, a global variable gets set when that switch is on. I want to make my Thermostat Scheduler use a different schedule (and set points) if the Winter Credit mode is on.
EDIT: if the Maker API could set global variables directly, I'd wouldn't even need the intermediate virtual switch... is this also planned?
So, replying to myself... Playing around, I realized that Thermostat Schedules can be restricted based on switches, so I replaced my global variable by a virtual switch.
