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

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 responsibility for any security failures should safe mode be disabled. The integrator agrees that they have advised the customer of the potential security failure prior to disabling safe mode. By disabling safe mode the integrator agrees that any liability for such security failures falls on the integrator and/or end-user. The integrator agrees to indemnify Chowmain for any loss or damage suffered due to any indirect, incidental and/or consequential damages, lost/stolen property, lost business, lost/stolen savings, lost profits or revenues resulting from a breach of this agreement and shall include all costs, expenses and reasonable attorney's fees incurred.


On systems with communications problems (particularly Serial systems which have been disconnected temporarily), or in other exceptional circumstances, bypass and arming commands may cause the opposite command to be activated incorrectly. This is due to the behavior of the ELK M1 ARM command which disarms when already armed, or bypassing which toggles when already in that state.

Whilst safeguards have been built in to help prevent this scenario (we check the state of the alarm shortly before), the state of the panel can potentially change during this time, or the state provided by the panel may be incorrect or corrupt, allowing the incorrect action to be executed.

For that reason, installers are now required to explicitly enable UNSAFE commands to acknowledge they understand the risks. Potentially safer workarounds when bypassing, unbypassing or arming include:
* M1 rules directly on the panel
* Use of Tasks

To accept the risk anyway, click the "Allow Unsafe Programming Commands" button in Actions, and press OK to confirm. The "Unsafe Programming Commands" Property will acknowledge the change, and the user will be notified that UNSAFE Mode is enabled.