Skip to content
Home Assistant TestFlight
AlarmDecoder

AlarmDecoder AD2 via ser2sock

Security Systems · Security

WorksLocal

1 report: 1 says it works.

Reported with 1 integration: AlarmDecoder.

What people report

IntegrationIn Home AssistantIn Apple HomeWhat they saidSource
AlarmDecoderWorks LocalInit failure fixed by firmware update and reload
Saved copy
The problem On startup, the AlarmDecoder module attempts to initialize the ad2 module (in my case using ser2sock) and sends a config string (output of monitoring the connection attempt): !CONFIG>ADDRESS=17&CONFIGBITS=ff02&LRR=Y&EXP=NYNNN&REL=YYYY&MASK=eaeaead0&DEDUPLICATE=N !RFX:0852429,00 !VER:00000666,V2.2a.6,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;LR;KE;MK;CB The following error is generated by the AlarmDecoder integration: 2021-07-10 14:54:38 WARNING (Thread-43) [homeassistant.components.alarmdecoder] AlarmDecoder unexpectedly lost connection 2021-07-10 14:54:38 ERROR (Thread-43) [root] …

Excerpt saved from GitHub on 2026-10-23.

Issue #52854 · 2021-07

Each row is one report from a GitHub thread, an integration’s docs, or r/homeassistant. Check the date and the linked source before you buy.

In ReReHome

Once Home Assistant’s HomeKit Bridge shares it, this device reaches Apple Home as a HomeKit accessory behind your Home Assistant bridge, so ReReHome shows and controls it like any other.

Identifiers

BrandAlarmDecoder
CategorySecurity Systems