Buzzed Posted October 25, 2011 Share Posted October 25, 2011 I exported the lighting file from my 991 and imported it into Elk but I can't get Elk to turn any of the lighting on. I have included screenshots of a simple rule created to test the lighting, that failed. Link to comment Share on other sites More sharing options...
Buzzed Posted October 25, 2011 Author Share Posted October 25, 2011 And here Link to comment Share on other sites More sharing options...
polexian Posted October 25, 2011 Share Posted October 25, 2011 Write this rule to test your elk. Every 15 seconds Turn on light for 10 seconds Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Buzzed Posted October 25, 2011 Author Share Posted October 25, 2011 I made the rule and sent it to the M1 but still no change Link to comment Share on other sites More sharing options...
polexian Posted October 25, 2011 Share Posted October 25, 2011 Is your elk and isy on the same subnet? Can you ping both of them? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Michel Kohanim Posted October 25, 2011 Share Posted October 25, 2011 Hello Buzzed, Please make sure that: 1. M1XEP is enabled for un-secure communications on port 2101 2. ISY is configured for port 2101 and your ELK's IP address 3. You do not have ELK RP connected simultaneously With kind regards, Michel Link to comment Share on other sites More sharing options...
Buzzed Posted October 25, 2011 Author Share Posted October 25, 2011 Michel when I go to ElkRP account details it shows that secure port 2601 is used. When I go into M1XEP setup/TCP/IP settings I check enable non secure port 2101. I then make sure that I have a good network connection and send the changes to the M1 panel. I then manually reboot the M1XEP but in the account details it still shows secure port 2601. Why are the changes reverting back to the original port? Link to comment Share on other sites More sharing options...
polexian Posted October 26, 2011 Share Posted October 26, 2011 Michel when I go to ElkRP account details it shows that secure port 2601 is used. When I go into M1XEP setup/TCP/IP settings I check enable non secure port 2101. I then make sure that I have a good network connection and send the changes to the M1 panel. I then manually reboot the M1XEP but in the account details it still shows secure port 2601. Why are the changes reverting back to the original port? Log into your isy admin console and go to configuration. Inside elk m1xep box you will need to put your elk ip address and port. for this I am going to use 2101, type in your security code, click save and generate elk export file. Save this file to your desktop. now lot into your elk through rp, connect to it through the network and click the m1xep setup. click tcp/ip settings at top, click enable non-secure port and put in 2101, then click SEND. Once it is all sent you will then reboot your elk. Once it comes back up, log into it again and re-import your lighting. click on automation->lighting. right click, clear all lighting. this will remove the old stuff right click import lighting data Send to control. Now go in and create 2 rules Every 15 seconds turn light on Send to control and close elk rp. Wait up to 30 seconds for the elk rp rule to take effect. This is the basic setup from scratch for elk-isy integration so this will work. Good luck. Link to comment Share on other sites More sharing options...
polexian Posted October 26, 2011 Share Posted October 26, 2011 Michel when I go to ElkRP account details it shows that secure port 2601 is used. When I go into M1XEP setup/TCP/IP settings I check enable non secure port 2101. I then make sure that I have a good network connection and send the changes to the M1 panel. I then manually reboot the M1XEP but in the account details it still shows secure port 2601. Why are the changes reverting back to the original port? Log into your isy admin console and go to configuration. Inside elk m1xep box you will need to put your elk ip address and port. for this I am going to use 2101, type in your security code, click save and generate elk export file. Save this file to your desktop. now lot into your elk through rp, connect to it through the network and click the m1xep setup. click tcp/ip settings at top, click enable non-secure port and put in 2101, then click SEND. Once it is all sent you will then reboot your elk. Once it comes back up, log into it again and re-import your lighting. click on automation->lighting. right click, clear all lighting. this will remove the old stuff right click import lighting data Send to control. Now go in and create 2 rules Every 15 seconds turn light on Send to control and close elk rp. Wait up to 30 seconds for the elk rp rule to take effect. This is the basic setup from scratch for elk-isy integration so this will work. Good luck. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted October 26, 2011 Share Posted October 26, 2011 Hi polexian, thanks SO very much for taking the time to post. That's precisely what needs to be done. With kind regards, Michel Link to comment Share on other sites More sharing options...
apostolakisl Posted October 26, 2011 Share Posted October 26, 2011 Michel when I go to ElkRP account details it shows that secure port 2601 is used. When I go into M1XEP setup/TCP/IP settings I check enable non secure port 2101. I then make sure that I have a good network connection and send the changes to the M1 panel. I then manually reboot the M1XEP but in the account details it still shows secure port 2601. Why are the changes reverting back to the original port? I similarly had troubles with my M1XEP not saving values. After an elk firmware upgrade I lost all my emails. I kept adding the emails back in, and then after the reboot they would be gone. In fact, the xep setup console would initially say that they were there, but when I clicked "receive" they would be gone. Apparently the xep console saves your last settings in the display without confirming that they are actually on the xep. I discovered that updating the ElkRP to the latest 2.0.10 fixed that problem. Previously, I had been using a version that was about 1 year old. 2.0.6 I think. Link to comment Share on other sites More sharing options...
Buzzed Posted October 26, 2011 Author Share Posted October 26, 2011 Well I feel like I took a step backwards because now the M1XEP won't connect to the network (it did before) and ElkRP can't seem to find it when I do the find. This internet stuff is the most challenging, at least for me. Link to comment Share on other sites More sharing options...
polexian Posted October 26, 2011 Share Posted October 26, 2011 Are you running windows 7? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Buzzed Posted October 27, 2011 Author Share Posted October 27, 2011 Windows XP Link to comment Share on other sites More sharing options...
polexian Posted October 27, 2011 Share Posted October 27, 2011 What version of firmware is your isy on? Also try power cycling the elk to get it to reconnect. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
polexian Posted October 27, 2011 Share Posted October 27, 2011 Double post Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Buzzed Posted October 27, 2011 Author Share Posted October 27, 2011 I have tried disconnecting the Elk battery and cycling off the panel as well as the M1XEP, and the DSL router. I have pulled the network plug on the ISY until I get the ElkRP to once again communicate with the local network. I get the error message Failed To Connect To Server whenever I hit the network button to connect. I do see a flickering green light at a point where the network cable plugs into the M1EXP so I'm assuming that it is seeing network traffic and I have a solid orange led lighted on the board itself. I'm assuming here that the ElkRP software initiates communication with the LAN 1st and this has nothing to do with passwords and RP access codes. The ElkRP no longer sees the M1XEP if I hit the find and search buttons. ElkRP reports V2.0.10 This system was communicating before messing with the ISY Link to comment Share on other sites More sharing options...
Buzzed Posted October 27, 2011 Author Share Posted October 27, 2011 Well I finally got the M1XEP back online. I pulled the network cable from the M!XEP then unplugged the unit. I then disconnected the battery from the Elk M1 panel and powered it down. I left everything as is for a couple of hours and when I powered everything back up the ElkRP was able to find the m1XEP. I then followed the rest of your instructions and the test lighting had the lights a-blinking! I set the lights to all illuminate if after dark the Elk panel alarms. I notice that sometimes all the lights come on and sometimes a few do not. Should I be thinking here about a SignaLinc phase coupler to get better results? Link to comment Share on other sites More sharing options...
polexian Posted October 28, 2011 Share Posted October 28, 2011 Not at all. When the elk module is released it will fix the light problem bright now the interface isn't great with the isy and elk. Im expecting the Eli module to be released soon, but that is just me. I have no insite on it and only micheal and the gang know the release time frame. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Buzzed Posted October 28, 2011 Author Share Posted October 28, 2011 Elk Module?? Can you please give me a link to that information so I can at least read up on it a bit, I have no idea what it's supposed to do? Link to comment Share on other sites More sharing options...
polexian Posted October 28, 2011 Share Posted October 28, 2011 Here is the topic everyone is following. http://forum.universal-devices.com/viewtopic.php?f=17&t=5331 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.