Conditional triggers with required expression

📐 Rule Machine®
1

Create rules using two triggers and required expression

image
image1920×1080 448 KB

The problem is that after 10 pm which stop triggers ,something happens to the rule and will no longer trigger when the required expression allows triggers again at 6:30 am. It will show decreased trigger as true and increased trigger as false. I have to update the rule to reset the issue a simple start stop does not reset it. here is the log. It appears that the triggers are acting more as a "and" instead of an "or" condition. Any thoughts on the issue is much appreciated.

app:7382024-01-30 08:01:09.563 AMinfoInitialized
app:7382024-01-30 08:01:09.185 AMinfoUpdated: Required Expression now true
app:7382024-01-30 08:01:09.061 AMinfoScheduled: between 6:30 AM and 10:00 PM
app:7382024-01-30 08:01:09.034 AMinfoScheduled: between 6:30 AM and 10:00 PM
app:7382024-01-30 08:00:00.930 AMinfoNot triggered: Condition Temperature of sunroom(65.0) is >= SpanLow(68) FALSE
app:7382024-01-30 08:00:00.801 AMinfoEvent: sunroom temperature 65.0
app:7382024-01-30 07:50:01.243 AMinfoNot triggered: Condition Temperature of sunroom(64.9) is >= SpanLow(68) FALSE
app:7382024-01-30 07:50:01.096 AMinfoEvent: sunroom temperature 64.9
app:7382024-01-30 07:35:01.169 AMinfoNot triggered: Condition Temperature of sunroom(64.7) is >= SpanLow(68) FALSE
app:7382024-01-30 07:35:01.023 AMinfoEvent: sunroom temperature 64.7
app:7382024-01-30 07:30:01.116 AMinfoNot triggered: Condition Temperature of sunroom(64.5) is >= SpanLow(68) FALSE
app:7382024-01-30 07:30:01.053 AMinfoEvent: sunroom temperature 64.5
app:7382024-01-30 07:05:01.376 AMinfoNot triggered: Condition Temperature of sunroom(64.4) is >= SpanLow(68) FALSE
app:7382024-01-30 07:05:01.318 AMinfoEvent: sunroom temperature 64.4
app:7382024-01-30 07:00:01.248 AMinfoNot triggered: Condition Temperature of sunroom(64.3) is >= SpanLow(68) FALSE
app:7382024-01-30 07:00:01.112 AMinfoEvent: sunroom temperature 64.3
app:7382024-01-30 06:55:01.346 AMinfoNot triggered: Condition Temperature of sunroom(64.2) is >= SpanLow(68) FALSE
app:7382024-01-30 06:55:01.150 AMinfoEvent: sunroom temperature 64.2
app:7382024-01-30 06:45:01.792 AMinfoNot triggered: Condition Temperature of sunroom(64.1) is >= SpanLow(68) FALSE
app:7382024-01-30 06:45:01.735 AMinfoEvent: sunroom temperature 64.1
app:7382024-01-30 06:30:01.331 AMinfoRequired Expression now true
app:7382024-01-30 06:30:01.329 AMinfoEvent: null null null
app:7382024-01-30 06:30:00.889 AMinfoScheduled: between 6:30 AM and 10:00 PM
app:7382024-01-30 06:30:00.843 AMinfoScheduled: between 6:30 AM and 10:00 PM
app:7382024-01-29 10:00:00.824 PMinfoRequired Expression now false
app:7382024-01-29 10:00:00.823 PMinfoEvent: null null null
app:7382024-01-29 09:55:06.486 PMinfoRequired Expression now true
app:7382024-01-29 09:55:06.354 PMinfoScheduled: between 6:30 AM and 10:00 PM
app:7382024-01-29 09:55:06.320 PMinfoScheduled: between 6:30 AM and 10:00 PM
app:7382024-01-29 09:55:04.506 PMinfoAction: Set Private Boolean(false) True

2

It may be good to see the entire rule.

But without that, I suspect you might be running into problems for having two triggers for the same attribute on the same device, See the note in: Rule 5.1 | Hubitat Documentation

It might also be good to explain what you are trying to do, Off hand, I can't tell a reason this might be different from a plain "changed" trigger (though I suppose it depends on what's going on with that variable), which would also avoid this problem.

3

Thanks for reply. I removed all the conditional triggers for my rule and handled the conditions in the rule. The concept is "control an auxularly heater in sunroom, with temperature set point obtained from ecobee heat setpoint, between hours of 6:30 am and 10:00 pm, using ecobee sensor in sunroom,sonos s40 plug to control dumb heater . The ecobee polls every 5 mins. Basicly a thermostat. The contional triggers was an attempt to control varations in temperature in sunroom (a bit of traffic in and out the door) . i tried the increased and decrease by x trigger; however i think the base is reset on every update, so didnt work for my application. So I left the trigger as increase or decreased as you pointed out same as changed, if it would have worked. Removed the conditional time trigger as it left heater on after 10 ( no trigger ). So now every thing is handled in rule based on triggers from sensor changes and ecobee heat setpoint changes. With safe guard rules on overtemp and switch not responding open or closed announced on Alexa dot and iphones. Maybe a current sensor plug is in a future upgrade..

A side note on s40 plug its not happy on hubitat zigbee radio. Kept dropping off. Moving the hub around and adding additional repeater devices changed links on zigbee map but wasn't stable. I gave up and put it on the HUE, stable now no issues, lot of repeater devices there. I have a few of the s40 on the hue, I use " all 4 hue" to make rules for plugs (very limited) before purchasing the Hubitat. All the plugs are controlled by hubitat rules.. Basic control from hue app, smarter control from hubitat rules and dashboard, voice control through Alexa using either.