1. It is not possible for the direct CMS link to connect to multiple monitoring services concurrently. If you wish to use this driver and also have monitoring with a 3rd Party Security Company, you can utilise the Cloud Signaling method for security monitoring. More info here. This driver can only use the direct connection.
   
2. By default, device alarms are only received by the driver when the system is in the ARMED state. If you wish to utilise this for automation, please refer to the "Setting Devices up as Zones" section in the Installation Guide for more info
   
3. There are no exit/entry delay events received, so the Control4 UI will not show these.
   

What forms of communication does this driver use?

1. This driver uses cloud communication when issuing commands (Arm/Disarm/Functions) and the CMS link locally (SIA DC-09 protocol) to receive feedback events.
   
2. An invitation to Chowmain in the Installers/Companies Hub settings is required to authorise the driver to communicate with the Hub. Please refer to the "Ajax Settings" section in the driver installation guides for more info.
   

What hardware will this driver work on?

1. This driver is compatible with all versions of the Ajax Hub. For a detailed compatibility of devices, you can find more info here
   

Can the driver trigger Ajax Relay devices?

1. Due to rate limits, this feature has not been implemented in the driver. If circumstances do change in the future, we may re-visit this.
   

Why are device instrusion alarms not changing the driver to an Alarm State?

1. Because the driver has the optional ability to integrate with device alarms (these won't change the state of the Group in the driver to Alarm eveytime there's a trigger). To ensure alarms are shown accurately, configure the instrusion alarm confirmation settings within Ajax. More info here