Jump to content

ooker

Members
  • Posts

    5
  • Joined

  • Last visited

ooker's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. ooker

    ELK Module Setup

    The UD folks have posted documentation here: http://www.universal-devices.com/mwiki/ ... ity_Module
  2. I ran into a number of issues getting the ELK Module setup. Unfortunately, it took most of the day and two support sessions with UD (they were very helpful). Unfortunately, there is not a lot of documentation about how to setup the ELK Module and the ELK M1XEP Ethernet interface for the ELK. So I wrote up what it took to get things working for me, here. I hope this helps other people who are trying to get their ISY-99i ELK Modules working: viewtopic.php?f=26&t=7415 Documentation on the ELK module is now available here: http://www.universal-devices.com/mwiki/ ... ity_Module
  3. ooker

    ELK Module Setup

    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.
  4. If I try to connect to my ELK M1 Gold (using the network) with the ELK RP software when my ISY-99i is powered up, I get a lot of errors, and it is very slow. If I unplug the ISY-99i, I can communicate with the ELK M1 from the ELK RP software just fine. Is this expected behavior with v3.1.13? I only just added the ELK and the ELK module, so I can't compare with previous releases of software for the ISY-99i I have the latest firmware on the ELK and on the ELK ethernet module. Also, regarding my previous post the issue is not specific to the mac for me. I've tried accessing the admin console via the standalone app and via the link from the web interface. I can typically click quickly between the Main tab and the Configuration tabs, but if I click on the Programs tab it can take minutes to come up or will get a socket error.
  5. I am trying to use 3.1.13 with the Elk module. I am using the admin Console App on a Mac. After connecting to my ISY-99i/IR Pro, I can click between the Main and Config tabs just fine. If I click on the Programs Tab or Elk tab, the admin console becomes unresponsive and eventually shows an empty alert window with a title of "Security Warning" After a very long wait (several minutes) I got a an Error alert "Socket Open Failed java.net.SocketTimeoutException" And after that, the Security Warning alert finally filled out with text and buttons saying "ISY is currently configured with the default SSL certificate..." I've tried several times to generate and install a new self-signed certificate without luck. I have cleared the Java cache and restarted the machine. Any suggestions?
×
×
  • Create New...