Language:

Partner Portal

Ajax Response

Ajax Response

App for incident handling by rapid response units

FAQ

How to enable critical alerts in Ajax app on Android?

Critical alerts allow receiving alarms even if your smartphone is in Do Not Disturb or Silent modes.

To enable critical alerts:

  1. Open Ajax app.

  2. Tap on а Menu-M menu.

  3. Go to App settings Settings-M.

  4. Tap on System settings.

  5. Enable Critical alerts. To do that:

    • Tap on the Critical alerts toggle.

    • Tap on the To phone settings.

    • Enable Show notifications option.

    • Return back to Ajax app.

  6. Select the Critical alerts volume level. The volume slider allows you to test the sound’s volume. At the lowest volume setting, the smartphone notifies you with a vibration signal only.

Can I connect an Ajax system to monitoring software without a hub

Yes, you can connect an Ajax system to the monitoring software without an Ajax hub. The functionality is available in the following Ajax apps versions:

  • Ajax Security System v3.25 and later;

  • Ajax Desktop v5.25 and later;

  • Ajax PRO: Tool for Engineers v2.25 and later;

  • Ajax PRO Desktop v5.25 and later.

If your app version is earlier, you need an Ajax hub to connect a system to the monitoring software.

Other features do not depend on the adding of a hub to the space, including the Control and Rooms tabs and quick access to automation devices.

How to enable sending events to the CMS with a malfunction code instead of an alarm when the system integrity check is active in PRO Desktop

To enable sending events to the CMS with a malfunction code instead of an alarm when the system integrity check is active:

  1. Open the PRO Desktop app.

  2. Go to the Objects module.

  3. Select the required object.

  4. Go to the hub’s settings by clicking on the gear icon Settings-M.

  5. Select Monitoring Station.

  6. Enable the option Arm with malfunctions without alarm.

ajax sending malfunction code pro desktop

When the option is enabled, arming with malfunction provokes sending events to the CMS with a malfunction code (E380) instead of an alarm (E130).