Hub is a central device of the Ajax security system, coordinating the connected devices, and interacting with the user and security company. Hub is developed only for indoor use.
Hub requires Internet access to communicate with the cloud server Ajax Cloud—for configuring and controlling from any point of the world, transferring event notifications, and updating the software. The personal data and system operation logs are stored under multilevel protection, and information exchange with Hub is carried out via an encrypted channel on a 24-hour basis.
Communicating with Ajax Cloud, the system can use the Ethernet connection and GSM network.
Please use both communication channels to ensure more reliable communication between the hub and Ajax Cloud.
Hub can be controlled via the app for iOS, Android, macOS, or Windows. The app allows responding promptly to any notifications of the security system.
Follow the link to download the app for your OS:
The user can customize notifications in the hub settings. Choose what is more convenient for you: push notifications, SMS, or calls. If the Ajax system is connected to the central monitoring station, the alarm signal will be sent directly to it, bypassing Ajax Cloud.
Up to 100 Ajax devices can be connected to the hub. The protected Jeweller radio protocol ensures reliable communication between the devices at a distance of up to 2 km in the line of sight.
Use scenarios to automate the security system and decrease the number of routine actions. Adjust the security schedule, program actions of automation devices (Relay, WallSwitch or Socket) in response to an alarm, Button press or by schedule. A scenario can be created remotely in the Ajax app.
Sockets and Indication
- LED logo indicating the hub status
- SmartBracket attachment panel. Perforated part is required for actuating the tamper in case of any attempt to dismantle the hub
- Socket for the power supply cable
- Socket for the Ethernet cable
- Slot for the micro SIM
- QR code
- Tamper button
- On/Off button
- Сable retainer clamp
The LED logo can light up red, white or green depending on the status of the device.
|Ethernet and at least one SIM card are connected||Lights up white|
|Only one communication channel is connected||Lights up green|
|The hub is not connected to the internet or there is no connection with the Ajax Cloud service||Lights up red|
|No power||Lights up for 3 minutes, then blinks every 10 seconds. The color of the indicator depends on the number of the connected communication channels.|
Connecting to the Network
- Open the hub lid by shifting it down with force.
Be careful and do not damage the tamper protecting the hub from dismantling.
- Connect the power supply and Ethernet cables to the sockets.
1 — Power Socket
2 — Ethernet socket
3 — SIM-card slot
4 — Сable retainer clamp
- Press and hold the power button for 2 seconds until the logo lights up. The hub needs approximately 2 minutes to identify the available communication channels.
The bright green or white logo color indicates that the hub is connected to Ajax Cloud.
If the Ethernet connection does not occur automatically, disable proxy, filtration by MAC addresses and activate the DHCP in the router settings: the hub will receive an IP address. During the next setup in the mobile app, you will be able to set a static IP address.
To connect the hub to the GSM network, you need a micro-SIM card with a disabled PIN code request (you can disable it using the mobile phone) and a sufficient amount on the account to pay for the GPRS, SMS services and calls.
In some regions, Hub is sold with a SIM card along
If the hub does not connect to Ajax Cloud via GSM, use Ethernet to set up the network parameters in the app. For the proper setting of the access point, username, and password, please contact the support service of the operator.
The user with administrator rights can configure the Ajax security system via the app. The administrator account with the information about the added hubs is encrypted and placed on Ajax Cloud.
All the parameters of the Ajax security system and connected devices set by the user are stored locally on the hub. These parameters are inextricably linked with the hub: changing the hub administrator does not affect the settings of the connected devices.
One phone number may be used to create only one Ajax account.
Create the Ajax account in the app following the step-by-step guide. As part of the process, you need to confirm your email and phone number.
Ajax account allows to combine the roles: you can be the administrator of one hub, as well as the user of another hub.
Adding the hub to the Ajax app
Granting access to all system functions (to display notifications in particular) is a mandatory condition for controlling the Ajax security system via the smartphone.
- Login into your account.
- Open the Add Hub menu and select the way of registering: manually or step-by-step guidance.
- At the registration stage, type the name of the hub and scan the QR code located under the lid (or enter a registration key manually).
- Wait until the hub is registered.
If there are already users on the hub, the hub administrator, PRO with full rights or the installation company of the selected hub can add your account to it. You will receive a notification that the hub is already added to another account.
Get in touch with our support to determine who has admin rights on the hub.
Prior to installing the hub, make sure that you have selected the optimal location: the SIM card demonstrates consistent reception, all the devices have been tested for radio communication, and the hub is hidden from direct view.
The device developed only for indoor use.
The hub should be reliably attached to the surface (vertical or horizontal). We do not recommend using double-sided adhesive tape: it cannot guarantee secure attachment and simplifies the removal of the device.
Do not place the hub:
- outside the premises (outdoors);
- nearby or inside any metal objects that cause attenuation and shielding of the radio signal;
- in places with a weak GSM signal;
- close to radio interference sources: less than 1 meter from the router and power cables;
- in premises with temperature and humidity over the permissible limits.
- Fix the hub lid on the surface using bundled screws. When using any other fixing accessories, make sure that they do not damage or deform the hub lid.
- Fix the power and Ethernet cables with the supplied cable retainer clamp and screws. Use cables with a diameter no larger than the supplied ones. The cable retainer clamp must fit tightly to the cables so that the hub lid closes easily.
The cable retainer clamp helps to prevent sabotage — the power and Ethernet cables will not be pulled out on purpose.
- Put the hub on the lid and fix it with bundled screws.
Do not flip the hub when attaching vertically (for instance, on a wall). When properly fixed, the Ajax logo can be read horizontally.
Fixing the hub on lid with screws prevents any accidental shifting of the hub and minimizes the risk of device theft.
If the hub is firmly fixed, the attempt to tear it off triggers the tamper, and the system sends a notification.
Rooms in the Ajax app
The virtual rooms are used to group the connected devices. The user can create up to 50 rooms, with each device located only in one room.
Without creating the room, you are not able to add devices in the Ajax app.
Creating and Setting Up a Room
The room is created in the app using the Add Room menu.
Please assign a name for the room, and optionally, attach (or make) a photo: it helps to find the needed room in the list quickly.
By pressing on the gear button go to the room settings menu.
To delete the room, move all the devices to other rooms using the device setup menu. Deleting the room erases all its settings.
The hub doesn’t support uartBridge and ocBridge Plus integration modules.
During the first hub registration in the app, you will be prompted to add devices to guard the room. However, you can refuse and return to this step later.
The user can add the device only when the security system is disarmed.
- Open the room in the app and select the Add Device option.
- Name the device, scan the QR code (or insert the ID manually), select the room and go to the next step.
- When the app starts searching and launches countdown, switch on the device: its LED will blink once. For detection and pairing to occur, the device should be located within the coverage area of the wireless network of the hub (at a single protected object).
Сonnection request is transmitted for a short time when switching on the device.
If the connection fails on the first try, switch off the device for 5 seconds and retry.
Up to 10 cameras or DVRs that support RTSP protocol can be connected to Hub.
Icons display some of Hub statuses. You can see them in the Ajax app, in the Devices menu .
|SIM card is not installed|
|The SIM-card is defective or has a PIN-code on it|
|Hub battery charge level. Displayed in 5% increments|
|Hub malfunction is detected. The list is available in hub states list|
|The hub is directly connected to the central monitoring station of the security organization|
|The hub have lost connection with the central monitoring station of the security organization via direct connection|
States can be found in the Ajax app:
- Go to the Devices tab .
- Select Hub from the list.
Click to open the list of Hub malfunctions.
The field appears only if a malfunction is detected
|Cellular signal strength||Shows the signal strength of the mobile network for the active SIM card. We recommend installing the hub in places with the signal strength of 2-3 bars. If the signal strength is weak, the hub will not be able to dial-up or send an SMS about an event or alarm|
Battery level of the device. Displayed as a percentage
|Lid||Status of the tamper that responds to hub dismantling:
|External power||External power supply connection status:
|Connection||Connection status between the hub and Ajax Cloud:
|Cellular data||The hub connection status to the mobile Internet:
If the hub has enough funds on the account or has bonus SMS/calls, it will be able to make calls and send SMS messages even if the Not connected status is displayed in this field
|Ethernet||Internet connection status of the hub via Ethernet:
|Average Noise (dBm)||
Noise power level at Jeweller frequencies at the hub installation site.
The acceptable value is –80 dBm or lower
|Monitoring Station||The status of direct connection of the hub to the central monitoring station of the security organization:
If this field is displayed, the security company uses a direct connection to receive events and security system alarms
|Hub model||Hub model name|
|Hardware version||Hardware version. Unable to update|
|Firmware||Firmware version. Can be updated remotely|
|ID||ID/serial number. Also located on the device box, on the device circuit board, and on the QR code under the SmartBracket panel|
Settings can be changed in the Ajax app:
- Go to the Devices tab .
- Select Hub from the list.
- Go to Settings by clicking on the icon .
Note that after changing the settings, you should click the Back button to save them.
Avatar is a customized title image for Ajax security system. It is displayed in the hub selection menu and helps to identify the required object.
To change or set an avatar, click on the camera icon and set up the desired picture.
Hub name. Is displayed in the SMS and push notification text. The name can contain up to 12 Cyrillic characters or up to 24 Latin characters.
To change it, click on the pencil icon and enter the desired hub name.
In this category of settings, you can invite and delete users, edit their rights, and define how the security system notifies users about events and alarms.
To change the settings for a specific user, click on their username in the list of active users.
User Role — selecting the level of access to the system management and configuring: Admin or User.
Privacy Settings Management — when enabled, the user can control other users’ access to surveillance camerasand DVRs.
Permissions — this setting allows you selectively grant access to manage:
- System security modes.
- Pressing the panic button in the Ajax app.
- Automation devices.
- Chime feature.
The category is available for those users who have the right to manage privacy settings. The settings apply to the surveillance cameras, and DVRs integrated into the system.
Users — setting up access levels to surveillance cameras and DVRs for system users.
Installers — setting up access levels to surveillance cameras and DVRs for professional installers.
Ethernet — settings for wired Internet connection.
- Ethernet — allows you to enable and disable Ethernet on the hub
- DHCP / Static — selection of the type of the hub IP address to receive: dynamic or static
- IP Address — hub IP Address
- Subnet mask — subnet mask in which the hub operates
- Router — gateway used by the hub
- DNS — DNS of the hub
Cellular — enabling/disabling cellular communication, configuring connections, and checking account.
- Cellular Data — disables and enables SIM cards on the hub
- Roaming — if it is activated, the SIM cards installed in the hub can work in roaming
- Ignore network registration error — when this setting is activated, the hub ignores errors when trying to connect via a SIM card. Activate this option if the SIM card cannot connect to the network
- Disable Ping Before Connecting — when this setting is activated, the hub ignores operator communication errors. Activate this option if the SIM card cannot connect to the network
- SIM card 1 — displays the number of the SIM card installed. Click on the field to go to the SIM card settings
SIM card settings
- APN, User name, and Password — settings for connecting to the Internet via a SIM card. To find out the settings of your cellular operator, contact your provider’s support service.
Mobile data usage
- Incoming — the amount of data received by the hub. Displayed in KB or MB.
- Outgoing — the amount of data sent by the hub. Displayed in KB or MB.
Keep in mind that data is counting on the hub and may differ from your operator’s statistics.
Reset statistics — resets statistics on incoming and outgoing traffic.
- USSD code — enter the code that is used to check the balance in this field. For example, *111#. After that, click Check balance to send a request. The result will be displayed under the button.
Geofence — configuring reminders for arming/disarming the security system when crossing a specified area. The user location is determined using the smartphone GPS module.
Groups — group mode configuration. This allows you to:
- Manage the security modes for separate premises or groups of detectors.
For example, the office is armed while the cleaner works in the kitchen.
- Delimit access to control of security modes.
For example, the marketing department employees do not have access to the law office.
Security Schedule — arming/disarming the security system by the schedule.
Detection Zone Test — running the detection zone test for the connected detectors. The test determines the sufficient distance for the detectors to register alarms.
Jeweller — configuring the hub-detector ping interval. The settings determine how frequently the hub communicates with devices and how quickly the loss of connection is detected.
- Detector Ping Interval — the frequency of connected devices polling by the hub is setting in the range of 12 to 300 s (36 s by default)
- Number of undelivered packets to determine connection failure — a counter of undelivered packets (8 packets by default).
The time before raising the alarm by the communication loss between hub and device is calculated with the following formula:
Detector Ping Interval × Number of missed pings to determine connection failure
The shorter ping interval (in seconds) means faster delivery of the events between the hub and the connected devices; however, a short ping interval reduces the battery life. At the same time, alarms are transmitted immediately regardless of the ping interval.
We do not recommend reducing the default settings of the ping period and interval.
Note that the interval limits the maximum number of connected devices:
|12 seconds||39 devices|
|24 seconds||79 devices|
|36 and more seconds||100 devices|
Regardless of settings, the hub supports 10 connected sirens maximum.
Service is a group of hub service settings. These are divided into 2 groups: general settings and advanced settings.
Selecting the time zone in which the hub operates. It is used for scenarios by schedule. Therefore, before creating scenarios, set the correct time zone.
Adjustment of the hub logo LED backlight brightness . Set in the range of 1 to 10. The default value is 10.
Configuring automatic OS Malevich firmware updates.
- If enabled, the firmware is automatically updated when a new version is available, when the system is not armed, and external power is connected.
- If disabled, the system does not update automatically. If a new firmware version is available, the app will offer to update the OS Malevich.
Hub System Logging
Logs are files containing information about system operation. They can help sort out the problem in case of errors or failures.
The setting allows you to select the transmission channel for the hub logs or disable their recording:
- No — logging is disabled
We do not recommend disabling logs as this information may be helpful in the event of errors in the operation of the system.
The list of advanced hub settings depends on the type of application: standard or PRO.
|Ajax Security System||Ajax PRO|
Fire detectors settings
System integrity check
|PD 6662 Setting Wizard
Fire detectors settings
System Integrity Check
Restoration After Alarm
Devices Auto Deactivation
PD 6662 Setting Wizard
Opens a step-by-step guide on how to set up your system to comply with the British security standard PD 6662:2017.
The menu contains settings for communication between the hub and the Ajax Cloud:
- Hub-Server Polling Interval, sec. Frequency of sending pings from the hub to Ajax Cloud server. It is set in the range of 10 to 300 s. The recommended default value is 60 s.
- Delay of Server Connection Failure Alarm, sec. It is a delay to reduce the risk of a false alarm associated with the Ajax Cloud server connection loss. It is activated after 3 unsuccessful hub-server polls. The delay is set in the range of 30 to 600 s. The recommended default value is 300 s.
The time to generate a message regarding the loss of communication between the hub and the Ajax Cloud server is calculated using the following formula:
(Ping interval * 3) + Time filter
With the default settings, Ajax Cloud reports the hub loss in 8 minutes:
(60 s * 3) + 300 s = 8 min
- Receive events of server connection loss without alarm. Ajax apps can notify about the hub-server communication loss in two ways: with a standard push notification signal or with a siren sound (enabled by default). When the option is active, the notification comes with a standard push notification signal.
- Notify of connection loss over channels. Ajax security system can notify both the users and the security company about the loss of connection even via one of the connection channels.
In this menu, you can choose the connection loss of which channels will be reported by the system, as well as the delay for sending such notifications:
- Loss Notification Delay, min — time of the delay before sending the notification about loss of connection via one of the communication channels. Set in the range from 3 to 30 minutes.
The time of sending a notification about the loss of connection via one of the communication channels is calculated with the formula:
(Polling interval * 4) + Time filter + Loss Notification delay
The menu contains two groups of siren settings: siren activation parameters and siren after-alarm indication.
Siren activation parameters
If the hub or detector lid is open. If enabled, the hub activates the connected sirens if the body of the hub, detector, or any other Ajax device is open.
If in-app panic button is pressed. When the function is active, the hub activates the connected sirens if the panic button was pressed in the Ajax app.
You can disable the sirens reaction when pressing the panic button on the SpaceControl key fob in the key fob settings (Devices → SpaceContol → Settings ).
Settings of siren after-alarm indication
The siren can inform about triggering in armed system by means of LED indication. Thanks to this feature, system users and passing security companies patrols can see that the system was triggered.
Fire detectors settings
Settings menu of FireProtect and FireProtect Plus fire detectors. Allows configuring Interconnected Fire Detectors Alarm.
The feature is recommended by European fire standards, which require, in the event of a fire, a warning signal power of at least 85 dB at 3 meters from the sound source. Such sound power wakes up even a soundly sleeping person during a fire. And you can quickly disable triggered fire detectors using the Ajax app, Button, or KeyPad/KeyPad Plus.
System Integrity Check
The System integrity check is a parameter that is responsible for checking the status of all security detectors and devices before arming. Checking is disabled by default.
Alarm confirmation is a special event that the hub sends to the CMS and system users if several certain devices have triggered within a specified period of time. By responding to confirmed alarms only, the security company and the police reduce the number of visits on false alarms.
Restoration After Alarm
The feature does not allow arming the system if an alarm has been registered previously. For arming, the system should be restored by an authorized user or PRO user. The types of alarms that require system restore are defined when configuring the function.
The function eliminates situations when the user arms the system with detectors that generate false alarms.
The menu allows to enable arming in two stages, as well as set Alarm Transmission Delay for security system disarming process.
Devices Auto Deactivation
The Ajax security system can ignore alarms or other events of devices without removing them from the system. Under certain settings, notifications about events of a specific device will not be sent to the CMS and security system users.
There are two types of Devices Auto Deactivation: by the timer and by the number of alarms.
It is also possible to manually disable a specific device. Learn more about deactivating devices manually here.
Monitoring Station — the settings for direct connection to the security company’s central monitoring station. Parameters are set by security company engineers. Keep in mind that events and alarms can be sent to the central monitoring station of the security company even without these settings.
- Protocol — the choice of the protocol used by the hub to send alarms to the central monitoring station of the security company via a direct connection. Available protocols: Ajax Translator (Contact-ID) and SIA.
- Connect on demand. Enable this option if you need to connect to the CMS (Central Monitoring Station) only when transmitting an event. If the option is disabled, the connection is maintained continuously. The option is available only for the SIA protocol.
- Object number — the number of an object in the monitoring station (hub).
Primary IP address
- IP address and Port are settings of the primary IP address and port of the security company server to which events and alarms are sent.
Secondary IP address
- IP address and Port are settings of the secondary IP address and port of the security company server to which events and alarms are sent.
Alarm sending channels
In this menu, channels for sending alarms and events to the central monitoring station of the security company are selected. Hub can send alarms and events to the central monitoring station via Ethernet and EDGE. We recommend that you use all communication channels at once — this will increase the transmission reliability and secure against failures on the telecom operators’ side.
- Ethernet — enables event and alarm transmission via Ethernet.
- GSM — enables event and alarm transmission via the mobile Internet.
- Periodic Test Report — if enabled, the hub sends test reports with a given period to the CMS (Central Monitoring Station) for additional monitoring of object connection.
- Monitoring Station Ping Interval — sets the period for sending test messages: from 1 minute to 24 hours.
Event transmission encryption settings in the SIA protocol. AES 128-bit encryption is used.
- Encryption — if enabled, events and alarms transmitted to the central monitoring station in SIA format are encrypted.
- Encryption key — encryption key of transmitted events and alarms. Must match the value on the Central Monitoring Station.
Panic button coordinates
- Send coordinates — if enabled, the pressing of a panic button in the app sends the coordinates of the device on which the app is installed and panic button is pressed, to the central monitoring station.
Alarm Restore on ARC
The setting allows you to select when the alarm restore event will be sent to the CMS: immediately/upon detector restore (by default) or upon disarming.
Installers — PRO users settings (installers and representatives of security companies) of the security system. Determine who has access to your security system, the rights that are granted to PRO users, and how the security system notifies them about the events.
Security companies — a list of security companies in your area. The region is determined by the GPS data or the regional settings of your smartphone.
User Guide — opens the Hub user guide.
Data Import — a menu for automatical transferring devices and settings from another hub. Keep in mind that you are in the settings of the hub on which you want to import data.
Unpair hub — removes your account from the hub. Regardless of this, all the settings and connected detectors remain saved.
To return the hub to the factory default settings, switch it on, then hold the power button for 30 seconds (logo will start blinking red).
At the same time, all the connected detectors, room settings and user settings will be deleted. User profiles will remain connected to the system.
After adding the hub to the account, you become the administrator of this device. One hub can have up to 50 users/administrators. The administrator can invite users to the security system and determine their rights.
Events and Alarms Notifications
The hub notifies users of events in three ways: push notifications, SMS and calls.
Notifications are set in the menu Users:
|Event types||For what it is used||Types of notifications|
- Push notification is sent by Ajax Cloud to the Ajax Security system app, if an Internet connection is available.
- SMS is sent to the phone number indicated by the user when registering the Ajax account.
- The phone call means that the hub calls the number specified in the Ajax account.
We call only in the event of an alarm to get your attention and reduce the feasibility of you missing an important alert. We recommend to enable this type of notification. The hub consecutively calls all users who have enabled this type of notification in the order specified in the Users Settings. If the second alarm occurs, the hub will make a call again but not more than once in 2 minutes.
The call is automatically dropped as soon as you answer it. We recommend you to save the phone number associated with the hub SIM card in your contacts list.
Notification settings may be only changed for registered users.
The hub does not notify users of opening detectors triggering in the Disarmed mode when the Chime feature is enabled and configured. Only the sirens connected to the system notify about the opening.
Connecting a Security Company
The list of organizations connecting the Ajax system to the central monitoring station is provided in the Security Companies menu of the hub settings:
Contact representatives of the company providing services in your city and negotiate on the connection.
Connection to the central monitoring station (CMS) is possible via the SurGard (Contact ID), ADEMCO 685, SIA (DC-09), and other proprietary protocols. A complete list of supported protocols is available at the link.
Check the operational capability of the Ajax security system on a regular basis.
Clean the hub body from dust, spider webs and other contaminants as they appear. Use soft dry napkin suitable for equipment maintenance.
Do not use any substances containing alcohol, acetone, gasoline and other active solvents for cleaning the hub.
- Ajax Hub
- SmartBracket mounting panel
- Power supply cable
- Ethernet cable
- Installation kit
- GSM start package (available not in all countries)
- Quick Start Guide
While installing and using the hub, follow the general electrical safety regulations for using electrical appliances, as well as the requirements of regulatory legal acts on electrical safety.
It is strictly prohibited to disassemble the device under voltage. Do not use the device with a damaged power cable.
|Devices||up to 100|
|Groups||up to 9|
|Users||up to 50|
|Video surveillance||Up to 10 cameras or DVRs|
|Rooms||up to 50|
up to 5
|Number of connected sirens||up to 10|
|Power supply||110 – 240 V AC, 50/60 Hz|
|Accumulator unit||Li-Ion 2 A⋅h (up to 15 hours of autonomous operation in case of inactive Ethernet connection)|
|Energy consumption from the grid||10 W|
|Radio communication protocol with Ajax devices||
|Radio frequency band||866.0 – 866.5 MHz
868.0 – 868.6 MHz
868.7 – 869.2 MHz
905.0 – 926.5 MHz
915.85 – 926.5 MHz
921.0 – 922.0 MHz
Depends on the region of sale.
|Effective radiated power||8.20 dBm / 6.60 mW (limit 20 mW)|
|Modulation of the radio signal||GFSK|
|Radio signal range||
Up to 2,000 m (any obstacles absent)
|Communication channels||GSM 850/900/1800/1900 MHz GPRS, Ethernet|
|Operating temperature range||From -10°С to +40°С|
|Operating humidity||Up to 75%|
|Overall dimensions||163 × 163 × 36 mm|
|Service life||10 years|
|Certification||Security Grade 2, Environmental Class II SP2 (GSM-SMS), SP5 (LAN) DP3 in conformity with the requirements of EN 50131-1, EN 50131-3, EN 50136-2, EN 50131-10, EN 50136-1, EN 50131-6, EN 50131-5-3|
Warranty for the Limited Liability Company “Ajax Systems Manufacturing” products is valid for 2 years after the purchase and does not apply to the pre-installed accumulator.
If the device does not work correctly, you should first contact the support service—in half of the cases, technical issues can be solved remotely.
Technical support: [email protected]