Chowmain - ELK M1 Security Panel Driver Version 2

[alanchow]

Overview

Chowmain releases new ELK M1 security panel driver for Control4. This driver is a brand new driver we have written from the ground up that is even better than the original M1 driver we wrote two years ago. This new driver utilises the same licencing as the original driver and as such comes at no additional cost to existing licence holders.

Elk's M1 Controls incorporate security, fire, door entry control, and energy & task management to provide total control of home or business. By working with products from over 50 partner manufacturers the M1 Gold offer a truly integrated solution. These IP accessible systems offer simple, yet powerful on-site and remote user interfaces, giving the consumer full control anytime, from anywhere.

The Chowmain M1 driver for Control4 offers extensive integration of the M1 functionality to truely expand Control4's functionality to not only security based services but also occupancy and input/output expansion for automation tasks and is compatible with both Ness and ELK M1 systems.

The Chowmain ELK M1 driver is compatible with both Ness M1 and ELK M1 systems via RS232 or IP connectivity (requires optional ELK-M1XEP Module)

Driver Features

End User Interface Features Include

• Full support for all 8 areas
• Large variety of arming modes - Away, Stay, Stay instant, Night, Vacation, Disarm
• Bypass/unbypass functionality
• Alarm Code change function (Can be disabled by Installer)
• Virtual Function Button Support - F1,F2,F3,F4,F5,F6
• Fire, Panic, Police and Medical Emergency functionality built into alarm (Requires configuration and testing by Installer).
• Invalid User Code Feedback
• Both detailed and simple Zone feedback options, with zone list
• Visual feedback of Warnings and Trouble
• History support with custom driver for display of alarm logs
• Output Control and Feedback for all outputs (requires configuration by Installer)

Installer Features Include

• Huge Library of events including Trouble, Function Key Feedback, Tasks and Keypad Accesses for Door Access
• Control and feedback of Function Keys via Configurable Keypads or Experience buttons (via BUTTON_LINK / CONTACT_SENSOR)
• Quickly Configure Push/Email notifications for major events
• Alarm State Events, including an improved Alarm Event.
• M1 and M1XEP version Feedback
• Powerful logging functions via Control4 Composer History
• User Accessible Alarm Code Modification (can be disabled by Installer).
• M1 Counters (Requires Manual Polling by Installer)
• Automatic Clock Sync
• Temperature integration
• Basic support for M1 Lighting. Lights, Relays and Dimmers integration via M1 for greater integration and Advanced Lighting Support.
• Zone integration via Contact Closure
• Advanced system to allow override of arming modes using custom programming or prompt for custom PIN number
• Prompt for Custom PIN for custom commands
• Powerful Commands are provided including:
  • Activation of Tasks
  • Bypass Zones. Unbypass Zones or partitions.
  • Change User Code
  • Display Text On Keypad
  • Function Key Presses
  • Polling/Writing of M1 Counters
  • Speak Phrases or Words
  • Panel Clock Sync
  • Toggle Outputs
  • Zone Triggers

FAQ

What are the benefits of the V2 driver over V1

The list of benefits is huge, but, here are some of the major ones

• New History / Log Interface Driver. View ELKRP Logs in realtime.
• Completely rewritten communications system with huge benefits improving reliability and speed
• Optimised for Core Controllers (or later) and CA-10. These Controllers are even faster
• First time load is now significantly better on all controllers
• Output bindings are named
• Interact with your Keypad Function buttons in new ways using our new Button Links + Keypad Illumination bindings
• Use Custom Ports. 2101 is no longer required
• Huge List of New variables. Virtually limitless programming options available
• Custom arming modes system.
• Arming now detects open zones
• And lots more

Why was the ELK Lock Driver Removed in V2?

• The ELK Lock Driver requires a rewrite, and is not compatible with the new V2 driver. There is no ETA for its return. We recommend using the Door Access Events and Access Users in ELKRP instead.

Can I automatically upgrade between V2 and V1

• Due to the major upgrades between V1 and V2, the driver upgrade is a manual process, as the drivers are designed differently.
• The lighting drivers hare compatible with both V1 and V2, and the connection can simply be moved to the new driver.

What cool things can driver do?

• If you are using RS232 based communications the clock on the keypads usually drift after a while. The driver will automatically sync the clock to the controller's time so that it will always be accurate.
• The driver provides push and email notificaitons without programming for all major events. This is useful for the home owner to know who armed or disarmed the area.
• Keypad bindings for keypad function buttons and RF keyfob buttons makes it easy to program the driver.
• History Driver allows the customer and Installers to review whats happened in their home easily without ELKRP.
• Perform custom arming for different arming modes. Instead of arming Vacation mode for instance, you can turn off the house, provide feedback to the user and then execute a task on the panel, for it to perform additional tasks before executing vacation mode
• Provide Experience buttons which utilise the Keypad Function Illumination feedback to trigger actions on the alarm. Or even bind function buttons on the keypads to Configurable keypads

