---
title: "Ajax alarm in TapHome: arm and disarm, and use Ajax detectors in smart rules"
description: "Arm and disarm Ajax from TapHome and use Ajax door, leak, fire and motion detectors in smart rules. See what is coming and tell us what you need."
url: "https://taphome.com/en/ideas/ajax-alarm/"
language: en
lastmod: 2026-11-19
generator: hugo
---

# Ajax alarm in TapHome: arm and disarm, and use Ajax detectors in smart rules

Link your Ajax account to TapHome to arm, disarm and switch night mode from the TapHome app and smart rules, and use Ajax door, leak, fire and motion detectors as TapHome devices, with alarm and arming events within seconds and a local SIA DC-09 backup.

- Status: In development — We are working on it now.
- Type: Integration
- 14 interested
- Topics: [Integrations and protocols](https://taphome.com/en/ideas/topics/integrations-protocols/), [Security and alarms](https://taphome.com/en/ideas/topics/security-alarms/)
- Last updated: 2026-11-19


## Why and how you would use it

Many homes with TapHome also have an Ajax alarm, and the two systems do not talk to each other. Installers want the obvious links: close the blinds and lower the heating when the house is armed, turn on the lights on a leak or fire alarm, and arm Ajax from the TapHome app.

For example, the family leaves and arms Ajax on the keypad. TapHome should switch to away mode, but today that takes extra wiring, or it does not happen at all.

| | Today | With this idea |
|---|---|---|
| Alarm state in TapHome | Extra wiring | Built in |
| Arm from TapHome | Not possible | App and smart rules |
| Ajax detectors | Separate | TapHome devices |

## What will be possible

We are evaluating this integration. Nothing below is scheduled yet, and the details may still change.

- **Link your Ajax account in the TapHome app.** A setup wizard would link the Ajax user account, including the code when Ajax asks for one, and pick the Ajax spaces (homes) the Core serves. The Core would not store the Ajax password.
- **Arm, disarm and night mode.** The security state of the hub would be a TapHome device: you could see it and change it from the TapHome app and from smart rules. With Ajax groups, each group would be a device of its own. One Core could serve several hubs.
- **Ajax detectors as TapHome devices.** Door contacts (DoorProtect), leak detectors (LeaksProtect), fire detectors (FireProtect) and motion detectors (MotionProtect, MotionCam, CombiProtect) would appear in TapHome and could be used in smart rules and notifications.
- **Device health.** Low battery, tamper, malfunction and a detector the hub can no longer hear would show as device warnings in TapHome.
- **Instant events.** Arming, disarming, alarms and device faults would reach TapHome within seconds: the Ajax cloud would pass them to the TapHome cloud, which would hand them straight to the Core. As a backup when the internet is down, the Ajax hub could also report its events directly to the Core on the local network over SIA DC-09, the same protocol Ajax uses for monitoring stations, with optional encryption.

## What will not be possible

- **Motion while the alarm is disarmed.** Ajax motion detectors report motion only when the system is armed. In the disarmed state they save battery and send nothing, so they cannot replace TapHome presence sensors for lighting. The "Always active" setting in the Ajax app is not a way around it: it makes the detector raise a real alarm also when the house is disarmed.
- **Instant door events while disarmed.** The open or closed state of a door contact would be read from the Ajax cloud also when the alarm is disarmed, but with a delay of up to about a minute. Ajax sends instant door events to other systems only when the house is armed.
- **A local backup on a hub that already reports elsewhere.** The local SIA DC-09 connection uses the hub's monitoring station setting. A hub that already reports to a security company over SIA DC-09 may not have it free. Events from the Ajax cloud would still arrive, only without the local backup when the internet is down.
- **A monitoring station.** TapHome would not replace a certified alarm receiving centre. The alarm itself keeps working in Ajax, also when TapHome or the internet is down.
- **Everything else from Ajax in a first version.** Keypads, sirens, camera images and Ajax relays, sockets and wall switches are not part of the first version.

## How to solve it today

- **Ajax state to TapHome over a contact.** An Ajax relay can follow the security mode with an Ajax scenario. Wire its contact to an input of the [Core](https://hardware.taphome.com/en/core/) or a TapHome module and use it in smart rules.
- **The TapHome alarm.** For a new installation, TapHome has its own alarm with zones, arming from the app and push notifications, see [Alarm](https://taphome.com/en/docs/functional-areas/alarm/).

## Learn more

- [Alarm](https://taphome.com/en/docs/functional-areas/alarm/) documentation.

Do you install Ajax together with TapHome? Tell us which Ajax devices you would like to see in TapHome: vote for this idea, follow it for updates and answer the poll below.

**Vote · Follow:** Anyone can vote. Sign in with your TapHome account to follow ideas, answer polls, comment and suggest your own.

- [Ajax alarm in TapHome: arm and disarm, and use Ajax detectors in smart rules](https://taphome.com/en/ideas/ajax-alarm/)
- [Suggest an idea](https://taphome.com/en/ideas/#suggest)

