Arming Envisalink panel from MSR
-
Good afternoon all,
I have a question for anyone who has experience with MSR and Envisalink/EyezOn alarm panels. The integration works fine for the most part, but there is an oddity when MSR arms the system to away. I get a notification from in the EyezOn app that says the system was armed by the last user to DISARM the system. I'd like to arm it in a way that it arms by the the user that leaves the home, which triggers the automated Arm process. I tried to do it with a dedicated user code for MSR, but it doesn't arm with that user.
This is obviously more of an annoyance, as the alarm does get armed, but the audit trail is incorrect, so I don't know who armed it. Anybody have any insight?
running latest-26193-50401535 in Docker
-
I've written an EnvisalinkController for Reactor that I use, rather than HA's integration, but result is somewhat consistent in that it's unexpected/inconsistent (I'm on an Ademco/Honeywell panel). For me, arming produces the right user ID in a partition CID event and email from EyezOn. But alas, state isn't consistent with EVL3/4, and there does not seem to be a corresponding disarm CID event, and the overall keypad message/status event (which must be used to detect disarming) doesn't seem to report the user slot that disarmed the alarm (nor do I get an email from EyezOn that the alarm was disarmed, which given no CID event, makes sense). A bit different from your results, but frustrating nonetheless.
-
Gotta love AI... this thread sent me digging on the unsolved problem, and I just decided to ask Grok why I'm getting arming CIDs but not disarms... on my panel, opening reports are off by default. Thirty seconds in programming mode to enable opening reports and there they are! So now, I have parity... correct user IDs when arming and disarming (using EnvisalinkController).
Maybe check your panel configuration and ensure both arming (closing) and disarming (opening) reports are enabled?
-
Gotta love AI... this thread sent me digging on the unsolved problem, and I just decided to ask Grok why I'm getting arming CIDs but not disarms... on my panel, opening reports are off by default. Thirty seconds in programming mode to enable opening reports and there they are! So now, I have parity... correct user IDs when arming and disarming (using EnvisalinkController).
Maybe check your panel configuration and ensure both arming (closing) and disarming (opening) reports are enabled?
@toggledbits, thanks I did look for something like that, but I might be looking in the wrong place.
FWIW, my panel is an actual EyezOn panel (UNO IP Hybrid). I had an EnvisaLink 4 with a DSC panel that took a hit and I had to replace the unit. From a HAAS/MSR perspective, the interaction is identical.
