I would like to trip the reactor when temperature is above 73 but only untrip once it falls below 60.
Anyway to do this in reactor?
Ty
M
Two groups in one Reactor
Group 1: True: Temperature > 73 > Activities
Group 1: False: Temperature not >73 > NO ACTIVITIES
Groups 2: True: Temperature < 60 > Activities
Group 2: False: Temperature not < 60 > NO ACTIVITIES
Thereās almost certainly a more elegant way, but off the top of my head thatāll do it.
C
1 Like
So I tried this. Not sure how to test it but in the second group the first trigger is above 70 and the 2nd trigger is between 65 and 70 but only after the first trigger is met. If either one is active then the device stays tripped. I think this will work but Iām not sure.
Hope Iām not hijacking the thread but itās similar to a problem I have as Iād like to do the opposite but without motion sensors, ie trip (turn on) if the temp is below 16C and untrip if above 20C, this isnāt a problem but the moment the temp moves 0.1C the heating either turns Off (or On) - not good with gas ducted or split systems.
Presently I use a remotec thermostat that has a temp differential and I havenāt been able to reproduce this with Reactor.
How can I introduce a temperature differential (say 5C) into the Reactor?
OK this seems more complex.
Why would you want the first one to be triggered only afterward? They seem mutually exclusive?
C
Hmmm, no idea explicitly but how about setting a latching time so once the heating comes on it stays on for (say) 5 minutes? Same when it goes off?
C
This doesnāt seem to reflect the group structure that @Catman suggested, which is a workable/correct solution for the problem as posed. His structure is two groups in parallel (as siblings under the root group). This structure is āOutside tempā as a subgroup of the root group, which effectively makes āOutside tempā a condition of the outer group, and I donāt think thatās intended.
No good using a set time as it is a variable, it could 5 mins or 50 mins before the temp decrease enough to trigger the activity.
Hysteresisā¦ really the same problem.
Group 1 - Call Heat
- Device State temperature sensor < 16
Group 2 - Cancel Heat
- Device State temperature sensor >= 20
Activity āGroup 1 is TRUEā turns on the heater. Activity āGroup 2 is TRUEā turns off the heater.
1 Like
Iām new to reactor, trying to move things from pleg and using a mixture of both so forgive me.
the root conditions were quite intentional as I need those to be true in addition to the temperature conditions below that.
At this point I was simply tripping this on or off and pleg using the trip status of this reactor in a condition there
More a thought of ātrigger immediately and remain trigged for n minutes no matter what the temperature doesā
That, at least, would stop the states flicking.
But of course, @rigpapa nails it. DOH so obvious when someone rams it down your throat 
C
^^^ @rigpapa
Great, I can see the logic but while I could do this in PLEG, Iām struggling to find a way to make it work in Reactor. Take the following.
Obviously Iām not thinking Reactor but canāt find a way to have more than 2 Individual Groups that will give any Activity without it being a Condition.
You could use 2 seperate Reactors each one with a ādudā condition but I don;t think that is the way you intend it?
Any group you make NUL has no logic output and thus is not eligible to have Activities.
Your conditions should look like this:
And your activities like this:
@rigpapa
Thatās interesting as the group doesnāt like it as there is no other āstateā for the condition and remains in red - which indicates that it isnāt correct or needs correction - Iām I right in this conclusion?
It took me some time to work out how you got to this state as it wasnāt clear, but you canāt break it and a good play is the way to go.
Changing it to disabled still allows the activities to show status
Why have you disabled them? They should not be disabled.
They are enabled, I just wanted to see what would happen if they were disabled.
Just having a good play with it nowā¦
OK. Click on those ugly group names in the Conditions tab and give those groups some better names. Those default names canāt be helping.
No they arenāt, have also done that ā new problem is that I want to combine this all into one reactor - getting adventurous now, which raises a new problem as I don;t seem to be able to create logic using the True/False within that group, I need to go to the HeatSetpoint reactor to find the logic.
I think Iām getting over my head now and need an aspirin as I can see further problems ahead.
@rigpapa
Getting there but there are a couple of unanswered questions of why?
Please refer to the below image.
- The reactor schedule only work if they are False, which is weird as they worked correctly before when set to True. Setting it to TRUE turns the heat off!
- The Temp never moves off 19.44
logs below.
*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.5 config 20017 cdata 20045 ui 20045 pluginDevice 572 LuaXP 1.0.1
System: Vera version 1.7.4969 (7.31) on Sercomm NA301 ID 35 (Vera Edge); loadtime 1588936848; systemReady 1588936881; Lua 5.1; JSON dkjson 1.2; UnsafeLua=nil
Local time: 2020-05-09T09:20:27+1000; DST=0; Patterson Lakes, Victoria Australia; formats %d/%m/%Y %H:%M:%S
House mode: plugin 1; system 1; tracking off
Sun data: { "source": "int", "civdawn": 1588970410, "nautdawn": 1588968515, "sunset": 1589009024, "nautdusk": 1589012591, "stamp": 2020130, "latitude": -38.0693, "astrodusk": 1589014452, "longitude": 145.143, "civdusk": 1589010696, "astrodawn": 1588966654, "sunrise": 1588972082 }
Geofence: not running
************************************************************************************************************************************
Heating Setpoint (#676)
Version 20045.34 05/08/20 20:36:14
Message/status: Not tripped
Condition group "Setpoint" (NUL) false as of n/a <root>
Z-T-group "HeatOn" (AND) TRUE as of 09:12:44 <grprdkm7kp>
| &-T-service RearTempSensor (469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature < 19 [19.44 => 18.89 at 09:12:44; T/T as of 09:12:44/09:12:44] <condrdss6za>
| &-T-grpstate WinterSchedule (660) Fri-Sat-Night (grpr6ikpn4) isfalse [true => false at 08:00:00; T/T as of 08:00:00/08:00:00] <condre9l6a6>
Z-F-group "HeatOff" (AND) false as of 20:30:53 <grprdstwav>
| &-F-service RearTempSensor (469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature >= 21 [19.44 => 18.89 at 09:12:44; F/F as of 20:30:53/20:30:53] <condrdstyi5>
| &-T-grpstate WinterSchedule (660) Fri-Sat-Night (grpr6ikpn4) isfalse [true => false at 08:00:00; T/T as of 08:00:00/08:00:00] <condre9sn4s>
Activity grprdkm7kp.true
Device Broadlink RMPro (481) action urn:micasaverde-com:serviceId:Broadlink1/SendCode( CodeData="1586475909" )
Activity grprdstwav.true
Device Broadlink RMPro (481) action urn:micasaverde-com:serviceId:Broadlink1/SendCode( CodeData="1513567862" )
Comment:
Events
2020-05-09 06:34:49: Changing RS tripped state to false
2020-05-09 06:35:49: Reset action invoked
2020-05-09 06:35:49: Changing RS tripped state to false
2020-05-09 06:36:49: Reset action invoked
2020-05-09 06:36:49: Changing RS tripped state to false
2020-05-09 06:37:49: Reset action invoked
2020-05-09 06:37:49: Changing RS tripped state to false
2020-05-09 06:38:49: Reset action invoked
2020-05-09 06:38:49: Changing RS tripped state to false
2020-05-09 06:39:49: Reset action invoked
2020-05-09 06:39:49: Changing RS tripped state to false
2020-05-09 06:40:49: Reset action invoked
2020-05-09 06:40:49: Changing RS tripped state to false
2020-05-09 06:41:49: Reset action invoked
2020-05-09 06:41:49: Changing RS tripped state to false
2020-05-09 06:42:49: Reset action invoked
2020-05-09 06:42:49: Changing RS tripped state to false
2020-05-09 06:43:49: Reset action invoked
2020-05-09 06:43:49: Changing RS tripped state to false
2020-05-09 06:44:49: Reset action invoked
2020-05-09 06:44:49: Changing RS tripped state to false
2020-05-09 06:45:49: Reset action invoked
2020-05-09 06:45:49: Changing RS tripped state to false
2020-05-09 06:46:49: Reset action invoked
2020-05-09 06:46:49: Changing RS tripped state to false
2020-05-09 06:47:49: Reset action invoked
2020-05-09 06:47:49: Changing RS tripped state to false
2020-05-09 06:48:49: Reset action invoked
2020-05-09 06:48:49: Changing RS tripped state to false
2020-05-09 06:49:49: Reset action invoked
2020-05-09 06:49:49: Changing RS tripped state to false
2020-05-09 06:50:49: Reset action invoked
2020-05-09 06:50:49: Changing RS tripped state to false
2020-05-09 06:51:49: Reset action invoked
2020-05-09 06:51:49: Changing RS tripped state to false
2020-05-09 06:52:49: Reset action invoked
2020-05-09 06:52:49: Changing RS tripped state to false
2020-05-09 06:53:49: Reset action invoked
2020-05-09 06:53:49: Changing RS tripped state to false
2020-05-09 06:54:49: Reset action invoked
2020-05-09 06:54:49: Changing RS tripped state to false
2020-05-09 06:55:49: Reset action invoked
2020-05-09 06:55:49: Changing RS tripped state to false
2020-05-09 06:56:49: Reset action invoked
2020-05-09 06:56:49: Changing RS tripped state to false
2020-05-09 06:57:49: Reset action invoked
2020-05-09 06:57:49: Changing RS tripped state to false
2020-05-09 06:58:49: Reset action invoked
2020-05-09 06:58:49: Changing RS tripped state to false
2020-05-09 06:59:49: Reset action invoked
2020-05-09 06:59:49: Changing RS tripped state to false
2020-05-09 07:00:49: Reset action invoked
2020-05-09 07:00:49: Changing RS tripped state to false
2020-05-09 07:01:49: Reset action invoked
2020-05-09 07:01:49: Changing RS tripped state to false
2020-05-09 07:02:49: Reset action invoked
2020-05-09 07:02:49: Changing RS tripped state to false
2020-05-09 07:03:49: Reset action invoked
2020-05-09 07:03:49: Changing RS tripped state to false
2020-05-09 07:04:49: Reset action invoked
2020-05-09 07:04:49: Changing RS tripped state to false
2020-05-09 07:05:49: Reset action invoked
2020-05-09 07:05:49: Changing RS tripped state to false
2020-05-09 07:06:49: Reset action invoked
2020-05-09 07:06:49: Changing RS tripped state to false
2020-05-09 07:07:49: Reset action invoked
2020-05-09 07:07:49: Changing RS tripped state to false
2020-05-09 07:08:49: Reset action invoked
2020-05-09 07:08:49: Changing RS tripped state to false
2020-05-09 08:00:00: Device WinterSchedule (#660) urn:toggledbits-com:serviceId:ReactorGroup/GroupStatus_grpr6ikpn4 changed from "1" to "0"
2020-05-09 08:00:00: Condition condre9l6a6 test state changed from false to true
2020-05-09 08:00:00: Condition condre9l6a6 evaluation state changed from false to true
2020-05-09 08:00:00: Group HeatOn test state changed from false to true
2020-05-09 08:00:00: Group HeatOn evaluation state changed from false to true
2020-05-09 08:00:00: Condition condre9sn4s test state changed from false to true
2020-05-09 08:00:00: Condition condre9sn4s evaluation state changed from false to true
2020-05-09 08:00:00: Launching HeatOn.true activity
2020-05-09 08:00:00: Launching scene/activity grprdkm7kp.true
2020-05-09 08:00:00: Starting "grprdkm7kp.true" group 1
2020-05-09 08:00:00: Activity "grprdkm7kp.true" finished
2020-05-09 08:13:14: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "16.67" to "17.22"
2020-05-09 08:21:55: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "17.22" to "17.78"
2020-05-09 08:27:34: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "17.78" to "18.33"
2020-05-09 08:32:09: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "18.33" to "18.89"
2020-05-09 08:33:19: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "18.89" to "18.33"
2020-05-09 08:35:14: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "18.33" to "18.89"
2020-05-09 08:54:27: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "18.89" to "19.44"
2020-05-09 08:54:27: Condition condrdss6za test state changed from true to false
2020-05-09 08:54:27: Condition condrdss6za evaluation state changed from true to false
2020-05-09 08:54:27: Group HeatOn test state changed from true to false
2020-05-09 08:54:27: Group HeatOn evaluation state changed from true to false
2020-05-09 09:12:44: Device RearTempSensor (#469) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature changed from "19.44" to "18.89"
2020-05-09 09:12:44: Condition condrdss6za test state changed from false to true
2020-05-09 09:12:44: Condition condrdss6za evaluation state changed from false to true
2020-05-09 09:12:44: Group HeatOn test state changed from false to true
2020-05-09 09:12:44: Group HeatOn evaluation state changed from false to true
2020-05-09 09:12:44: Launching HeatOn.true activity
2020-05-09 09:12:44: Launching scene/activity grprdkm7kp.true
2020-05-09 09:12:44: Starting "grprdkm7kp.true" group 1
2020-05-09 09:12:45: Activity "grprdkm7kp.true" finished
Devices
Broadlink RMPro (481) urn:schemas-micasaverde-com:device:Broadlink:1 (1/-1); parent 0; plugin 8996; mfg model ; dev D_Broadlink.xml impl I_Broadlink.xml
ZWBC41S-RearDoor (468) urn:schemas-micasaverde-com:device:ComboDevice:1 (12/0); parent 1; plugin -; mfg Philio model PST02-A; dev D_ComboDevice1.xml impl
RearTempSensor (469) urn:schemas-micasaverde-com:device:TemperatureSensor:1 (17/0); parent 468; plugin -; mfg model ; dev D_TemperatureSensor1.xml impl
Watches
Device #660 WinterSchedule service urn:toggledbits-com:serviceId:ReactorGroup variable GroupStatus_grpr6ikpn4
Device #469 RearTempSensor service urn:upnp-org:serviceId:TemperatureSensor1 variable CurrentTemperature
Device #676 Heating Setpoint service urn:toggledbits-com:serviceId:ReactorSensor variable TestHouseMode
Device #676 Heating Setpoint service urn:toggledbits-com:serviceId:ReactorSensor variable cdata
Device #676 Heating Setpoint service urn:toggledbits-com:serviceId:ReactorSensor variable TestTime
Special Configuration
UseReactorScenes = 1
LogEventsToFile = 0
Retrigger = 0
FailOnTrouble = 0
ContinuousTimer = 0
Sorry, I have no idea what this means. Schedule? Not posted. Youāre testing āis falseā in the conditions, I donāt knowā¦
The Conditions editor is not a dynamic view. The Status tab is the (one and only) dynamic view.