The ELK security panel has excellent two way integration with myServer 6. It is the preferred security panel for use in a new installation or retrofit because of the high level of solid support.
It also supports limited automation capability.
As a dealer / end user, you decide where the automation rules are maintained - in the ELK panel or in myServer 6 rules.
The driver supports more than one ELK panel though this should be rare considering the expandability of one ELK panel.
The ELK can be connected to myServer 6 via a serial cable, via TCP (Elk's XEP), ELK Dual path communicator, or via Ser2Net software running on a ethernet connected Raspberry PI4
Supported possible ELK data elements:
Areas (8) (Supported) - Tracks status of area. Arm/Disarm/Stay, etc.
Keypads (16) (Supported) - Some ELK keypads provide temp, some don't. Sensors count towards myServer 6 device licenses if enabled.
Zones (208) (Supported) - Hardwired and wireless Sensors, etc. These count towards myServer 6 device liceneses. You can enable / disable these in myServer 6 dashboard to reduce the device count.
Output (64) (Supported) - Some physical (hardwired) Voltage only, relays, or a combination of the two. Can be used to actuate door locks, motors, fan, pumps, etc, some virtual used for internal tracking/flags on rules. These count towards myServer 6 device liceneses.
Lights (256) (Supported) - Usually either X10 or Insteon, or z-wave. These count towards myServer 6 device liceneses.
Tasks (32) (Not sure supported) - A tasks is similar to a computer macro. The logic of what the task does is controlled internally by the Elk rule engine.
Counters (64) (Supported) - Counters/flags, can be set, incremented, decremented.
Custom Setting/value (20) (Potentially supported) - Static values used in ELK rule engine.
Per ELK manual:
Type (TT) Range (NNN)
0 = Zone Name 1 – 208 Each Zone is considered a myServer device towards licensing. They are "Security family" devices.
1 = Area Name 1 – 8
2 = User Name 1 – 199
3 = Keypad Name 1 – 16
4 = Output Name 1 – 64, No name for 65 – 208 Each Output is considered a myServer device towards licensing. They are "Control family" devices.
5 = Task Name 1 – 32
6 = Telephone Name 1 – 8
7 = Light Name 1 – 256 Each Light is considered a myServer device towards licensing. They are "Lighting family" devices.
8 = Alarm Duration Name 1 – 12
9 = Custom Settings 1 – 20
10 = Counters Names 1 – 64
11 = Thermostat Names 1 – 16 Each Thermostat is considered a myServer device towards licensing. They are "Climate family" devices.
12 = Function Key 1 Name 1 – 16, NNN = Keypad number
13 = Function Key 2 Name 1 - 16
14 = Function Key 3 Name 1 - 16
15 = Function Key 4 Name 1 - 16
16 = Function Key 5 Name 1 - 16
17 = Function Key 6 Name 1 – 16
18 = Audio Zone Name 1 – 18 for use by M1XEP (though audio is supported by the ELK, Allonis recommends all media functions be managed directly by myServer)
19 = Audio Source Name 1 – 12 for use by M1XEP
The ELK supports the common monitoring service technical requirements:
Contact ID, SIA, Pulse 4/2, Pager DTMF Tones, Voice Message, Ethernet (Internet or Cellular)
Install and setup the ELK panel using ELK's Windows RP program.
Get the ELK on the IP network using ELKs ethernet module. Or, connect a DB9 serial cable to a USB to DB9 adapter. Plug the USB into the myServer 6 Pi4's USB port (USB2 is fine). Or, if on Windows, plug the cable into a DB9 RS232 port or plug the USB Adapter into the PC's USB port. Go to Device Manager to determine which COM port the adapter was assigned.
Download and install driver from myServer 6's Software Updater.
Once installed, find it in the Drivers tab.
Click on Configuration on the ELK driver.
Run the Add network (or serial) controller command
Click on all fields. Then modify the command for your particular system. If serial, enter "com5" if your device is on Com 5.
Note that RS232 connected panels connect at 115,200 baud.
Once your panel has been added, run the GetConfig command for that panel's device ID. Your list of ELK RP defined zones and devices should now populate.