Hi,
I have a multizone heating setup using Eurotronic Spirit TRVs (Same as Aeotec just launched rebranded)
I’m struggling with the export/store of a variable to re-use later. I need to store a current setpoint, change it to something else for 30 minutes, then use that variable to revert to the previous value. (Use case is the minimum setpoint is 8 degrees on these. I have them turned off in empty rooms, and want to turn them on to heat/25 degrees as a boost to prevent pipes freezing in winter (if rooms get to 2 degrees). In the UK I can’t leave at 8 as that means the boiler would be firing all winter for empty rooms, as its normally lower than that. Each room is its own independantly controlled zone, each able to demand the boiler fire even if all the others are off or closed and not demanding heat).
Could someone please guide. I have the variable defined, it’s just the save, change and re-set later i’m stuck with. Thanks
Hi,
I had found that but I still didn’t get the variable returned/saved. I just get null ( even after changing the variable after saving the expressions). I’ve replicated exactly including expression names but still null. I do have several uses (including lights on and return to same state as in referenced post) to take stored temp related variables and setting them back after, specifically this case and also ‘night’ mode for the occupied rooms, but returning to whatever the radiators were set to the previous day
I don’t see anywhere you’re saving current in your actions. There should be a SetVariable action run against the ReactorSensor. Check the linked example’s actions and you’ll see them.
You’re definitely into an advanced topic, but pushing limits is a good thing–you get to do new stuff, and I get to see where I can smooth things out more.
On a Seperate note ( to create a heating dashboard on the web ui and imperihome), I used reactor to create an indicator panel in multiswitch to show which rooms (each including bed and bathroom) were demanding heat based on setpoint vs temp -1.2 degrees (which stops valves closing too far near matched temps). It is brilliant to group devices and then return a true/false for status, even though no actions are needed there.
I also used reactor to create a quick set button in another multiswitch to 1.turn the guest room bedroom to 18, bath to 15 degrees, or set both to 8, and also an All Guests Off to set all rooms to 8 and turn the TRVs off (but they are still protected by the “anti freeze” sensor you just helped me configure :))
One thing that would be brilliant (unsure if exists or possible) would be the ability to create a contexed variable based on the device, where many of the same device types are used. It looks like I have to create 2 seperate variable for all my TRVs to save the state.
If only there were a way to create a generic variable for specific value ( like “urn:upnp-org:serviceId:TemperatureSetpoint1_Heat”, “CurrentSetpoint”) but be able to easily pull it and store from multiple devices .
Or even a way to create the individual variables in a batch or near copy based on a selection. (like with 10+ TRVs that are identical function wise but i need to save the same value and return the value later on each one). Perhaps Similar to the copy function elsewhere. Maybe where add variable is, an add similar that keeps the whole expression but just allows selection of specific device and doesn’t require the functions to be chosen again (kind of like a copy expression with a find/replace of the device ID if that makes sense.
Actually, that feature would be also great when using the “copy from” in activities, the ability to choose a replacement device would save lots of reselecting in multiple places, the next device (TRV in this case)
In any case, i’ll be donating to your development pot
Thanks again.
Yeah, I have another plugin that I haven’t released publicly that, among its capabilities, saves the state of devices as they are being modified and can restore them later to a point in time. I’ve been pondering how to get such a feature into Reactor, but it requires a good bit of additional data that Vera doesn’t keep handy natively, and I’m trying not to have the device information file Reactor already has not get a lot larger (almost unavoidable). Much to ponder here, but it’s definitely on my radar as a higher priority item.
That sounds awesome for the state saving. It is so handy for temps and light levels. I can also see it being used in energy monitoring triggers too (which I use to turn things on to charge batteries etc to prevent solar export to grid).
I’ll happily test anything if you think my setup is of use (i’m running over 20 reactor sensors and haven’t even properly started moving the multizone heating control from PLEG over yet).
A real big thing if you see value/have time would be the copy and device replace in activities tab (for more complex series actions).
My copy only effectively copies delays and I have to reselect every device, variable and value for each identical TRV.
The state variables are only a small part of the repetition here
Everything in yellow, I have to redo another 11 times