Jump to content

ELK Module Setup


ooker

Recommended Posts

Posted

Here's some info on setting up the ELK Module with an ISY-99i. This info is a result of spending too many hours today working with the UD support folks to troubleshoot my system:

 

These steps were used successfully with an ELK M1 Gold using this config:

ELK M1 Gold: v4.6.8

ELK M1XEP: v1.3.28

ISY-99i Pro/IR: 3.1.13 Beta

ISY-99i ELK Module (separate software purchase from within the ISY-99i Admin Console)

 

1) Enable Non-secure Port on the ELK M1XEP

The ISY-99i ELK Module needs the non-secure port enabled. The ELK Module uses the non-secure socket to communicate with the ELK M1XEP module.

-Launch the ElkRP app and do the following:

-Connect to the ELK (Connection -> Connect )

-Go to the Account Details:System

-Click on the [M1XEP Setup] button

-Check the "Enable Non-Secure Port" checkbox and note the port number (default = 2101)

-If you are using a static IP address for the M1XEP (this is recommended) then verify that the IP settings are still correct

-Send the config (ElkRP->M1)

-Reboot the M1XEP

-Verify that you can communicate with the M1XEP via a non-secure socket

-In the Account Details: System, note the port number user change the port to the non-secure port (e.g. 2101)

-Try to connect to the ELK (Connection -> Connect)

-If that works, you are good to go. Change the port back to the secure port for ElkRT (default was 2601)

-Note down the RP Access Code from the Account Details: System panel

 

2) Configure the ISY-99i ELK Module to communicate with your ELK M1XEP

-Bring up the admin console for the ISY-99i and do the following:

-Click on the Configuration tab

-Click on the Elk sub tab

-Enter the IP address of the M1XEP

-Set the port to the Non-Secure port number that you configured for the M1XEP (default 2101)

-Enter the access code (the RP Access Code was recommended by UD support)

-Enable the ELK M1XEP by clicking the "Enabled" checkbox

-Click the [save] button

-Click the [Refresh Topology] button to load the topology (e.g. areas, zones, etc. from the ELK)

 

 

Troubleshooting:

Symptom: If the Elk is configured, the ISY-99i Admin Console is slow and un-responsive. The ElkRP software does not connect/transfer data reliably. The data about the ELK is not loaded into the ISY-99i (you don't see the zone and area topology)

Solution: You most likely have the ELK Module in the ISY-99i configured with the secure port on the ELK M1XEP (e.g. 2601), and the result is that the ISY-99i apparently floods the network trying repeatedly to connect to the secure socket, even though it requires a non-secure socket.

 

 

Note: This does not cover all the config nor all the potential issues that one may encounter, but hopefully this will help others get their ELK Module configured.

Guest
This topic is now closed to further replies.

×
×
  • Create New...