Alarm Decoder integration sporadically outputs false readings and toggles sensors between open/closed until integration is reloaded

[Robrowski]

The problem

For the past few months (not sure when it started) Alarm Decoder has occasionally gotten into a mode where it falsely reports state changes for a few zones (not all) until it is reloaded. These zones are typically my hardwired contact sensors, which were easy for me to verify were fully in the closed or opened state. Before reloading, AD would report state changes regularly about every 4 seconds, then after reload would operate perfectly.

I don't know how to reproduce this, and it does not seem correlated with boot up.

What version of Home Assistant Core has the issue?

core-2024.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Alarm Decoder

Link to integration documentation on our website

https://www.home-assistant.io/integrations/alarmdecoder

Diagnostics information

No error messages or log messages ever seem to be generated. The state just toggles for a couple of sensors about every 4 seconds. For example, the hardwired door sensor will toggle regularly despite the door being wide open.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

This seem similar in theme to https://github.com/home-assistant/core/issues/63158

[home-assistant[bot]]

alarmdecoder documentation alarmdecoder source

[jscongdon]

I have not seen this on my installation. You should check what the Alarmdecoder is doing. I do not know your installation, but I can do this with the AD2Pi installed on a RasPi. SSHing into the Pi, screen the serial connection `screen /dev/ttys0 115200'. With any sensor state changes, you will see the output. When you see the issue on your HA, perform that step and see what is being reported. If what is being reported on the AlarmDecoder side matches the HA output, the issue is on your security panel side. And if this only happens when a contact is in the open state, you may have an issue with an EOL resistor.

**UPDATE: Once you enter the screen, it will cut the serial comms to the Pi, I can't remember what needs to be restarted to activate it again, but I just reboot the Pi.