M1XEP not connecting

[mmester]

Hi,

I have an M1 Gold with an M1XEP that was working for several years until a power failure a week ago. When AC power failed, the control went onto battery backup. The M1XEP was powered off the control itself (not a separate power adapter). After restoring AC power, the M1XEP stopped allowing connections via LAN. I don’t recall for sure, but there may have briefly been an “Ethernet Trouble” message on the keypad, but there isn’t anymore. Since that happened, I’ve put the M1XEP on a separate 12V, 1A power supply. I’ve disconnected and rebooted both the control and the M1XEP several times in different orders without success. The control itself seems to work fine, although I can’t get into ElkRP to investigate deeply.

The M1XEP gets an IP address via DHCP as usual and responds to pings for about 50 seconds reliably, then doesn’t return them for about 30 seconds, and comes back online. That and the status lights make it seem like it’s periodically rebooting. ElkRP is not able to connect securely or non-securely. The trace, linked below, indicates that it is contacting the M1XEP and receiving responses. When I try connecting non-securely, it gets to the state where it verifies the system identity but errors out during that step (saying the system didn’t respond).

Any ideas what’s going on here and how to fix it? I had been using a Home Assistant integration, but I’ve disabled it so that is unlikely to be the issue.

Trace from ElkRP is here: https://pastebin.com/vv5WmesJ

 

[amos]

Did you go into ElkRP and verify the M1XEP setup?

While you're in there, change it to a fixed IP address.
Its one less variable, and since the XEP is always on the network there's no need for dynamic assignment.

Also, post #2 here

ELK M1 not communicating to M1XEP anymore

Greetings; Something weird happened while I was overseas. I stopped being able to access the M1 remotely. When I came back home, I noticed that the ELK wasn't communicating with my ISY994 anymore either. ELK communicates via IP (M1XEP), not POTS. Normal behavior: - all dry contact...

cocoontech.com

RAL: "Another thing to check is to use the Find function in RP2 (under M1XEP Setup) and check the MAC address. Does it match what the label on the M1XEP says it should be? There is/was a problem with the M1XEP where it would randomly change it's MAC address, causing the connection to be lost. "

 

[mmester]

Thanks for the reply. I've checked the setup in M1XEP and tried the 'Find' function as well. The setup is correct. 'Find' doesn't locate the device, although the trace indicates it's making some amount of contact. The MAC address is correct and the device responds to pings periodically at the expected IP address (which is fixed anyway in this case). It just seems like it can't stay up long enough to complete the process.

 

[RAL]

What firmware level do you have running on the M1XEP?

 

[mmester]

I'm not sure about the firmware version and I don't know how to check when it's not connecting. I did update it relatively recently (in the last few months) and have connected to it many times via my Windows 10 machine, so I don't think the issue is SSL / TLS incompatibility.

 

[RAL]

T

I'm not sure about the firmware version and I don't know how to check when it's not connecting. I did update it relatively recently (in the last few months) and have connected to it many times via my Windows 10 machine, so I don't think the issue is SSL / TLS incompatibility.

The latest M1XEP firmware is 2.0.51. .You can use the M1XEP Diagnostic program to check what level yours is at. But if you did a recent update, I agree, your problem is not due to the issues with SSI/TLS.

 

[BraveSirRobbin]

Since you have a hard IP set address, have you tried connecting directly to the M1XEP? Perhaps that power outage damaged some of your network equipment.

You may have to assign an IP on the same subnet with your laptop/computer temporarily to do this.

 

[Mark S.]

FWIW, my M1XEP has reverted to the default IP address about 3 times in the many years I have had it. I don't know why it happens, but I suspect it is power-related. So ELKRP address did not match the actual M1XEP address, and I could not connect. Obviously I had to set the M1XEP address back to my chosen address again.