ELK M1 Gold WHENEVER/THEN Rules: Syntax, Examples, and Common Mistakes

WHENEVER/THEN is the M1 Gold's conditional automation engine. The WHENEVER block defines the trigger condition, such as a zone state change, time event, security mode change, or combination. The THEN block defines what happens when that trigger fires. Rules are created and managed through ElkRP software and stored on the panel. Each rule evaluates independently on every scan cycle, firing its THEN actions when the WHENEVER condition transitions from false to true.

Yes, but there is no automatic conversion tool from ELK and no published migration guide. Each OmniPro II rule needs to be manually decomposed into its trigger logic and action logic, then rebuilt using M1 Gold WHENEVER/THEN syntax. The concepts are similar but the implementation differs significantly, especially for compound conditions, UPB scene control, and security mode interactions. AntlerBridge was built specifically to handle this translation.

The M1 Gold supports a substantial number of rules, but the practical limit depends on rule complexity and available panel memory. For most residential and light commercial installations, you will not hit the hardware limit. However, excessive rules with overlapping conditions can create performance and debugging issues. Best practice is to consolidate where possible and document your rule logic outside the panel.

The most common causes are: the WHENEVER condition is checking for sustained state instead of a transition, the zone type does not match the condition type, the rule order creates a dependency that has not been met, or there is a timing conflict with another rule acting on the same output. Start debugging by isolating the rule (disable all others) and manually triggering the WHENEVER condition while monitoring in ElkRP.

M1 Gold supports time-of-day, day-of-week, and sunrise/sunset-based conditions within WHENEVER blocks. You can combine time conditions with zone or security state conditions using AND logic. Be aware that the M1's internal clock must be properly set and maintained. If you lose the real-time clock battery, time-based rules will fire at incorrect times or not at all.

OmniPro II used a flat numbered condition/action system where conditions were evaluated independently and linked to actions by number. M1 Gold uses an explicit WHENEVER/THEN pairing that makes the trigger-to-action relationship visible in the programming interface. This is structurally cleaner but requires a different mental model, especially for installers who have years of OmniPro II muscle memory.