Need Help with ELKRP.

[sanders2222]

For years, I've used an I/O link on my garage door contacts to "light-up" a KPL button in my house when the doors were open. I also get email/text messages if the door is left open for 40 minutes or more and motion is not detected in the garage.

Early this year I installed my M1. At that time I ran some new wires over to my garage door contact switches. The wires were not connected to the switches but were patched to my M1 & set at "Normally Open". Just today, I finally got around to taking down my I/O link and connected the wires to the door contacts.

All connections look good as my ELK keypad shows the Garage doors violated (with doors closed) and "Ready" when they're open. I now need to change the M1 settings for the garage door zones to "EOL Supervised/RF". I cannot arm my system until this is addressed. However, I can't seem to log onto the ELKRP to change the settings.

I had a lot of trouble linking up the M1XEP when I initially set the system up early this year and it's been a while since I remember signing in to the RP. I don't recall how I eventually resolved the initial problem. It doesn't appear my network settings have changed nor has my ISY had communication issues with the M1. Anyone have any suggestions? I would assume I can make these changes from my keypad but I'd prefer making the changes from the RP.

 

[jpmargis]

However, I can't seem to log onto the ELKRP to change the settings.

Can you provide some details? Are you able to FIND the M1XEP? Are you able to connect? Are you getting an error message of some kind? Do you know the M1XEP IP address? Can you ping it?

 

[Del91574]

Without getting into the XEP, you have the contacts/zone definition backwards or wired incorrectly.

Do you know the local IP address set to the XEP by your LAN?

 

[sanders2222]

Sorry for omitting this information. The IP address and port that are displayed in the setup/find window do match that on my homescreen.

I think I logged into the system a month or so ago and it worked fine then. Nothing has changed since then so I don't know why I get a "Failed to connect to server" message now when I try to log into the system.

 

[jpmargis]

Try rebooting the M1XEP. Wait 10 minutes. Yes, TEN MINUTES. Then try to connect.

 

[sanders2222]

Try rebooting the M1XEP.

I can't recall ever having to do this, but it WORKED!. Once repowered, the software connectsed, updated the needed zones and my system is back up and armed. Thanks.

 

[tmbrown97]

Without getting into the XEP, you have the contacts/zone definition backwards or wired incorrectly.

He knows this - it's what he's trying to correct. Sounds like they were set to NO while the contacts weren't connected, and now he was trying to resolve it since finally hooking up the sensors.

 

[Del91574]

Slightly OT, and not sure if any other pros have noticed XEP's sitting on rock solid networks that simply don't allow connection after being up and running for months, but solved by a power cycle?

In my cases, all set for static IP's from a private pool.

 

[tmbrown97]

I only see it happen if something goes screwy while I'm working with it - like the app (computer or phone) crashes mid-communication, or something like that... then it takes a power cycle to reset it. That's the only time mine ever locks up, and it's only happened a half-dozen times or so in 5 years.

 

[Del91574]

I've got one site where every time I go there it seems like I need to reboot it...then again, the XEP isn't mapped outside of the local network and the system is being used as an access control panel and RP is commonly used to change users and credentials. I'm starting to think I might run the power through the on board relay and fire a rule daily in the early AM to reboot.

 

[tmbrown97]

I was just going to mention that... A long time ago, David aka Spanky posted a useful monitoring rule that would supervise the ethernet connection and upon loss automatically cycle the modem by using an output/relay to interupt power as you mentioned. Unfortunately I have to run in a few minutes and don't have time to search for it - maybe later tonight. I forget exactly what the trigger was he used but I'd try that before just an automatic reboot.

 

[Del91574]

Since the unit is on a Cisco switch and not mapped out anywhere, I'd tend to belive it's rock solid myself, but without running wire shark and going through all the logs....the rule is pretty easy to write up, Thinking it's a quirk with the XEP. My own house has done it a couple of times also.