Arming Envisalink panel from MSR

[3rdStng]

Hi @toggledbits. It appears that the race condition from this post has returned. Or maybe it's a sibling race condition?

MSR latest-21360-315df22 in docker on unRAID server for Hubitat C7 running 2.30.0.121

EDIT: I may see the cause of the issue- More below in my EDIT section. And please let me know if this is TOO much information and screenshots. Trying to make it easier for you. Thx.

I have a contact sensor report over my Echo devices when it is opened/closed, but only when the Hubitat is in it's Home state. Every once in a while this contact sensor get's stuck in the open state, as it is right now. A quick open and close resets the state, but that's a different issue.

The issue, similar to the last race condition, upon my docker restart, the Reset Reaction is announced followed by the Set Reaction. If I remove the Mode entity and restart the docker, no announcements are made.

Copy of the rule prior to docker restart (Copied to only notify on one Echo vs spam the family.)

Docker restarted - SET times changed.

Removed Mode entity and restarted Docker - Contact sensor and SET times remained.

Added Mode back in and restarted again. SET time and Home True value are set to the same time.

EDIT: I was grabbing my entire rule to show the work. No Constraints, No Local Expressions. Upon doing this, I noticed that the Mode entity has a Null value. I checked another one of my rules that uses my Mode state and that rule is also Null. As if this value is not being stored. The overview/summary page shows the value as Home, but when I edit the rule, it shows Null.

A completely different rule, not touched, yet. Showing the null value differences.

[3rdStng]

If I restart my Hubitat controller, the Entity value when editing the rule will show the current value. But if I restart my docker, it will then show a null value.

Value after HE hub reboot but before docker restart

[3rdStng]

@toggledbits posted a new blind docker build 21362 which has resolved the Mode issue. He wasn't able to test this build, but I wanted to get this update on here in case others come across it. I will mark this as SOLVED for now, even though this build was not tested by him.

[wmarcolin]

@3rdstng

Allow me my two cents, in the third situation when you return to the Hubitat mode evaluation, it is written home with the "h" in lowercase, and remember that this is a case sensitive comparison that is valid, i.e., see that in the Currente Value status the Home is with the H in uppercase, that would make your rule unfeasible.

[toggledbits]

He's got a case-insensitive test going; it'll be fine. The problem arises mostly when you send a new mode to Hubitat... that's where you need to be careful and get the case correct.