[APP][Pro] Ajax Security System - Make Ajax alarms part of your smart home

it hasn’t happened again since then

Good morning, Since the latest experimental update, the app has been constantly triggering intrusion alarms whenever a door sensor opens—even when the alarm system is not armed. Could this please be fixed? It’s driving us crazy! :sweat_smile:

Should be fixed with v1.0719. Currently busy converting stuff so memory usage will be a lot less. Might take a few days with bugs here and there, thanks for trying the test version

Latest test version might work : https://homey.app/nl-nl/app/com.ajax.security/Ajax-Beveiligingssysteem/test/

Hello Mike,

Since the latest update to version 1.0.723, the app crashes immediately every time.

4bf8a509-846a-4478-b881-5aad912d64e5

I’m currently in a training course (for my main job) so I might not be able to respond for a few hours but I’ve uploaded a new version that’ll hopefully will resolve al these issues: https://homey.app/nl-nl/app/com.ajax.security/Ajax-Beveiligingssysteem/test/

I’m using the latest experimental version on my Homey Pro (2023). I’m trying to use my Keypad Outdoor Jeweller, to start a trigger. For this I’m using: "This keypad or this remote switched ‘disarmed’ "

Although the alarm was disarmed, the flow was not triggered. When I use another card from the hub instead of the keypad, it works perfectly fine. Any idea what I’m doing wrong here?

Hi JSR1, unfortunately Ajax does this a certain way that theres not much that can be done about that. What you could do/try ; use the hub card “The system was disarmed” and fill in the user name field with the name Ajax shows for that code or user. The card’s source_name / source_type tokens tell you who disarmed it.

If you disarm with the keypad’s general code (not a personal one) and the card still doesn’t fire, please send a diagnostics report right after a disarm so I can see what Ajax sent.

Hi @MikeTango,

I am experiencing an issue similar to the one reported by @AlbyG in post #185, concerning a DoorProtect with an external magnetic contact on a garage door. This was reported as fixed in post #191, but I am seeing the following behaviour with app version 1.0.730.

Environment

  • Homey model: Homey Pro 2026

  • Homey firmware version: 13.5.3

  • Ajax Security System app version: 1.0.730

Device and configuration
My garage door is monitored by a wired floor-mounted magnetic contact connected to the external input of an Ajax DoorProtect.

In the Ajax app:

  • Built-in opening sensor: disabled.

  • External contact: enabled.

Steps to reproduce
With the alarm disarmed:

  1. Close the garage door:

    • Ajax displays “External contact: Closed”.

    • Homey displays “Contact alarm: No”.

  2. Open the garage door:

    • Ajax correctly changes to “External contact: Open”.

    • Homey still displays “Contact alarm: No”.

The Homey Flow condition “The contact alarm is on” therefore always returns false in these tests. I have not tested the behaviour while the alarm is armed.

Expected behaviour
Homey should reflect the external contact’s open/closed state, including while the alarm is disarmed.

Use case
I want to create a Homey Flow that checks whether the garage door is open, sends a pulse to the garage relay if necessary, waits for confirmation that the door is closed, and then arms the alarm.

Could you check whether this is related to the external contact issue reported previously, or whether a different setting or Flow card is required?

I previously submitted a diagnostic report, but I no longer have its code. I can generate a new report or provide the extended diagnostics from the app settings if needed.

Thank you for your help!

Hi @Arnaud_Villat ! Mine is working fine: have you enabled in the Homey App, in the advanced settings of the sensor, the external contact? I had to do this after the update.

@MikeTango

I have this problem now

Make sure to (auto) update, that should be fixed with the latest version

Hi Miketango,

The flow triggered by pressing the doorbell stopped working about a week ago. Has anything changed in an update that could have caused this?

nice regards

Thanks for letting me know. About a week ago the app moved to a new engine, and the doorbell detection was rebuilt as part of that, so this is very likely related.

I haven’t heard others with the same issue, so could you:

  1. Update to the latest version (1.0.740) if you haven’t already.
  2. Press the doorbell once.
  3. Within a few minutes, open the app’s settings in Homey and send me a diagnostics report (the “extended diagnostics” export), and tell me roughly what time you pressed it.

Please also check in the Ajax app that the account Homey uses is an administrator of the space, and that doorbell notifications are switched on for it.

With that report I can see whether the press reaches Homey and where it gets lost.

Hi @AlbyG and @MikeTango,

Thank you for your help!

I don’t see an external contact option in the sensor’s advanced settings in Homey, but I can now see the detector’s state correctly.

I suspect I accidentally selected the garage relay instead of the DoorProtect when creating my Flow, so this may have been a mistake on my side rather than an app issue.

I’ll test opening and closing the garage door this evening to confirm that both the state and the Flow condition update correctly, and report back here.

Thanks again!

No problem, hopefully it’s resolved else I’ll see what can be done