CONTROL4 ELK M1: Unable To Arm / Disarm

For general troubleshooting, it is recommended to do the following first:

1. Ensure the driver is running the latest version of the Chowmain ELK V2 Driver. If the V1 driver is being used, it is recommended to remove and replace the driver with the V2 version. Right Click the driver in Composer and ensure the Device File is chowmain_elk_m1_v2.c4z
   
2. If the driver doesn't have a "cloud status" property, it is likely the original M1 driver from the Control4 database which was not developed by Chowmain and is no longer supported by Snap.
   
3. Ensure that the driver has an active trial or is licenced. The driver will not work if it is showing an expired trial
   
4. It is recommended that the panel is running 5.3.30 or later firmware. Versions older than 5.3.0 do not contain full arming support as required. However, numerous faults have been fixed since 5.3.30 which may affect arming 
5. Use the Display Diagnostics action (the output is shown in the lua tab) to check for any obvious errors
   

Common Issues

1. The most common issue is that the user permissions have Access incorrectly permitted. When Access is explicitly enabled for users, the ELK M1 API incorrectly treats the Arming / Disarming operation as a Door Unlock Request instead.
   
2. Alarm Arming/Disarming codes must be different to the codes used for door unlocking. You can find this permission in ELKRP >  Users > User > Ensure User Authorisations "Access" is unticked
   

For Programming,

1.  Unsafe mode must be enabled. More info is available in https://help.chowmain.software/portal/en/kb/articles/control4-elk-m1-programming-commands-in-composer-pro-programming-fail
   
2. Depending on the programming commands being used, you may need to add a default user code to the area

• Related Articles

• CONTROL4 ELK M1: Unable To Connect To Panel via Network

  For general troubleshooting, it is recommended to do the following first: Ensure the driver is running the latest version of the Chowmain ELK V2 Driver. If the V1 driver is being used, it is recommended to remove and replace the driver with the V2 ...

• Control4 ELK M1: Zone status does not correctly respond properly or Realtime status is not correct

  Ensure you are using the latest version of our ELK M1 V2 driver. You can identify this by right clicking on the device in System Design on Composer, and pressing Get Info. The filename must say chowmain_elk_m1_v2.c4z. If the original filename of the ...

• CONTROL4 ELK M1: Programming Commands in Composer Pro Programming Fail with "Safe Mode enabled in Properties" error

  Installers are now required to explicitly enable Unsafe mode to enable programming access to Arming, Bypass and Unpass commands. Once UNSAFE mode is enabled, it cannot be reversed. The integrator agrees and acknowledges that Chowmain takes no ...

• CONTROL4 ELK M1: Unable To Connect To Panel via Serial

  We recommend installers use Ethernet instead of Serial (via M1-XEP or other approved ELK ethernet M1 devices) as it enables improved troubleshooting, management and more reliable connectivity to the M1 panel For general troubleshooting, it is ...

• CONTROL4 ELK M1: Bypassed Zones show as Violated in Control4 Interface

  The Control4 Alarm Proxy does not provide support for showing bypassed zones in the customer interfaces. It only supports showing bypassed zones in Composer Pro. This is a limitation of the Control4 Alarm Proxy and not the driver. For that reason, we ...