What module is required to connect to the panel via network

• Whilst this module supports serial, we recommend the use of IP, using a M1-XEP module which also helps facilitate reconfiguration of the panel locally or remotely (with port forwarding or a seperate VPN server/router), without the requirement to disconnect the Control4 system. Keep in mind, whilst connected in ELKRP, Control4 cannot connect properly to the Ness M1, but will automatically try to reconnect after ELKRP has disconnected
• The C1M1 has not been tested by Chowmain, but we have been provided feedback by users that it does operate

I'm typing the correct code, however, disarming or arming does not operate

• In ELKRP, ensure that the "Access" permission is unticked for the user.
• "Access" is used for door access controls instead of arming / disarming and when enabled, will treat the code as a door access attempt should not be enabled for general alarm usage or most installers.
• If Access permissions are granted, attempts to arm or disarm the system from Control4 will not disarm the system, but instead incorrectly trigger a door access event instead.

I'm getting Keypad doesn't exist errors

Ensure every partition you control has a NESS keypad available for control4

There is missing information in the M1 interface (Zones improperly named, or other information missing).

Re-Run Auto-Setup. It may have been incorrectly interrupted

Auto-Notifications are not sending.

• Auto-Notifications requires a 4Sight subscription.
• Check Spam.
• Check that your panel has been set up properly

When executing programming commands, the client is notified of "SAFE MODE" errors.

Use of Bypass, Unbypass and Arming commands require SAFE Mode to be disabled by the installer. For more information, on SAFE MODE, refer to Quickstart information provided with the driver or the full driver manual

Do you offer showroom discounts?

We offer dealers a free showroom licence for demonstration and educational purposes. See link below for T&C's and signup procedure.

Chowmain Dealer Showroom FAQ

I want to try this driver out before buying it?

All Chowmain drivers for Control4 come with a 90 day trial.

How do I find out more information about the driver?

Please see the links below for more information about the driver.

Driver Link

 

[C4 User]

I know this is off topic but is the elk m1 gold a diy system? Meaning can I as homeowner install and program the system? I currently have the DSC Neo that I plan to replace. 

[alanchow]

8 hours ago, C4 User said:

I know this is off topic but is the elk m1 gold a diy system? Meaning can I as homeowner install and program the system? I currently have the DSC Neo that I plan to replace. 

It is not a DIY system.

[Olichops]

I had an Elk M1 and it was easy to program. If you can use composer you can do the ELK unless they added some dealer only BS

[Andrew Cruz]

Many issues with system falling offline and coming right back online.  

[Andrew luecke]

2 hours ago, Andrew Cruz said:

Many issues with system falling offline and coming right back online.  

We have a beta which has so far fixed this for mostly everyone. Your dealer needs to submit a ticket.

Also, if you're using the cbus m1 module, keep in mind it seems to be an issue with the module itself. Old firmware also causes issues (particularly m1xep v1.x firmware)

[Andrew luecke]

G'day,

Just some updated info. ELK have identified an issue which may cause an issue on some systems (particularly with our driver). We've only seen it on 2 or 3 systems so far personally. We can provide affected dealers with updated firmware that should fix it. We've been trying to track this one down for weeks / months

But it happens during some operations, and causes a loop where the driver keeps reconnecting on our stable driver (or the betas). In the latest beta of our driver though, even when the firmware issue is triggered, it no longer reconnects, but Display Diagnostics now detects when the issue has occurred.

 

Andy

[Andrew luecke]

G'day,

