I believe the integration with Ajax will never happen.
For years now, we’ve been hearing the same things about developers working on it, but nothing ever comes of it.
It would definitely be great to have such integrations, but I don’t think it will happen.
The only way forward is if Ajax opens up their API—if they don’t, no one will ever be able to build it.
Is there a standard api and an enterprise api?
Is it possible to use a pro account with the api? (as I can only see access via a user account).
Hello,
I just did Ajax HA Integration that works like bridge between Jeedom and HA.
Everything from Jeedom works in HA.
It’s very early version. Let’s test it together.
I do not have physical access to my Ajax hub and do not have root rights, so some things are unclear for me.
I do not add [email protected] user to my hub, so some of events may not work for me.
In my configuration I have one Hub and 4 Arming groups.
What is works:
- Arm/Disarm state updates
- Open/Closed state updates
- ExternalPower, Voltage, Temperature sensors
- Jeedom Ajax action buttons (ARM, DISARM, ON, OFF, etc)
What I do not known:
- How Alarm comes in MQTT messages.
- What event codes mean (hub.eventCode). I have something like M22_2A, M22_29, M22_2D.
What is not work in Jeedom:
- Relay stay not updated in Jeedom.
- Voltage point error: 119.000 volts insted of 11.90
- Night Mode button do not work on groups
- Night Mode button on Hub can only enable Night Mode. Currently I do not know how to disable Night Mode and leave some groups ARMED
There two main problems:
-
Jeedom Ajax plugin complety ignores malfunctions while arming. If garage door is opened - garage will be armed and signal to police will be sent. Currently I don’t know now, how to check for malfunctions before or after ARMING.
-
Sometimes it do not update state after arming/disarming. In theory I can force update with manual full refresh, not waiting for MQTT Event.
UPDATE: Jeedom Ajax Plugin is easy to patch to unlock more features. Hope next release will be fully functional ![]()
Hi. I’d like to publish (and use) my integration, but at the moment I’m quite stuck on the legal side; similar software, even if not based on reverse engineering, would break Ajax ToS, and would lead to a ban (quite an annoying thing, as I wouldn’t be able to use my home alarm system) and to the deletion all the work I’ve done.
Let me know if you have any advice.
Jeedom Ajax plugin uses jeedom market login and password to access ajax API via cloud.jeedom.com. The plugin looks very simple, so the best way is to buy license for 8 EUR, rewrite plugin in python and use cloud.jeedom.com without jeedom ![]()
Did you known what hub event codes mean?
M_22_02 looks like NIGHT_MODE_ON
M_22_28 looks like NIGHT_MODE_OFF
it’s the same for all users or hub/config specific?
Jeedom Ajax API can do a lot more, than Jeedom Ajax plugin. I already test two hacks:
- Redirect all RAW events from Jeedom API to HA integration, because jeedom plugin ignores some critical information (in my case is malfunctions when arming)
- Call API with more options (ARM and check for problems, NIGHT_MODE_OFF), that plugin do not provide

Jeedom plugin provide NIGHT_MODE action for Groups. Does latest HUBs support NIGHT_MODE per group? For me it’s always server error and original app do not provide this function.
Hi, this is the worst solution i have ever heard. Install a buggy soft and pay 8$ to have a plugin !!!
From what I see and already test: It’s possible to make good and usable AJAX integration. Jeedom Ajax API can provide all features that I known.
I need to convert 40 lines of code, to be able make direct API calls on ARM/DISARM
Jeedom API make POST request to http://myserver/plugins/ajaxSystem/core/php/jeeAjaxSystem.php on each update or event. So simple mod_rewrite can redirect all traffic to my script and then to integration.
Looks realistic to use jeedom just once, to receive API tokens, or maybe initial setup ![]()
It’s released and works much better than I expected. For me it’s better than original APP!
There is UI and Integration.
I started new topic
I found AJAX API description in public access. Looks like Jeedom cloud works like proxy, everything from Ajax API works in Jeedom cloud, every event like in documentation. I think you code can work with Jeedom Cloud with minimum modifications like changing urls and adding jeedom market login.
Or maybe you can add something to my code. Now it 100% based on Ajax API.
I’ve been running jeedom ajax plugin with mqtt linked to HA for more than a year. my experience shows that jeedom plugin is not very reliable I’m very keen to test your integration. I’ll keep the community posted on my findings. Thank you very much for your effort
let’s hope that jeedom will not block proxy traffic
I call API once, at integration reloading (HA restart) and when sending ARM/DISARM commands. All other time integration listening for events from API. So there is almost zero traffic.
Good to know. I’m asked for Ajax API token. Where do I find it?
Documentation is here
Well I found the APÏ key in plugin logs. So far I can’t connect despite the fact that jeedom instance can be accessed from outside (just checked again). In URL I put https://myurl:port, in API token what I found in ajax plugin logs and the following message is returned
[%key:common::config_flow::error::cannot_connect%]
Thanks! I overlooked the fact that ajax plugin code needs to be hacked. All entity_id’s created. Let’s go forward with some testing from now on
Can I change entity_id’s once they have been created without affecting integration functionning?
Yes, I rename my without problems
I do not know how to do this. Some old versions of HA ask me to rename all sensors with device rename. I can change it, if someone point me how to do it.

