zorax2 Posted January 15, 2023 Share Posted January 15, 2023 (edited) An important note that isn’t currently on the eisy wiki page for initial setup and migration is that the Elk Portal from our ISY 994s does not work with eisy. You need to the install the PG3 Elk Node Server to get the Elk M1 to integrate with your eisy. I wasn’t able to find a full step-by-step process in one place on the Elk help thread nor the Github pages on how to setup the Elk node server with Polyglot 3 (PG3) and had to do a lot of searching the forum to figure out how to do this as a newbie to the eisy, PG3 and node servers. I’ll attempt to go through the steps I took to get things working as the steps were not completely obvious to me as I came from the ISY994 with the Elk Module to the new version of Elk on PG3 with the eisy. I may miss some intermediate minor steps but these steps should help you get to the finish line for getting ELK installed and operating with your eisy. 1. Use Elk RP2 and configure the ME1XEP setup in the account details. Click on M1XEP Setup, go to TCP/IP settings tab, click on the box “Enable Non-Secure Port” and change / add port number 2101. The secure port should remain 2601. Log in / connect to your M1 via RP2 and make sure that it updates this configuration so that you can use port 2101. 2. Check your router to ensure you have the correct IP address for the Elk M1 on your network. My router showed the name as “Digiboard” rather than Elk. Once you have the IP address for your Elk, configure a manually assigned / reserved DHCP IP address on your router. If the IP address isn’t an reserved IP address and the address of the M1 changes on your router, it will break the link to the Node Server. 3. Get access to Polyglot 3. I had trouble initially getting access to it. I tried from both the ISY Launcher and Admin Console. At times, it wouldn’t take my password so I wasn’t able to log in. Somehow, I ended up with access to the Polyglot 3 server and this is where you need to be. Check the PG3 sub-forum if you run into issues here. I have no idea as to why I had trouble with this. Nevertheless, you’ll need to get to the PG3 webpage to move further in the process. 4. Go to the node server store on PG3 and purchase the Elk Node Server and install the trial or purchased version of the Elk Node Server. 5. You cannot do initial configuration of the Node Server via the UD administrator console. I didn’t realize this and tried to use the Elk selection in the Node Servers tab at the top and tried adding nodes there. Nope – this does not work. It wasn’t obvious to me as a new user so I thought I should point it out. 6. Now that you have installed the Elk Node Server, access it via the Polyglot 3X webpage. Click on details to connect to the Elk Node Server. 7. Configure your Node Server by clicking on “Configuration” between “Nodes” and “Log” to get to the Custom Configuration Parameters below. 8. For the “host”, as described in the instructions, add the IP address for the M1 from your router along with the non-secure port number 2101. The sample instructions use 192.168.1.15:2101. Simply use your IP address followed by the colon and 2101. Enter your user code. The user code is essentially the password of a user created within RP2 “users”. In my case, User 001, the passcode and my chosen User Name “EISY console” is shown on my RP2 user page. Enter this password / user code into box next to “user code”. 9. Check the number of areas you defined in RP2. Most people will likely have 1 area so enter “1” in this box. 10. For outputs, go to your RP2 configuration page. Go to Automation, Outputs to see what range of outputs you are or will be using. My RP2 page shows 64 total outputs. I selected a range of 1-16 (no spaces before or after hyphen) as I won’t be using more than that. 11. I left change node names as “false” as that was the default. I’ll have to learn a bit more before I make changes there. 12. Save the changes. 13. Click restart. I clicked on “Log” to see ensure that a connection had been made to the Elk. 14. Go to the Administrator Console for your EISY. Select Node Servers, Elk, Add all Nodes. 15. If successful, the Elk Controller and Elk Outputs, Zones and Controllers will show up on the left side where your devices are found. 16. At the top of the list of names of your zones will likely be “Home”. Click on “Home”. This will bring you to the current status of Area 1 of your alarm system. There is now a dropdown box that you can change to arm, disarm, etc. Choose what you would like to do and then click the dialog box “Set armed Status” to whatever you’ve selected. This process is different from the Elk Portal Module where the Armed status was listed next to the “Main”, “Programs”, “Configuration” part of the Administrative Console. That’s it. Hopefully this got you on track to start using the Elk module on your eisy. Edited January 16, 2023 by zorax2 Do not do step 14. Link to comment
Jimbo.Automates Posted January 16, 2023 Share Posted January 16, 2023 Your steps are all good except, do not do #14.Sorry all the details of adding a node server are not part of the ELK node server instructions. That should be created for the new users.Sent from my Pixel 6 Pro using Tapatalk Link to comment
zorax2 Posted January 16, 2023 Author Share Posted January 16, 2023 30 minutes ago, Jimbo.Automates said: Your steps are all good except, do not do #14. Sorry all the details of adding a node server are not part of the ELK node server instructions. That should be created for the new users. Sent from my Pixel 6 Pro using Tapatalk Change specified (do not do step #14) made to the original post. Thank you for reviewing the steps. 1 Link to comment
Recommended Posts