Not sure what is going on, but that seems like the normal messages that come from the system are not being sent correctly, I would say fiddle with encryption settings to see what happens? Basically the alarm system is the one initiating contact and sending stuff, the package and therefore HA just respond.
Did anyone get this integration working? I am trying to install now, but keep getting an error; unless somebody can help?
Information on issue
https://github.com/corvis/homeassistant_ajax_security/issues
Looks good to me, I will have a play tonight and if happy I will make the changes to the guide!
I just installed 2023.1.0. It seems there is a regression. When alarm is armed (armed_away) state of the four zones is set to armed_away but interface icons are set to green instead of red
Likewise, when alarm is disarmed, state of the four zones is set to disarmed but interface icons are set to sort of grey instead of green
It is confirmed?
Hi all. After 2023.1, the state of the āSia alarmā device is always āunavailableā even if the connection status is āconnectedā and events are coming to HA (checked with events listening service into developer tools). Nothing changes if I activate/deactivate the alarm. Are other people experimenting the same situation ? Thank you for your support
on my side as explained above, states are correctly reported but the icon status is wrong; I made a PR, no feedback yet.
It is interesting, I am not seeing this behaviour and there has been no change in SIA, so it might be a change in either alarm_control_panels or the visualization of thoseā¦
Thanks. How could we tackle this issue? Nothing is reported in logs, how could I help?
@eavanvalkenburg I took a little piece of log. You can find hereunder.
Maybe could be useful for your debugging.
Tell us if you need something more.
Thank you for your support.
2023-01-10 22:01:19.378 WARNING (MainThread) [pysiaalarm.base_server] Code not found, replying with DUH to account: 001
....
2023-01-10 22:01:30.428 WARNING (MainThread) [pysiaalarm.base_server] Code not found, replying with DUH to account: 001
.....
2023-01-10 22:01:43.915 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: 0F310038"SIA-DCS"4613L0#001[#001|Nri1/PE502]_21:01:23,01-10-2023
2023-01-10 22:01:43.916 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': '001', 'ti': None, 'id': None, 'ri': '1', 'code': 'PE', 'message': '502', 'xdata': None, 'timestamp': '21:01:23,01-10-2023'}
2023-01-10 22:01:43.922 WARNING (MainThread) [pysiaalarm.base_server] Code not found, replying with DUH to account: 001
I should have said that I logged an issue on github: https://github.com/home-assistant/core/issues/85386. If you think it may be due to a change in alarm panel, is it the right place to post the issue? Could someone take ownership?
Hi all ā¦ something changes without no actions by my side. Now state and attributes are corrected. ā¦ mystery
Isnāt this just as a result of a colour scheme change within HA?
If so, how could we recover it? I just have no clue knowing that Iām using regular alarm control panels that are created by SIA integration
Beside the icon color defect, I noticed that alarm control panels get disconnected very often which never occurred before. It has been running flawlessly for months. After I upgraded to 2013.1.0, it turns out that a few days later hub+ firmware got automatically upgraded as well. It is now running EU 2.14.0. So it is quite hard to make an assumption on what made this regression. To be honest Iām not very keen to downgrade.
EDIT
I must add that Iām using the default theme. I set-up now card_mod as a workaround. Here is the code. However I havenāt found yet how to do it for the button of the main alarm control panel.One step at a time 
- type: glance
show_state: false
entities:
- entity: alarm_control_panel.5656_ccc_zone_3_alarm
card_mod:
style: |
:host {
--card-mod-icon-color:
{% if is_state("alarm_control_panel.5656_ccc_zone_3_alarm", "disarmed") %}
green
{% else %}
orangered
{% endif %}
}
- entity: alarm_control_panel.5656_ccc_zone_2_alarm
card_mod:
style: |
:host {
--card-mod-icon-color:
{% if is_state("alarm_control_panel.5656_ccc_zone_2_alarm", "disarmed") %}
green
{% else %}
orangered
{% endif %}
}
- entity: alarm_control_panel.5656_ccc_zone_4_alarm
card_mod:
style: |
:host {
--card-mod-icon-color:
{% if is_state("alarm_control_panel.5656_ccc_zone_4_alarm", "disarmed") %}
green
{% else %}
orangered
{% endif %}
}
- entity: alarm_control_panel.5656_ccc_zone_1_alarm
card_mod:
style: |
:host {
--card-mod-icon-color:
{% if is_state("alarm_control_panel.5656_ccc_zone_1_alarm", "disarmed") %}
green
{% else %}
orangered
{% endif %}
}
title: Alarme
columns: 2
EDIT2: for those interested by the solution see this post change background color
Whatās happened to this integeration? Itās totally unrealiable now. I keep getting āUnavaiableā status and in my logs this morning itās even got an entry as being Disarmed and shut down my wifi cameras.
Itās completely screwed for me as well. So unreliable is it that somehow itās decided that my system was disarmed and turned off my cameras about 10 minutes after I left theh house.
by any chance did you reboot HA?
Please also check with Ajax, because there were no code changes to the SIA integration so this is either a issue with Ajax (and mine still works fine) or something generic in HA or particular to your setupā¦
I have emailed Ajax support to ask if there is any issue.
I started having issues with this with the last December update of HA and it has followed through to the January builds.
Nothing has changed with the integration.
Only 32 minutes ago did it go to Unavailable again and it triggered some automatons that are only supposed to go on when the alarm is armed. So this is very concerning.
Another thing, the dashboard Alarm card doesnāt always reflect the status of the entity.
did you try to reboot HA?