v0.6.3

Tamper events in the activity log

Home Assistant integration 0.6.3 · bridge firmware 0.9.2 (unchanged)

• Zone event entities now emit tampered and tamper_restored when a sensor's cover switch changes, and the panel event entity emits panel_tampered / panel_tamper_restored for the enclosure.
• A transition is only reported once both the previous and current values are known, so a bridge or Home Assistant restart never logs a tamper that did not happen.
• Dashboards that list the bridge's event entities, such as the Recent activity logbook card, show tampers with no filter change.

Requires bridge firmware 0.9.2 for live tamper detection.

See #11.

v0.6.2

Robust zone state tracking, live sensor tamper, loss diagnostics

Home Assistant integration 0.6.2 · bridge firmware 0.9.2

Addresses occasionally missed sensor state changes and adds live sensor tamper.

Zone open/closed

• The 345 MHz status byte is decoded per zone: only the loop bit matching the zone's programmed input means open (0x80 loop 1, 0x20 loop 2, 0x10 loop 3). Doors on loop 2 report A0 open / 80 closed; the previous bit-7 assumption marked them open on every packet, including tamper and battery changes.
• The alarm engine's EVENT_ZONE_OPENED OPEN/CLOSE line is now a third independent source alongside the RF packet and the Zone N OPENED/RESTORED text.
• Every transition is queued and published in order ahead of everything else, so a fast open-then-close reaches Home Assistant as ON then OFF.

Sensor tamper, now live

• Packet bit 0x40 (verified: C0 tampered/closed, E0 tampered/open), the Zone N TAMPERED / TAMPER RESTORE / TAMPER DETECTED / TAMPER restored lines, and the live trouble_memory_add / trouble_memory_restore lines (also low battery and loss of supervision). Panel enclosure tamper is live as well.

New diagnostic sensors

• UART receive errors, MQTT reconnects, and Zone poll corrections (increments whenever the 30 s poll finds a state the live lines missed).

Stall reduction

• Panel UART receive buffer 8 KB → 32 KB; USB serial logging no longer blocks the loop.

Firmware must be updated to 0.9.2.

See #10.

v0.6.1

Panel command queue

Home Assistant integration 0.6.1 · bridge firmware 0.9.1

• Protected bridge commands (arm, disarm, bypass, zone chime, volume) that arrive while one is already in flight are now queued, eight deep with duplicates collapsed, and sent one at a time through the bridge's command-pacing gate. Previously the second command in a burst was dropped, so an automation that changed two zones' chime only changed the first.
• No new blocking or hold-off behaviour. The existing "value already matches the panel, skip the write" check is unchanged.
• Integration version bumped to match; no integration code changes.

Firmware must be updated to 0.9.1 for the queue.

See #9.

v0.6.0

Per-zone chime control

Home Assistant integration 0.6.0 · bridge firmware 0.9.0

• One select entity per zone with the panel's six chime types (Off, Voice, Voice and ding-dong, Loud ding-dong, Voice and loud ding-dong, Ding-dong), read back from the panel's zone programming table.
• New bridge command topic panel/zone_chime/set ({"zone":N,"mode":M}) mapped to the console's zone_chime <zone> <mode> command through the protected, unlock-supervised path.
• Requests that already match the panel's current value are skipped so automations never cause needless settings-flash commits.
• The zone table is re-read shortly after each change so the new value is confirmed from the panel, not the command echo.
• Manifest advertises zone_chime_control.

Firmware must be updated to 0.9.0 for the chime selectors to become available.

See #8 for details.