AJAX Security System Integration that works!

First stable version + UI is ready.

It’s works like original app, with correct malfunctions and arm errors processing.

It uses modified Jeedom Ajax Plugin as proxy to original AJAX API.

I use official Ajax API documentation (it’s open to public) and skip all jeedom ajax plugin processing. It’s only limited to Ajax API.

There is readme in repo how to install and configure my integration.

The integration was build with HA UI in mind, so some sensors optimized to use in UI as easy as possible.

4 Likes

Hey Oleksiy ! Thanks for your work, maybe you can join forces with this project : Custom Component: Ajax Systems

it doesnt require Jeedom

1 Like

Super project… I have a problem to connect HA with Jeedom with your integration: I receive the error “[%key:common::config_flow::error::cannot_connect%]”

Jeedom it’s installed in a doker in a Raspberry PI5 and HA Core OS in other PI5. Jeedom and HA it’s accessible from the outside.

link does not work, I cannot find it in other topics…

it changed :slight_smile: GitHub - foXaCe/ajax-security-hass: Home Assistant integration for Ajax Security Systems

1 Like

Hi Oleksiy,

Do you still maintain this integration?

I have just setup Jeedom and purchased the plugin. I get all the ajax devices in Jeedom and can arm and disarm. But I do not get updates on states unless I synchronize.

Hi @gonzague

Your integration require an Enterprise API which is not “normal” for average AJAX users to acquire. Correct me if I’m wrong?

@TheStigh I recently released this: GitHub - bvis/aegis-hass: Aegis — Unofficial Home Assistant integration for Ajax Security Systems and co-branded apps · GitHub
It does not need any enterprise API, just your user credentials to work, you could try it and tell me if it is fine for you

4 Likes

Hey @basi

Thanx, I’ll have a look! I did also make my own integration :slight_smile: but through JeeDom.

@basi I tested your integration and the only part I could not get working was the video streams.
I saw you mentioned it in the road map, do you have an ETA on this?

But thanks so much, great integration. This is by far the easiest version without the hassle of having an API key.

1 Like

Fantastic!
Finally I am able to use Ajax components for automations. :folded_hands:

1 Like

Hi @armandvuyk — thanks for testing it and for the kind words.

Video streaming is the one capability I genuinely can't build on my own: I don't own any of the video-capable Ajax hardware (MotionCam with video, Video Doorbell, the NVR line), and
unlike the sensor/alarm side — which I can reason about from the protocol — video needs to be developed and verified against a real device end to end. There's no way for me to do that
blind, so the honest answer on an ETA is: it only happens if someone who has the hardware is willing to work through it with me. The rest of the integration got where it is precisely
because users with specific devices helped pin things down, so this is very much how the project moves forward.

If you're up for that, the best first step is to open a GitHub issue so we can track it properly and start from real data:

:backhand_index_pointing_right: Sign in to GitHub · GitHub

To get us off the ground, please include:

  1. Exact device model — the precise name as it appears in the Ajax app (e.g. MotionCam, MotionCam Outdoor, Video Doorbell, MotionCam (PhOD)), and whether it's Jeweller or Fibra.
  2. Versions — your Home Assistant version and the Aegis for Ajax version you tested.
  3. A diagnostics download — Settings → Devices & Services → Aegis for Ajax → ⋮ (three dots) → Download diagnostics, and attach the JSON to the issue. It's already scrubbed of secrets,
    and it tells me exactly how your video device is exposed to the integration.
  4. DEBUG logs while you reproduce it. Add this to configuration.yaml, restart HA:

logger:
default: warning
logs:
custom_components.aegis_ajax: debug

  1. Then, with logging on, open the camera's live view in the official Ajax mobile app once, and separately try the camera entity in Home Assistant. Note the approximate timestamps of
    each, then grab the log (Settings → System → Logs → download) and attach it.

That first capture lets me see what your hub actually exposes for the video device and whether the integration is already receiving anything usable. I can't promise where it lands —
video is a bigger lift than the sensor work — but with a real device and someone willing to iterate, it goes from "impossible for me" to "let's find out." Really appreciate the offer to
help.

— basi