purchased the Ajax alarm system myself and am therefore the end user of the system.
Unfortunately, the webshop/supplier where I bought the system is unable to provide an Ajax Enterprise API key. I understand that this key is required in order to integrate the system with external platforms.
I would like to connect and integrate my Ajax alarm system with a third-party solution, but not via SIA. My intention is to use the Ajax Enterprise API for this integration.
Could you please advise who can assist me in obtaining the correct API access or guide me on the proper procedure to enable this integration as an end user?
The KNX integration uses SIA similarly to this integration at the current point. The only change is that for the KNX integration you also can replace your existing security company with Elausys instead, in order to arm/disarm your system.
What we are working on here, is full Enterprise API control with serverside events for instant alarms as well as polling of each individual device so you can use for example door sensors for automations, enable relays and more in everyday flows. This is as far as I know only attempted by this Homey integration and the Home Assistant integration that I am currently in talks with, and can only be done due to the work of someone at Ajax France that developed a proxy that will enable caching and restrictions on polling while also using Enterprise API keys not exposed to endusers. This is however quite challenging due to Ajax´es very restrictive API polling requirements.
I am trying to get a connection, with a local SIA connection. I can add the AJAX hub in Homey, so I assume some message is received by Homey?
But after this, no status updates are given. Did anyone else have succes with a local SIA connection or does this not yet function and shoud I use the enterprise api or proxy? This is still unclear for me
Added a few hours later: seems like I found what the problem was. In Ajax for the Security Company (meldkamer) you need to add the Ajax user ID in the field Object ID. The Ajax user ID is the one you’ve entered during the create device in Homey. The “night mode” is now received by Homey when set.
Here is a working Ajax Enterprise integration; Ajax Security Enterprise | Homey Don’t forget to fill in all, including Ajax login. Hope this helps some people (whom have an Enterprise key)
This integration already supports the use of Enterprise API key. But the problem is restrictions on the keys, hence why we also had to introduce a proxy.
@Thomas_Thaulow I have the Enterprise API now and can add my hub as a user to Homey through your app. As Pro (Installer) it’ gives an error. How do I add devices and camera’s now because the app says they are not found?
yes, I know… also this ‘proxy’ setup does not sound like the most ‘elegant’ solution next to the time it takes to get there… but I’m not technical enough
The proxy both lets users make use of an Enterprise API key without knowing the key itself, and it also enables us to restrict or cache data to limit how often users poll from it, due to Ajax´s polling restrictions. So quite frankly there is no other way, if you are not given your own Enterprise API key. This is a limitation on how Ajax has built their products, and is a problem for anyone who wants to integrate with them, not only Homey users.
Hi! I got almost everything flawless working with the Enterprise API. Thanks for this. A few questions:
Homey can not recieve the nightmode status correctly. I made a flow ‘when nightmode is not enabled, enable night mode’. It works. But when i do the opposite, ‘when nightmode is enabled, disable night mode’ it shows me that its not enabled yet.. so it won’t disable the nightmode then.
I add almost every device in my home except a few PIR sensors. Strange, because i have ± 10 PIR’s with only motion and glassbreak, (some where found and added, and some are not found) and ± 5 with also the PHOD photo option (also some where found, some not). I did buy the devices in the same order, looks like the same products for me. Signal strengt is all the same.. what could be wrong?
I don’t know what can be the issue for you, but what I do know is that both arming and disarming work well for me. For “night mode” (deelinschakeling) and "fully armed” (without deelinschakeling)
This logs shows it works on my side. I left out the time-stamps, which are not relevant here.
Note that I am not using the API. I am using the option to send updates to an external alarm central.
