Odd LogicSvr behavior

[gReatAutomation]

In my logic server I have a boolean variable called GarageOverheadDoorClosed. The variable keys off of my alarm contact and the mimolite zwave diginput.

If alarm contact is equals "Secure" the garage over head door is closed.




If the mimolite zwave diginput is FALSE the garage over head door is closed.

If BOTH are true then the garage door is closed. I then have a triggered event (Is New Field Value For) that triggers off of this variable and if the variable evaluates to TRUE then garage door is closed.




After opening the garage door and then closing it, I receive an SMS because the GarageOverheadDoorClosed variable changed form TRUE (closed) to FALSE (open) then back to TRUE (closed) when the door is closed which would trigger the SMS. 

While I am receiving the initial SMS when the door closes after being opened, I am receiving text messages several hours AFTER the garage door closed as well

[gReatAutomation]

So it seems that refreshing a driver will cause this to happen. In my case I have not used latching which it looks like I will have to do to prevent this.

[Dean Roddey]

That may not prevent it either. It will depend on where drivers treat a field coming out of an error state as a change in state, then you will get the trigger. That may be the case. That was the way everything worked historically. There's been work to move away from that, but it's not universally implemented I'm pretty sure.

The MIMO I assume you did as a field value trigger. The zone status is a standard trigger. The former are dealt with at a pretty low level and I thought I had updated the code to deal with that correctly. What is the other driver? It may be treating coming online as a status change and sending out the trigger.