[SOLVED] OH3 Vista20p Ademco Binding - unable to disable chimemode

Having trouble with the Ademco Binding for OH3 when trying to disable Chime Mode.

The odd thing is that ChimeMode can be enabled with the binding just fine. So it leads me to question is the correct command being sent by the binding?

Below is the debug output. The on command receives an ACK where as the off never does and the state never changes:

  • Item ‘Partition1_PartitionChimeMode’ changed from ON to OFF
    14:15:10.365 [DEBUG] [ternal.handler.PartitionBridgeHandler] - Sending XXXX1
    14:15:10.365 [DEBUG] [ernal.handler.EnvisalinkBridgeHandler] - write(): “12341”
    14:15:10.366 [DEBUG] [ernal.handler.EnvisalinkBridgeHandler] - Wait For ACK
    14:15:10.830 [DEBUG] [ernal.handler.EnvisalinkBridgeHandler] - read(): “%00,01,1C28,08,00, DISARMED CHIME Ready to Arm $”
    14:15:10.831 [DEBUG] [ernal.handler.EnvisalinkBridgeHandler] - Command 0 received
    14:15:10.831 [DEBUG] [ernal.handler.EnvisalinkBridgeHandler] - got input 01,1C28,08,00, DISARMED CHIME Ready to Arm
    14:15:10.832 [DEBUG] [ternal.handler.PartitionBridgeHandler] - Decoding lastMessage: DISARMED CHIME Ready to Arm
    14:15:10.832 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Partition1_PartitionChimeMode’ changed from OFF to ON

Environment details:
OH3 in Docker container
Envisalink 4
Ademco Binding manually installed

The updated jar file is from this form discussion: Openhab and Envisalink Vista / Honeywell Alarm - #49 by eusblh

Anyone have any suggestions?

Or does anyone know how I can get started on learning to create/modify bindings?

Resolved in the updated jar file. The Chime functionality was not sending the proper disable string.

Where is that updated JAR file?

Best, Jay


@basriram updated the code and is hosting it in his Github.

1 Like

I’m getting this now with the 3.4 version vs. the 3.2 version I had running.

I’m running OH 3.2, not sure if that is the issue or not? I did restart OH from scratch.

2022-10-13 07:39:23.647 [WARN ] [ng.ademco.internal.handler.EnvisalinkBridgeHandler] - No pulse seen for the last 1 minutes
2022-10-13 07:40:28.649 [WARN ] [ng.ademco.internal.handler.EnvisalinkBridgeHandler] - No pulse seen for the last 1 minutes

Best, Jay

I don’t see any of those warnings but I am not the best at debugging with OH yet.

I am however running 3.3.

My guess is OH 3.2 and OH 3.3 environments are different hence that error I was seeing. I rolled back until I upgrade OH to 3.3.

Best, Jay

Hey @basriram and @dubbleb,

Can someone re-compile the Ademco binding against the 4.x framework? I finally upgraded to OH 4.x and the binding doesn’t work now. All the Things are online but OH can’t talk to the unit because of this issue below.

2023-11-17 22:08:08.363 [WARN ] [ng.ademco.internal.handler.EnvisalinkBridgeHandler] - No pulse seen for the last 1 minutes
2023-11-17 22:09:13.364 [WARN ] [ng.ademco.internal.handler.EnvisalinkBridgeHandler] - No pulse seen for the last 1 minutes
2023-11-17 22:10:18.366 [WARN ] [ng.ademco.internal.handler.EnvisalinkBridgeHandler] - No pulse seen for the last 1 minutes

Best, Jay

Hey Jay - I believe you should be using the currently supported binding Alarm Decoder for a vista20p. This is what I use and it is built in / working with openhab 4.0. Hope that helps.