How to temporarily deactivate a device without removing it from the system

Updated

Deactivating the device may be necessary if the device is incorrectly installed or configured, loses connection with the hub, or is defective. In this case, the CMS engineer or the system user temporarily deactivate the device until the cause of the malfunction is eliminated.

Deactivated device does not execute system commands, does not participate in automation scenarios, and does not send notifications of alarms, malfunctions, and other events to the CMS and to users of the security system (push notifications, SMS, calls). At the same time, the current states of the device (connection status with the hub, battery charge level, etc.) is displayed on the status screen in the Ajax app (Devices — select the desired device in the list and click it).

The ability to deactivate devices is supported by hubs with OS Malevich 2.9 and higher, as well as Ajax apps starting with versions:

  1. Ajax for iOS 2.15
  2. Ajax for Android 2.18
  3. Ajax PRO for iOS 1.8
  4. Ajax PRO for Android 1.8
  5. Ajax PRO Desktop 2.6

Only a user with administrator rights can temporarily deactivate the device.

To disable/enable the device:

  1. Open the Ajax app and go to the Devices tab .
  2. Select the desired device and go to its settings by pressing .
  3. Go to the menu item Temporary deactivation .

The function is available for all Ajax devices without type restrictions, as well as for third-party wired devices connected to the security system via Transmitter and MultiTransmitter.

Please note that it is impossible to exclude Ajax central panels (Hub, Hub Plus, Hub 2, Hub 2 Plus) from the system.

Two options are available in the app:

  • Deactivate entirely. The device will not execute system commands or run automation scenarios. The system will ignore device alarms, notifications of low battery charge, body opening, loss/restoration of communication with the hub, etc.
  • Deactivate notifications about the lid state — messages about triggering the tamper button of the device are ignored. At the same time, the security system will record other device events (alarms, malfunctions), and transmit them to Ajax apps and to the Central Monitoring Station of a security company.

At the moment when the device is enabled/disabled, the corresponding notification arrives at the CMS and the system user in the Ajax app.

Depending on the selected mode, the deactivated device is marked with an icon in the list of hub devices:

  1. — the device is completely deactivated
  2. — the system ignores triggering notifications on the device body

When the System Integrity Check is enabled in the hub settings, the deactivated device is not taken into account when arming.

If the “Alert with a siren if the hub or detector body is open” option is enabled in the hub settings, the siren will not react to tamper triggering of the deactivated device.

Performance features of some Ajax devices after deactivation:

  1. When you deactivate the ReX range extender, the system ignores only its events. ReX-connected detectors operate in normal mode.
  2. StreetSiren with a version older than 3.70.10 cannot be deactivated.
  3. Temporarily deactivated automation devices do not participate in scenario execution. When deactivated, the device saves the current state (active or inactive), but it is impossible to change the state of the deactivated automation device through the app.
  4. A temporarily deactivated FireProtect/FireProtect Plus fire detector does not trigger the interconnected fire alarm. But smoke detection triggers the siren built into the device.
  5. The deactivated KeyPad displays the security system status (armed, disarmed) with indication, but does not execute commands.
  6. The deactivated SpaceControl key fob does not send arming/disarming commands, the panic button is inactive.
  7. The deactivated Button in the panic button mode does not send alarms to the hub, and in the control mode, it does not start automation scenarios.