Howdy,
My system:
-- Honeywell vista 20P (PROM v10.23)
-- 6160 keypad
-- EnvisaLink 4 (version 182)
-- Home Assistant
At the moment, through the TPI interface no zone change events are being sent. Only through the zone dump are the zone status updated.
Though recently I enabled syslog reporting and the zone change events are received immediately.
At the moment, I am not concerned when a zone is restored (closed) (I understand the limitation outlined in section 3.5 of the docs) rather seek to receive immediate reporting when a zone is faulted (open). Looking for confirmation if this type of reporting should work via the TPI interface for Honeywell vista systems? If yes, might there be a bug the current version of the EnvisaLink firmware? I would be more than happy to perform any necessary tests.
At this time I am at the point to where I can further invest in the Honeywell system or move over to a DSC. Though key here to keeping the Honeywell setup is to simply get the zone reporting to work.
Thanks!
Zone change events missing in TPI interface
Moderators: EyezOnRich, GrandWizard
-
- Posts: 3
- Joined: Sat Sep 19, 2020 3:04 am
Re: Zone change events missing in TPI interface
I just updated my EVL4 to 182 to test this as I have an identical setup, it was working on 1.3.164
Yes, the HA UI should report state changes of the zone within 1s of opening.
Yes, the HA UI should report state changes of the zone within 1s of opening.
Re: Zone change events missing in TPI interface
This is happening for me too. Is there a way to downgrade my firmware to 164 or another version where this still works? This is the key feature that I bought the Envisalink for...
Re: Zone change events missing in TPI interface
Here is tracing from the library that I'm using showing that the zone update commands aren't being sent (zone 2 was opened at :46 and closed at :49).
Code: Select all
2022-01-06 16:01:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < %00,01,5008,17,00,LOBAT 17 $
2022-01-06 16:01:42 DEBUG (MainThread) [pyenvisalink.honeywell_client] Data received:%00,01,5008,17,00,LOBAT 17 $
2022-01-06 16:01:42 DEBUG (MainThread) [pyenvisalink.honeywell_client] Code:%00 Data:01,5008,17,00,LOBAT 17
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < %02,0300000000000000$
%00,01,0008,02,00,FAULT 02 FRONT DOOR $
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.honeywell_client] Data received:%02,0300000000000000$
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.honeywell_client] Code:%02 Data:0300000000000000
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: %02 with data: 0300000000000000
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.honeywell_client] Parition 1 is in state NOT_READY
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.honeywell_client] Data received:%00,01,0008,02,00,FAULT 02 FRONT DOOR $
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.honeywell_client] Code:%00 Data:01,0008,02,00,FAULT 02 FRONT DOOR
2022-01-06 16:01:46 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_keypad_update for code: %00 with data: 01,0008,02,00,FAULT 02 FRONT DOOR
2022-01-06 16:01:49 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < %02,0100000000000000$
%00,01,5008,17,00,LOBAT 17 $
2022-01-06 16:01:49 DEBUG (MainThread) [pyenvisalink.honeywell_client] Data received:%02,0100000000000000$
2022-01-06 16:01:49 DEBUG (MainThread) [pyenvisalink.honeywell_client] Code:%02 Data:0100000000000000
2022-01-06 16:01:49 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: %02 with data: 0100000000000000
2022-01-06 16:01:49 DEBUG (MainThread) [pyenvisalink.honeywell_client] Parition 1 is in state READY
Re: Zone change events missing in TPI interface
That's an old bug that was introduced back in 1.2.145 (~2018). It only surfaces if you have one zone opening and closing, that's why it sailed through automated testing without being detected. The bug was in 1.3.164 too.
It's fixed in pre-release 1.4.185 which will not be formally released as its part of a bigger package coming out in Q1 2022. You can ask your service provider for a manual update. For eyezon email their support, for others contact your dealer or facilities manager.
K
It's fixed in pre-release 1.4.185 which will not be formally released as its part of a bigger package coming out in Q1 2022. You can ask your service provider for a manual update. For eyezon email their support, for others contact your dealer or facilities manager.
K