SIA — Ajax Alarm status is constantly triggered

[rock3r]

The problem

I have an Ajax Systems alarm. I connected it via the SIA integration to HA. The integration seems to work, but it constantly shows the alarm status as Triggered, regardless of what the actual status is.

What version of Home Assistant Core has the issue?

core-2024.7.4

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

SIA Alarm Systems

Link to integration documentation on our website

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

Diagnostics information

home-assistant_sia_2024-08-03T16-47-50.071Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I can't see any reference to the device (ajax_systems_alarm_status) in the debug log, even after restarting the integration.

Additional information

This used to work, but it stopped working ~1-2 months ago.

[home-assistant[bot]]

Hey there @eavanvalkenburg, mind taking a look at this issue as it has been labeled with an integration (sia) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of sia can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign sia Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

sia documentation sia source _{^{(message by IssueLinks)}}

[karlblum]

I have the exact same issue.

Ajax security hub seems to send code RP to HASS every few seconds:

2024-10-15 09:49:29.185 DEBUG (MainThread) [homeassistant.components.sia.entity] Received event: Content: #007|Nri0/RP0000]_06:49:28,10-15-2024, Zone (ri): 0, Code: RP, Message: 0000, Account: 007, Receiver: None, Line: L0, Timestamp: 2024-10-15 06:49:28+00:00, Length: 0039, Sequence: 1087, CRC: 0C77, Calc CRC: 0C77, Encrypted Content: None, Full Message: "SIA-DCS"1087L0#007[#007|Nri0/RP0000]_06:49:28,10-15-2024. 2024-10-15 09:50:29.243 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: 6D050039"SIA-DCS"1088L0#007[#007|Nri0/RP0000]_06:50:28,10-15-2024 2024-10-15 09:50:29.243 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': '007', 'ti': None, 'id': None, 'ri': '0', 'code': 'RP', 'message': '0000', 'xdata': None, 'timestamp': '06:50:28,10-15-2024'}

When you arm and disarm, then Ajax will send CL and OP signals accordingly. Then the issue is resolved. It seems that for some reason the state becomes faulty in HASS and it waits for OP signal (Open/Disarm).

It started happening a few months ago.

[olivierfaber]

I have the same issue, but the RP messages (automatic test - interval is 1 minute but you change it in the Ajax settings) were always there. I checked with Ajax and they told me there were no changes in the SIA protocol in the last few months.

In my case, this issue was triggerd by using the wrong pin on my keypad a few times. The keypad locks & the Ajax hub sends a RL code (reader locked). This SIA implementation does not recognise the RL code, sends a DUH message back to Ajax. That triggers the Ajax hub to disconnect and reconnect and try again, it loops from there.

2024-10-21 16:56:09.345 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': 'REDACTED', 'ti': None, 'id': None, 'ri': '1', 'code': 'RL', 'message': '3', 'xdata': None, 'timestamp': '14:57:32,10-21-2024'} 2024-10-21 16:56:09.349 WARNING (MainThread) [pysiaalarm.base_server] Code not found, replying with DUH to account: D46867

My workaround to get it out of this loop is to disable the ethernet channel in the sia settings of the Ajax system for a second and enabling it again. This clears the Ajax hub of pending messages.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.