hmm strange and is that with the newest beta version (see here: Ajax alarm system)?
Now i have installed the latest beta (v0.3.2b), but now even less logging 
. I am wondering if my setup is done correctly:
After the config flow it gives the following:
The sensors are not updated and no further logging to be found, even after a reboot.
so the component actually waits for messages from the alarm system, so if there is nothing happening, then you wouldn’t see anything change, that is how the protocol works. However in the ajax system that I have there is a setting for the ping_interval, which is basically the alarm system letting a monitoring station now it is still online, is that set somewhere in your alarm as well?
These are all the available settings on the Alarm:
You can see that in the Utcar docker container i used, there is a ‘Heartbeat’ recieved every minute so the Alarm works. Should that not be visible in the component logging normally?
I also tried setting/ triggering the alarm but no go .
Hello
An API exist but it is necessary to obtain specific access from ajax
I want to share my few lines for managing Ajax with esp32 board + this SIA integration.
Big thanks to @fireon and @eavanvalkenburg
Will be happy if it helps someone.
https://github.com/akarpenkoua/ajax-spacecontrol-esphome
4 Likes
Thanks for the kudos and happy that it helped!
PS. Your repo on Github seems to be private so the link reports a 404 
I have some issues after upgrading to 112.1 and newly released Ajax integration 0.3.2. When I hover the red icon it says (translated) “Reset”.
The status icon for the alarm that I had in my dashboard that usually says “Armed/Disarmed” now says “Unavailable”.
Not really sure how to help identify this as I haven’t seen anything when looking in the logs, but if there is any information I can provide please let me know.
Edit: I can also see that in the Ajax app it says “Not connected” when looking under the Hub and (translated) “Security central”.
Edit again: Downgrading to 0.2.4 solved the issue.
Hi, I just upgraded my own to 0.112.1 and with SIA 0.3.2 and everything works, you might have to make a slight change in your system so it retries the connection, I have heard that sometimes if a alarm system can’t reach the server (in this case HA) it doesn’t retry but just goes offline, so if the upgrade took a long time and it wasn’t able to reach it, but that doesn’t explain why downgrading does work, could you run some logging for it?
I have a small database so upgrade to 112.1 went fast. I’m happy to debug if you explain it to me like you would explain to your grandma since I’ve never tried debugging before 
sure, enable this in your configuration.yaml https://www.home-assistant.io/integrations/logger/
with custom_components.sia: debug
as one of the rows, and then in your Logs (now in Configuration under Logs) you should be able to see something going on and make sure to reupgrade to 0.3.2 because the old one I don’t want to do something with anymore.
Like this?
logger:
default: info
logs:
custom_components.sia: debug
Under Configuration > Logs there is nothing SIA related. There are 335 entries in the complete log but can’t say I found anything alerting. What should I look for?
Noticed now that this one went from “Disconnected” to “Connected” now all of a sudden:
that means there is nothing coming from the alarm, maybe put default to warning to you only see sia. and then maybe try to make a slight settings change in your alarm
Changed debug setting to “warning” and now the log only has the following about SIA:
2020-07-03 17:11:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for sia which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
In the Ajax app the connection is “Disconnected” again now.
I changed the configuration setting “Account” just to “touch” the settings but no difference.
Configuration.yaml:
sia:
port: 8124
hubs:
- name: AJAX
account: BEA
ping_interval: 5
zones:
- zone: 1
name: Hemmet
sensors:
- alarm
- smoke
sorry, for the new component you have to setup through a config flow, if you go to integrations and add it there it should connect, you can delete the config entry in configuration.
1 Like
My bad, I must have missed the instructions completely, sorry for that. Works like a charm again
1 Like
Good to hear!
@eavanvalkenburg I’ve just updated to the new version of your SIA plugin and it works really great! I’ve got a question though, how do I customize the new alarm component? When I press any of the buttons I get the following error pop up:
Failed to call service alarm_control_panel/alarm_arm_away. unsupported operand type(s) for &: 'NoneType' and 'int'
Before the update I had manually created an alarm control and then used simple automations such as:
automation:
- alias: "Alarm: Arm away"
trigger:
- platform: event
event_type: call_service
event_data:
domain: alarm_control_panel
service: alarm_arm_away
action:
- service: mqtt.publish
data_template:
topic: ajax/alarm
payload: arm
It still works with the new one, but the error pops up every time you press the button(s).
Is the solution to not use the included alarm component and create a custom one where I keep the state in sync manually?
Hi all,
with this Alarm and this integration, is it possible to armed/disarmed the alarm with Home assistant ?