With OS Malevich 2.9 update, temporary deactivation of devices without removing them from the system has become available. Deactivation may be necessary if the device is incorrectly installed or configured, loses connection with hub, or is defective.
To deactivate a device, go to its settings (Ajax app → Devices tab → select the device you need → Settings → Temporary Deactivation).
The duress code allows for simulating an alarm shutdown. In this case, you won’t be given away by the Ajax application and sirens installed at the facility, and the security company and other security system users will be warned about the incident.
Alarm special features when entering the duress code:
The security company’s Central Monitoring Station (CMS) will receive a “disarming under duress” alarm event. The response unit responds accordingly after arriving at the facility.
All users of your hub receive notifications of security system disarming, where the disarming icon (torn circle on the user icon) will be red.
If the security system is disarmed using the duress code by mistake, contact the Central Monitoring Station (CMS)
The duress code can be set in the user settings:
Hub → Settings → Users → Your profile settings → User passcode
Select the required group in the Arming/Disarming permission menu.
After this, the keypad will control arming/disarming only for the selected group.
Tamper is a miniature button on the device board. It is released when the lid is opened as well as a result of an attempt to unfasten and/or lift the device from the surface, which initiates an event.
When the tamper is released, the Hub sends push notifications and SMS messages (if this type of notification is enabled) to all users of the security system and also communicates the event to the central monitoring station of the security company.
If the tamper is released, Ajax applications display the Open status in the Lid field of the device menu. In addition, a malfunction badge appears on the device icon.
By default, the hub is set to a hub–detector ping interval of 36 seconds and 30 undeliverable data packets to consider the device lost. With these settings, the hub will detect the loss of the detector in 18 minutes.
To reduce this time, go to the hub settings in the Jeweller section and change the settings. The minimum time for detecting loss of connection with the device is 36 seconds (3 polls of 12 seconds each).
The time before raising the alarm by the communication loss between hub and device is calculated with the following formula:
Note that with the minimum ping interval, short-term interference can lead to loss of connection with the device. Therefore, set the minimum values only if it is critically important to promptly inform about events in the system.
The loop (zone) number is required to add a guarded facility to the CMS along with descriptions of all devices connected to the hub.
The loop (zone) number is available in the settings after activating the group mode in the Ajax application:
Having selected a group, you will see a list of its devices. Each device has a Device No. (or DeviceIndex in Ajax PRO Desktop) that corresponds to the loop (zone) number. A number is assigned when a device is attached to the Hub. The first added device has the first loop (zone) number.
After a device or a detector is removed, its number will be assigned to the next added device. However, the numbering of other devices will not change.
In the Ajax app, select the«Devices» tab . Information about the firmware version and device ID is located at the very bottom of the tab with the device parameters.
Go to the Device tab, select the device you want to check.
How Ajax keypads differ
How battery charge is displayed in Ajax apps
How to temporarily deactivate a device without removing it from the system
How long Ajax devices operate on batteries, and what affects this