Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart

[cw-kid]

My condition is that the current set point of the Thermostat is greater than 10

The current set point is currently 10

So I'd expect this to be not ticked and not green aka false.

If I used >= then yeah OK but not when I use >

Also I am not sure I have this correct ?

I want an OR in between the two window sensors.

So if the setpoint is greater than 10 and window 1 is open OR window 2 is open then fire my action.

In PLEG I just write my condition like this:

Thermostat_SetPoint > 10.00 and (MasterBedWindow_TrippedStatus==1 or KidsBedWindow_TrippedStatus==1)

Thanks

[Elcid]

@cw-kid set up like below and with or

So top comment and any one of other comments would need to be true.

Obviously the comments would be entities

[cw-kid]

@elcid Hiya mate.

So the Thermostat's current setpoint >10 trigger that also goes in to the group or would that remain at the top like this>

Basically if the current setpoint is over 10 degrees and either of the upstairs windows are open or indeed both of them are open, then I want it to fire the HTTP command to Node-Red to do the TTS on the Google Speaker.

[Elcid]

what you have is

Themostat > 10 and (master bedroon or kidbed window open)

so for group to go true the temp has to be 11 or greater and one window has to be true

[cw-kid]

@elcid That's exactly what I wanted then. (I think)

Assuming it will fire if both windows are open also.

Or one or the other window is open.

I will test it.

Cheers.

[Elcid]

Yes will fire/go true, if one or more windows,

You can also add time condition, say you wanted to wait 60 seconds just in case some one just opened window for a few seconds.
click 3 dots for other options on trigger/condition

[cw-kid]

Its not working.

Because its not evaluating the current set point properly it seems.

I set it to 9 which is less than 10 but its still true when it should be false

[cw-kid]

@elcid said in Why is this Green and ticked when its not true ? And how to do OR:

You can also add time condition, say you wanted to wait 60 seconds just in case some one just opened window for a few seconds

That's a good idea. I see the extra options but not sure where to stick in my 60 second delay without breaking it even more LOL

[Elcid]

use sustained for so windows have to be open the sustained time.

Your group appears to be working as it is true. What are your reactions

[cw-kid]

@elcid said in Why is this Green and ticked when its not true ? And how to do OR:

Your group appears to be working as it is true. What are your reactions

It shouldn't be true though, it should be false if its not > than 10

So how can it be true when the thermostat is set to 9 ?

Reactions ? You mean what is my action ?

It just sends a HTTP GET request out.

[cw-kid]

Its not clear. It says "False" at the top in the blue bar.

But its green and ticked.

The current set point is 9.

My trigger is >10

So why is it green and ticked ?

If I open a window now it runs the action when it shouldn't because the heating is off as its currently 10 or less.

I only want the action to run when the heating is on - setpoint is greater than 10.

[toggledbits]

Reminder: this is the first time this code has run in anyone's hands other than mine. It is also several years less used and tested than Vera Reactor.

There is a bug in numeric comparisons, and it will be fixed for today's build (later this evening).

[cw-kid]

Thought it was me again doing something stupid.

[cw-kid]

How do we update the Raspberry Pi installation when you release an update ?

[toggledbits]

No it's me. So sorry. Updates are easy. All you need to do is stop Reactor, un-tar the release package in the reactor directory, and don't run the install script. Just start Reactor again. That will leave your config files intact (the script shouldn't clobber them anyway, but then, 9 isn't greater than 10, is it? Sigh....)

[cw-kid]

@toggledbits Hi

Was this fixed in the 21050 release ?

Thank you.

[cw-kid]

@toggledbits said in Why is this Green and ticked when its not true ? And how to do OR:

but then, 9 isn't greater than 10, is it? Sigh..

No LOL I was having a blonde moment

[toggledbits]

@cw-kid said in Why is this Green and ticked when its not true ? And how to do OR:

No LOL I was having a blonde moment

Then I must have been having an early senior moment when I leaked that one. Sheesh.

I do believe that all of the numeric comparisons are working now.

[cw-kid]

@toggledbits Just updated to 0.1.21051 and I can confirm its now working with my Thermostat and the trigger >10

10 or below is false and 11 or above is true.

Thank you