A setpoint would only change if you change it, perhaps you mean if there is a change in Temp regardless of the setpoint?
If you are wanting a change from the setpoint either up or down then just use < or > in the condition.
Trigger: Setpoint
CurrentTemp
Condition: (CurrentTemp< setpoint) or (CurrentTemp> setpoint)
Action: What you want it to do.
You might need to change the order or CurrentTemp and setpoint.
Have a read of PLEG Basics if in doubt. ( I just play around with it until I get the desired result)
I did mean setpoint. I have a wall thermostat that i’d like to use to control a virtual thermostat - so setting the wall to 71 should set the virtual to 71 as well. Thanks for the <> advice.
Re the Action, how do you pass the actual setpoint variable from one device to the other? I couldn’t figure this out in either PLEG or Reactor.
In reactor, you need to get the current setpoint and assign that to a variable.
In the Expressions tab add a new variable, call it what you want then hit the cog wheel. That’ll give you a drop down. Grab the device and the attribute.
You then need to toggle the up and down arrows which exports the variable
Then in the activities you can use that as the value to send to the virtual thermostat
Does that help?
(Hopes i"ve not screwed this up) Maybe it should be in another thread…
Thanks will try that. I have just about everything written in pleg and I’m not really in the mood of rebuilding everything in reactor nor did I find it very easy to use with multiple ands and ors. I have a few hundred conditions that would need to be rewritten.
Can anybody help me with the same question for pleg?
I dont have a vera running right now, so this is all from memory.
You could use pleg to detect a change in set point, then run a scene with luup that pulls the set point from the physical thermostat and applies it to the virtual.
local thermostat=44
Local virtual=45
local target_temp =luup.variable_get(“urn:upnp-org:serviceId:TemperatureSetpoint1”,“CurrentSetpoint”, thermostat)
As a triger i use when setpoint temperature goes above 6 C (or minimim F)
in action i use the following luup code
local lul_temp = luup.variable_get(“urn:upnp-org:serviceId:TemperatureSetpoint1_Heat”,“CurrentSetpoint”, id of wall thermostat)
luup.call_action(“urn:toggledbits-com:serviceId:AutoVirtualThermostat1”, “SetCurrentSetpoint”, {NewCurrentSetpoint = lul_temp}, id of virtual thermostat)
I not sure if we are talking about the same thing now, this was about Setpoints?
I had to look at what I did on the VL which is still humming away doing what it was designed for.
The reality is that Temp changes are detected by the Temp Sensor in the Thermostat.
The below is in UI5, not all triggers,conditions and actions can be shown, this was a limitation of this version of PLEG.
In short Setpoints are just that…a point that has been set and in the case of Thermostats, it is the Thermostat that maintains the Temp, not the HA System.
The above illustrates how you can get a value from your thermostat in PLEG (really simple as it in the drop down), select what temp you want then use this trigger in your Conditions to do whatever you want to do.