Good news. Whilst many people have been using the betas already, 20240819, and then 20240821 has been moved to production on our new online marketplace (and I'd like to thank everyone who tested the betas). Please note, that due to the breadth of this release, this is not an automatic upgrade from earlier builds. It can be downloaded from: https://chowmain.software/drivers/control4-elk-m1

The summarised changelog is below (due to the size of this update, some features/enhancements/optimisations may have been missed from this list):

 

Major Changes

• Chowmain Licensing Support. Support for our new Marketplace, including all of the new features
• Huge Improvements to Performance. At a bare minimum, one particular optimisation sped up panel connecting time 20% without any further changes by improving the CPU efficiency. Another unique optimisation improved logging speed for 10000 entries from 6631ms to 60ms processing time. Any action which generated a log entry on the panel is also substantially more efficient
• Output Names, Area Names, Counter Names and Zone names are only downloaded on "Read From Panel" Operation and first time. If you want to update them you can now use our new Update XX Name actions, or use our new Auto Update XXX Names to follow the old behavior. This provides substantial improvements to reconnection time
• Major Improvements to Outputs/RELAYS
• Improvements to History
• Major Bug Fixes
• Display Zone Numbers In Interface is now only used during Initial Read and "Update Zone Names" operation.
• Huge Improvement to reconnection speed, with substantial improvements
• Significantly improved troubleshooting and diagnostics
• Replace and overhaul Backend for History custom interface for improved experience and to address some bugs with the framework

Features (20240821)

Panel V2:
- [Bug] Fix multiple arm/disarm notifications which have been observed on one system on first connection (only observed on RS232) after upgrade to 20240819.
- [Bug] Fix minor driver anomaly which is due to log data being received before the correct stage before panel configuration is known
- [Bug] Handle race condition which may occur in stage 3/4 where log data is received, but the states might not be fully set up. This has never been observed in production.
- [Performance] Move Auto Update Name operations to Stage 3 before realtime state data is handled. This can improve the connection rate in some circumstances
- [Performance] Ignore Log data operations during startup until stage 5.  This avoids driver anomolies and improves performance, however some variables will now only be updated when fully connected.

 

Features (20240819)
All:

• [Licencing] Support Chowmain Licencing
• [Troubleshooting] Support for Extended Diagnostics and Related Diagnostics.
• [Performance] Huge Performance Improvements
• Some tests as an example showed improvements from 6631ms to 60ms processing time.
• Print Debugging turns off now after 24 hours automatically

Panel V2:

• [Bug] Display Zone Numbers In Interface is now only used during Initial Read and "Update Zone Names" operation. This prevents circumstances in new drivers where the Zone names keep showing "XXX [ZONE NUMBER][ZONE NUMBER][repeat...]"
• [Troubleshooting] Add New Broken ZoneStatus Checks. We've encountered a firmware issue where ZoneStatus data gets corrupted (it is believed to be caused by Bypass operations). When encountered, this causes an infinite boot loop.
• [Troubleshooting] New internal logs to help narrow down broken ZoneStatus Checks
• [Workaround] Provide "Validate Command Transmissions" property. This disables command checks. If you need this, you generally either have a firmware issue, configuration issue, or hardware issue (generally caused by CBUS Module). This option should only be used in extreme cases and WILL likely cause side effects, such as potentially incorrect panel states
• [Bug] Fix Output Feedback
• [Bug] Fix Control of Outputs 108-208
• [Speed] Reduce CPU Usage during Connection by generating zones differently
• [Speed] Do not Automatically download latest Output Name, Area Name or Counter Names. Instead, only download during read panel, and allow updates using "Update XXX Names" action. This will reduce CPU usage during connection and speed up connection time.
• [Speed] Reduce Redundant Logging.
• [Improvement] Delay Initial connection for 15s
• [Fix] Remove Display Wiegand Directory. V2 doesn't have lock Support
• [Improvement] Better Protection against faulty Comms data
• [Bug] Fix Issue with Trouble Status Crash
• [Bug] Resolve issue with Zone Definitions. This also improves Auto-Configuration of Zones
• [Bug]: Fix Crash triggered in some circumstances caused by binding issues
• [Usability] Better handling of Zone Trouble State. Treat them as Open. Unfortunately, C4 doesn't support Trouble states
• [Crash] Resolve Driver Crash on Reboot
• [Bug] Fix Function Keypad numbers
• [Performance] Cache History Log generation. Logs are rendered only once, the result is cached, and reused. On some systems without many log updates, this should improve latency/performance at the cost of a small amount of memory. On "noisy" systems, the memory is expected to be freed quickly anyway
• [Performance] Don't try to send or render Logs if there is no history agent in ANY circumstances
• [Performance] Update Logs in Realtime, only if a History Client is connected
• [Performance] Don't update History clients during driver Start, unless they're connected. This should speed up driver connection time
• [Miscellaneous] Improvements to Diagnostics
• [Memory/Performance] Limit Maximum Log size to 520 entries. This prevents the logs growing until a infinite size
• [Workaround] Minimum Firmware now recommended is 5.3.30. Previous firmware versions may cause an infinite connection loop during specific Zone Bypass operations

History V2:

• Improvement/Bug] Upgrade custom interface to new framework. Old framework was depreciated upstream. This may fix some bugs (particularly long term)
• [Workaround] Workaround potential issue we've seen affect other drivers in extremely rare circumstances. This driver we do not believe is affected, but have added the workaround to be safe
• [Bug] Fix Issue with Log Transfers between History and Alarm in some circumstances (History)