-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zone program mode (*56) incorrectly changes state of binary sensor alarm zone #94
Comments
Also applies to *58 (expert zone program mode) and *82 (alpha descriptor programming), as well as probably plenty of other places in program mode. |
Zone updates are currently driven by the virtual keypad updates that the EVL sends. From the log it looks like entering program mode sends keypad updates that include zone information with the integration is likely interpreting as valid zone updates. I'm not sure yet whether I'll be able to filter those out based on the information available from the EVL. But from what I can tell from the logs, while I see it triggering a state update, it doesn't look like it's actually changing the zone's state value. I see your automation triggering though so I'm curious what your triggers and conditions look like for the automations. |
Here's a quick video of showing this. You can clearly see that going into program mode and going into zone 1 is changing the state of the binary sensor for zone 1. Same thing would happen if I went into program mode for another zone, the respective zone would also have a state change. As far as the automations go, the triggers are very plain and boring. There are no conditions on the automation, just the triggers.
and
Untitled.video.-.Made.with.Clipchamp.2.mp4 |
@philh30 Do you have any thoughts on this? It looks like |
so off topic but what card did you use to control your panel like a keypad? that video |
https://community.home-assistant.io/t/honeywell-vista-20p-full-keypad-via-envisalink/690039/2 |
@bdf0506 Just FYI, I haven't forgotten about this - I'm just not quite sure what to do about it. From my comment above, it might be possible to adjust the zone update handling but I'm a bit worried about it breaking other scenarios that are already working (there's a whole complicated history around this - some of which is detailed in #9). |
I have an Envisalink 4 on a Honeywell Vista 20p system. If you go into zone program mode (*56), whenever you select the zone, it will change the state of the binary sensor for that zone, even though that binary sensor has not actually been tripped. So in my case, I have a few automations when zone 1 (fire) triggers and clears. Simply going into zone program mode will change the binary sensor from fire from off to on. Since when you go into zone program mode, it defaults to zone 1, each time that you go into zone program mode, it will change the state of the fire sensor - and if you enter another zone number, that one will now also flip from off to on. Unsure if this is actually a problem with this Envisalink module for HA, or perhaps it is something upstream in the pyenvisalink package.
To reproduce:
I do have syslog enabled on the Envisalink config. When this condition happens, the syslog is clear, there is no reference to Zone 1 opening.
Relevant debug log:
Full debug logs:
The text was updated successfully, but these errors were encountered: