I created a reactor device to monitor humidity and whether or not the thermostat is on. Every so ofter I have to restart the device because it indicated tripped but the HRV is not running.
Is there is way to automate restarting the reactor device to catch these instances?
It should be a very rare case that a ReactorSensor needs to be restarted (usually only when setting the “Test Time” or “Test Home Mode”. It is certainly not something that should be done programmatically or scheduled.
I’m not sure what an “HRV” is? Can you describe what you are doing in more detail, or more correctly, describe what you want it do to. Also, please post a logic summary from the Tools tab.
Here is the logic,
The HRV circulates air in the house to bring humidity down typically. So it is true so the HRV should be on but it is off. Is there is way to get it to recheck the conditions on a timed interval?
Please post a logic summary from the Tools tab.
*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.4 config 19226 cdata 19082 ui 19237 pluginDevice 309
System: Vera version 1.7.4453 on Sercomm G450; loadtime 1571085134; systemReady 1571085159; Lua 5.1; JSON dkjson 1.2
Local time: 2019-10-14T22:58:45-0500;
House mode: plugin 3; system 3; tracking on
Sun data:
Geofence: not running
====================================================================================================================================
HRV Control (#342) tripped
Version 19082.18 09/24/19 22:08:41
Message/status: Tripped
Condition group "Thermostat Check" (AND) TRUE as of 09-25.07:14:49 <root>
&-T-service Thermostat (242) urn:upnp-org:serviceId:HVAC_UserOperatingMode1/ModeStatus <> Off [autochangeover => heaton at 09-30.19:09:41; T/T as of 09-25.07:14:49/09-25.07:14:49] <cond0>
&-T-group "Humidity Low" (OR) TRUE as of 09-25.07:14:49 <grph5nwrj0>
| |-T-service Humidity Sensor - B (325) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [58 => 57 at 13:35:48; T/T as of 09-25.07:14:49/09-25.07:14:49] <condh5ny5bj>
| |-T-service Humidity Sensor - H (228) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [55 => 60 at 09:53:46; T/T as of 09-25.07:14:49/09-25.07:14:49] <condh5nyj50>
Activity root.false
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
Activity root.true
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
Events
10/14/19 15:32:34 reload: notice=Luup reload
10/14/19 15:32:34 start:
Devices
Humidity Sensor - H (228) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 225; plugin -
Humidity Sensor - B (325) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 274; plugin -
Vera Connect Works W (225) urn:schemas-micasaverde-com:device:VeraConnectWWN:1 (0/-1); parent 0; plugin 8151
Thermostat (242) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 225; plugin -
Basement Motion (274) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -
OK. Everything looks good. I would make very sure that you don’t have some old logic (Lua, PLEG, scene trigger, etc.) somewhere that isn’t competing with the ReactorSensor for control of the HRV.
Your logic is perhaps a bit misleading in name because your “Humidity Low” group is actually testing to see if humidity is above a certain level (greater than 35%), so that’s “high humidity” the way I think about it. Is that correct? Do you actually expect your “Humidity Low” group to be false when humidity is under 35%/dry?
I would not use ModeStatus to check the thermostat mode, as this has some real inconsistencies in implementation with various T-stats. ModeTarget would be a better choice, I think.
In addition, a good way to make sure something gets turned on when it needs to be is to extend your logic so that you not only check if it should be on, but also if it is currently off. This requires some restructuring of your logic, but before we dive into that, make the above change for ModeTarget and see if it performs more as expected. There’s a good chance that alone will solve your issue.
thanks for the help …
I recreated the logic …
I changed the name to Househumidityhigh.
And ModeTarget is not in the drop down list (i am using a Nest T-stat).
*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.4 config 19226 cdata 19082 ui 19237 pluginDevice 309
System: Vera version 1.7.4453 on Sercomm G450; loadtime 1571115747; systemReady 1571115778; Lua 5.1; JSON dkjson 1.2
Local time: 2019-10-15T10:32:57-0500; DST=1;
House mode: plugin 1; system 1; tracking on
Sun data:
Geofence: not running
HRV Control (#342) tripped
Version 19082.7 10/15/19 10:29:51
Message/status: Tripped
Condition group “HRV Control” (AND) TRUE as of 00:18:36
&-T-service Thermostat (242) urn:upnp-org:serviceId:HVAC_UserOperatingMode1/ModeStatus <> Off [heaton at 00:18:36; T/T as of 00:18:36/00:18:36]
&-T-group “HouseHumidityHigh” (OR) TRUE as of 00:18:36
| |-T-service Humidity Sensor 1 (357) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [54 => 53 at 08:36:57; T/T as of 00:18:36/00:18:36]
| |-T-service Humidity Sensor - H (228) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [55 => 50 at 05:21:22; T/T as of 00:18:36/00:18:36]
Activity root.false
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue=“0” )
Activity root.true
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue=“1” )
Events
10/15/19 00:02:53 reload: notice=Luup reload
10/15/19 00:02:53 disabled at start-up:
10/15/19 00:18:35 action: action=SetEnabled, state=1
10/15/19 00:18:35 action: action=Restart
10/15/19 00:18:35 start:
10/15/19 00:18:36 condchange: newState=true, cond=condj7k8r7h
10/15/19 00:18:36 evalchange: newState=true, cond=condj7k8r7h
10/15/19 00:18:36 condchange: newState=true, cond=condj7kdi44
10/15/19 00:18:36 evalchange: newState=true, cond=condj7kdi44
10/15/19 00:18:36 condchange: newState=true, cond=condj7kdvcn
10/15/19 00:18:36 evalchange: newState=true, cond=condj7kdvcn
10/15/19 00:18:36 condchange: newState=true, cond=grpj7kd2cs
10/15/19 00:18:36 evalchange: newState=true, cond=grpj7kd2cs
10/15/19 00:18:36 condchange: newState=true, cond=root
10/15/19 00:18:36 evalchange: newState=true, cond=root
10/15/19 00:30:12 devicewatch: device=357, old=“57”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“56”
10/15/19 02:36:42 devicewatch: device=357, old=“56”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“55”
10/15/19 05:21:22 devicewatch: device=228, old=“55”, name=Humidity Sensor - H, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“50”
10/15/19 05:36:50 devicewatch: device=357, old=“55”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“53”
10/15/19 06:36:54 devicewatch: device=357, old=“53”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“54”
10/15/19 08:36:57 devicewatch: device=357, old=“54”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“53”
10/15/19 10:29:51 configchange:
Devices
Humidity Sensor 1 (357) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 274; plugin -
Humidity Sensor - H (228) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 225; plugin -
Vera Connect Works W (225) urn:schemas-micasaverde-com:device:VeraConnectWWN:1 (0/-1); parent 0; plugin 8151
Thermostat (242) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 225; plugin -
Basement Motion (274) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -
OK. Well, you’re just going to have to watch its behavior, then (ModeStatus values).
It’s possible that the HRV is missing the command for some reason. Another way to mitigate those kinds of problems is to restructure your logic so that you make a test of the HRV state a part of the conditions, so any time the HRV is supposed to be on (the logic you have) but it’s not on (the logic you need to add), it turns it on. That revised group structure might look like this:
- Root group – now just a container, NUL operator
- Group “Need HRV” – AND
- Device state Thermostat mode <> Off
- Group “HIgh Humidity” – OR
- Device state Humidity 1 > 35
- Device state Humidity 2 > 35
- Group “HRV On” – AND
- Device state HRV Status is FALSE
- Group State (this ReactorSensor) “Need HRV” is TRUE
- Group “Need HRV” – AND
The for activities:
- “Need HRV is FALSE” : turn off HRV
- “HRV On” is TRUE": turn on HRV
The “HRV On” group will only be true for an instant–because the activity turns the HRV on, the group goes false as soon as that happens, so you may not be able to see it make the transition in the UI status display (it’s too quick for the display refresh rate), but you’ll know it’s working because the HRV comes on.
By doing it this way, any time the HRV should be on but it’s not, the ReactorSensor will send the action to turn it on. That’s better than resetting the ReactorSensor or using a timer to try to get the behavior you want, and it handily gets around all kinds of problems like communication errors, power failures bringing things back in the wrong state, etc.
BTW, when posting logic summaries, please post the formatting characters. The first line output for the summary contains instructions to catch those.
see logic below … not working … HRV is not being turned on with high humidity.
*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.4 config 19226 cdata 19082 ui 19237 pluginDevice 309
System: Vera version 1.7.4453 on Sercomm G450; loadtime 1571115747; systemReady 1571115778; Lua 5.1; JSON dkjson 1.2
Local time: 2019-10-15T12:14:26-0500; DST=1;
House mode: plugin 1; system 1; tracking on
Sun data:
Geofence: not running
HRV Control (#342)
Version 19082.9 10/15/19 12:14:13
Message/status: Not tripped
Condition group “HRV Control” (NUL) false as of n/a
Z-T-group “Need HRV” (AND) TRUE as of 12:12:21
| &-T-service Thermostat (242) urn:upnp-org:serviceId:HVAC_UserOperatingMode1/ModeStatus <> Off [heaton at 12:12:21; T/T as of 12:12:21/12:12:21]
| &-T-group “HighHumidity” (OR) TRUE as of 12:12:21
| | |-T-service Humidity Sensor 1 (357) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [53 at 12:12:21; T/T as of 12:12:21/12:12:21]
| | |-T-service Humidity Sensor - H (228) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [50 at 12:12:21; T/T as of 12:12:21/12:12:21]
Z-T-group “HRV On” (AND) TRUE as of 12:12:21
| &-T-service HRV (189) urn:upnp-org:serviceId:SwitchPower1/Status isfalse [0 at 12:12:21; T/T as of 12:12:21/12:12:21]
| &-T-grpstate (self) (-1) Need HRV (grpj7kd2cs) istrue [true at 12:12:21; T/T as of 12:12:21/12:12:21]
Activity grpj8b307w.true
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue=“1” )
Activity grpj7kd2cs.false
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue=“0” )
Events
10/15/19 00:18:35 action: action=Restart
10/15/19 00:18:35 start:
10/15/19 00:18:36 condchange: newState=true, cond=condj7k8r7h
10/15/19 00:18:36 evalchange: newState=true, cond=condj7k8r7h
10/15/19 00:18:36 condchange: newState=true, cond=condj7kdi44
10/15/19 00:18:36 evalchange: newState=true, cond=condj7kdi44
10/15/19 00:18:36 condchange: newState=true, cond=condj7kdvcn
10/15/19 00:18:36 evalchange: newState=true, cond=condj7kdvcn
10/15/19 00:18:36 condchange: newState=true, cond=grpj7kd2cs
10/15/19 00:18:36 evalchange: newState=true, cond=grpj7kd2cs
10/15/19 00:18:36 condchange: newState=true, cond=root
10/15/19 00:18:36 evalchange: newState=true, cond=root
10/15/19 00:30:12 devicewatch: device=357, old=“57”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“56”
10/15/19 02:36:42 devicewatch: device=357, old=“56”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“55”
10/15/19 05:21:22 devicewatch: device=228, old=“55”, name=Humidity Sensor - H, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“50”
10/15/19 05:36:50 devicewatch: device=357, old=“55”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“53”
10/15/19 06:36:54 devicewatch: device=357, old=“53”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“54”
10/15/19 08:36:57 devicewatch: device=357, old=“54”, name=Humidity Sensor 1, var=urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel, new=“53”
10/15/19 10:29:51 configchange:
10/15/19 12:11:39 configchange:
10/15/19 12:11:40 condchange: newState=true, cond=grpj8b57t0
10/15/19 12:11:40 evalchange: newState=true, cond=grpj8b57t0
10/15/19 12:11:40 condchange: newState=false, cond=condj8b7bqv
10/15/19 12:11:40 evalchange: newState=false, cond=condj8b7bqv
10/15/19 12:11:40 condchange: newState=true, cond=condj8b8jbk
10/15/19 12:11:40 evalchange: newState=true, cond=condj8b8jbk
10/15/19 12:11:40 condchange: newState=false, cond=grpj8b307w
10/15/19 12:11:40 evalchange: newState=false, cond=grpj8b307w
10/15/19 12:11:40 sensorstate: state=false
10/15/19 12:11:45 action: action=SetEnabled, state=0
10/15/19 12:12:20 action: action=SetEnabled, state=1
10/15/19 12:12:20 action: action=Restart
10/15/19 12:12:20 start:
10/15/19 12:12:21 condchange: newState=true, cond=condj7k8r7h
10/15/19 12:12:21 evalchange: newState=true, cond=condj7k8r7h
10/15/19 12:12:21 condchange: newState=true, cond=condj7kdi44
10/15/19 12:12:21 evalchange: newState=true, cond=condj7kdi44
10/15/19 12:12:21 condchange: newState=true, cond=condj7kdvcn
10/15/19 12:12:21 evalchange: newState=true, cond=condj7kdvcn
10/15/19 12:12:21 condchange: newState=true, cond=grpj8b57t0
10/15/19 12:12:21 evalchange: newState=true, cond=grpj8b57t0
10/15/19 12:12:21 condchange: newState=true, cond=grpj7kd2cs
10/15/19 12:12:21 evalchange: newState=true, cond=grpj7kd2cs
10/15/19 12:12:21 condchange: newState=true, cond=condj8b7bqv
10/15/19 12:12:21 evalchange: newState=true, cond=condj8b7bqv
10/15/19 12:12:21 condchange: newState=true, cond=condj8b8jbk
10/15/19 12:12:21 evalchange: newState=true, cond=condj8b8jbk
10/15/19 12:12:21 condchange: newState=true, cond=grpj8b307w
10/15/19 12:12:21 evalchange: newState=true, cond=grpj8b307w
10/15/19 12:14:13 configchange:
Devices
Humidity Sensor 1 (357) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 274; plugin -
Humidity Sensor - H (228) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 225; plugin -
Vera Connect Works W (225) urn:schemas-micasaverde-com:device:VeraConnectWWN:1 (0/-1); parent 0; plugin 8151
ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -
Thermostat (242) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 225; plugin -
HRV (189) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -
Basement Motion (274) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -
Please repost the logic summary, following the instructions I mentioned above. When you post without the necessary codes, the formatting is broken and it makes it very difficult even for me to read. I’ll go to great lengths to ensure your success, but please don’t make it harder to do it than remote debugging already is.
It just needs a jump start because the conditions were already met when you created them, before creating the activities. Disable and enable the sensor to clear it and it should get moving. Or, turn the HRV on yourself, then back off. It should then quickly turn it back on again.
Sorry about that … here you go … I disabled and enabled and the HRV started. So if I manually turn off the HRV it should start it again given the logic below … .correct?
*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.4 config 19226 cdata 19082 ui 19237 pluginDevice 309
System: Vera version 1.7.4453 on Sercomm G450; loadtime 1571257935; systemReady 1571257960; Lua 5.1; JSON dkjson 1.2
Local time: 2019-10-16T15:58:27-0500; DST=1
House mode: plugin 1; system 1; tracking on
Sun data:
Geofence: not running
====================================================================================================================================
HRV Control (#342)
Version 19082.9 10/15/19 12:14:13
Message/status: Not tripped
Condition group "HRV Control" (NUL) false as of n/a <root>
Z-T-group "Need HRV" (AND) TRUE as of 15:57:59 <grpj7kd2cs>
| &-T-service Thermostat (242) urn:upnp-org:serviceId:HVAC_UserOperatingMode1/ModeStatus <> Off [heaton at 15:57:59; T/T as of 15:57:59/15:57:59] <condj7k8r7h>
| &-T-group "HighHumidity" (OR) TRUE as of 15:57:59 <grpj8b57t0>
| | |-T-service Humidity Sensor 1 (357) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [53 at 15:57:59; T/T as of 15:57:59/15:57:59] <condj7kdi44>
| | |-T-service Humidity Sensor - H (228) urn:micasaverde-com:serviceId:HumiditySensor1/CurrentLevel > 35 [50 at 15:57:59; T/T as of 15:57:59/15:57:59] <condj7kdvcn>
Z-F-group "HRV On" (AND) false as of 15:57:59 <grpj8b307w>
| &-F-service HRV (189) urn:upnp-org:serviceId:SwitchPower1/Status isfalse [0 => 1 at 15:57:59; F/F as of 15:57:59/15:57:59] <condj8b7bqv>
| &-T-grpstate (self) (-1) Need HRV (grpj7kd2cs) istrue [true at 15:57:59; T/T as of 15:57:59/15:57:59] <condj8b8jbk>
Activity grpj8b307w.true
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
Activity grpj7kd2cs.false
Device HRV (189) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
Events
10/16/19 15:32:35 reload: notice=Luup reload
10/16/19 15:32:35 start:
10/16/19 15:57:20 devicewatch: device=189, old="1", name=HRV, var=urn:upnp-org:serviceId:SwitchPower1/Status, new="0"
10/16/19 15:57:20 condchange: newState=true, cond=condj8b7bqv, oldState=false
10/16/19 15:57:20 evalchange: newState=true, cond=condj8b7bqv, oldState=false
10/16/19 15:57:20 condchange: newState=true, cond=grpj8b307w, oldState=false
10/16/19 15:57:20 evalchange: newState=true, cond=grpj8b307w, oldState=false
10/16/19 15:57:20 startscene: scene=grpj8b307w.true, sceneName=grpj8b307w.true
10/16/19 15:57:20 runscene: scene=grpj8b307w.true, sceneName=grpj8b307w.true, group=1, notice=Starting scene group 1
10/16/19 15:57:20 endscene: scene=grpj8b307w.true, sceneName=grpj8b307w.true
10/16/19 15:57:20 devicewatch: device=189, old="0", name=HRV, var=urn:upnp-org:serviceId:SwitchPower1/Status, new="1"
10/16/19 15:57:20 condchange: newState=false, cond=condj8b7bqv, oldState=true
10/16/19 15:57:20 evalchange: newState=false, cond=condj8b7bqv, oldState=true
10/16/19 15:57:20 condchange: newState=false, cond=grpj8b307w, oldState=true
10/16/19 15:57:20 evalchange: newState=false, cond=grpj8b307w, oldState=true
10/16/19 15:57:29 action: action=SetEnabled, state=0
10/16/19 15:57:58 action: action=SetEnabled, state=1
10/16/19 15:57:58 action: action=Restart
10/16/19 15:57:58 start:
10/16/19 15:57:59 condchange: newState=true, cond=condj7k8r7h
10/16/19 15:57:59 evalchange: newState=true, cond=condj7k8r7h
10/16/19 15:57:59 condchange: newState=true, cond=condj7kdi44
10/16/19 15:57:59 evalchange: newState=true, cond=condj7kdi44
10/16/19 15:57:59 condchange: newState=true, cond=condj7kdvcn
10/16/19 15:57:59 evalchange: newState=true, cond=condj7kdvcn
10/16/19 15:57:59 condchange: newState=true, cond=grpj8b57t0
10/16/19 15:57:59 evalchange: newState=true, cond=grpj8b57t0
10/16/19 15:57:59 condchange: newState=true, cond=grpj7kd2cs
10/16/19 15:57:59 evalchange: newState=true, cond=grpj7kd2cs
10/16/19 15:57:59 condchange: newState=true, cond=condj8b7bqv
10/16/19 15:57:59 evalchange: newState=true, cond=condj8b7bqv
10/16/19 15:57:59 condchange: newState=true, cond=condj8b8jbk
10/16/19 15:57:59 evalchange: newState=true, cond=condj8b8jbk
10/16/19 15:57:59 condchange: newState=true, cond=grpj8b307w
10/16/19 15:57:59 evalchange: newState=true, cond=grpj8b307w
10/16/19 15:57:59 startscene: scene=grpj8b307w.true, sceneName=grpj8b307w.true
10/16/19 15:57:59 runscene: scene=grpj8b307w.true, sceneName=grpj8b307w.true, group=1, notice=Starting scene group 1
10/16/19 15:57:59 endscene: scene=grpj8b307w.true, sceneName=grpj8b307w.true
10/16/19 15:57:59 devicewatch: device=189, old="0", name=HRV, var=urn:upnp-org:serviceId:SwitchPower1/Status, new="1"
10/16/19 15:57:59 condchange: newState=false, cond=condj8b7bqv, oldState=true
10/16/19 15:57:59 evalchange: newState=false, cond=condj8b7bqv, oldState=true
10/16/19 15:57:59 condchange: newState=false, cond=grpj8b307w, oldState=true
10/16/19 15:57:59 evalchange: newState=false, cond=grpj8b307w, oldState=true
Devices
Humidity Sensor 1 (357) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 274; plugin -
Humidity Sensor - H (228) urn:schemas-micasaverde-com:device:HumiditySensor:1 (16/0); parent 225; plugin -
Vera Connect Works W (225) urn:schemas-micasaverde-com:device:VeraConnectWWN:1 (0/-1); parent 0; plugin 8151
ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -
Thermostat (242) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 225; plugin -
HRV (189) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -
Basement Motion (274) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -
Yes, it looks like everything is set up correctly, and at least for the state things were in, it was doing the right thing. It should be that if you turn off the HRV, it should turn it right back on.
Okay … seems to be working as expected … will see for sure when the humidity drops to below 35%.
Thanks for your help.
1 Like
one last thing … when the reactor device is tripped it actually doesn’t indicate it is tripped. Is there anyway to have it showing tripped with the logic you provided?
I figured it out … setting the root to an OR from NULL
1 Like