TCP Secure SSL negotiation failed, code: -3

[Kristopher Farley]

info:
m1G: hardware- .11, boot ver – 3.3.6, control – 5.3.30
m1XEP: hardware – 1.0, boot ver – 2.0.4, firmware- 2.0.51

ever since about a week ago, my elk ELK-7TS is not longer able to connect to my XEP

i can obviously access the XEP via RP and i’m able to make changes to the unit but neither my 7TS nor my home assistant instance running the Elk integration can contact the XEP unit anymore.

when i check the trace i keep seeing the following:

4:38:57 Close_Socks: 16 = 00
14:38:57 UDP send to 255.255.255.255, Port: 2362, M1XEP
14:38:58 TCP SessionRead received: 10027F0000A5100373D4
14:38:58 ProcessTCP RP msg: 10027F0000A5100373D4
14:38:58 RpComms for control
14:38:58 From M1: 10027F0000A5100373D4
14:39:00 Open_Socks: 01 = 56
14:39:00 TCP Secure connection accepted
14:39:00 TCP Secure Received client hello
14:39:00 TCP Secure Begin SSL negotiation
14:39:00 TCP Secure SSL negotiation failed, code: -3
14:39:02 Open_Socks: 16 = 01
14:39:02 Close_Socks: 16 = 00
14:39:02 UDP send to 255.255.255.255, Port: 2362, M1XEP
14:39:07 Open_Socks: 16 = 01
14:39:07 Close_Socks: 16 = 00
14:39:07 UDP send to 255.255.255.255, Port: 2362, M1XEP
14:39:09 Open_Socks: 01 = 57
14:39:09 TCP Secure connection accepted
14:39:09 TCP Secure Received client hello
14:39:09 TCP Secure Begin SSL negotiation
14:39:09 TCP Secure SSL negotiation failed, code: -3
14:39:12 Open_Socks: 16 = 01
14:39:12 Close_Socks: 16 = 00
14:39:12 UDP send to 255.255.255.255, Port: 2362, M1XEP
14:39:13 TCP SessionRead received: 10027F0000A5100373D4
14:39:13 ProcessTCP RP msg: 10027F0000A5100373D4
14:39:13 RpComms for control
14:39:13 From M1: 10027F0000A5100373D4
14:39:16 TCP SendUnkPkt 16XK15391472203251100068

looks like i’m having issues with SSL but despite turning it off on the XEP it still tries to create an ssl connection

not sure if anyone else has seen that or if it’s just me.

i upgraded the firmware on the XEP today to see if that would fix the problem but that doesn’t seem to have done so.

my network is completely flat and the XEP has a static IP set via a DHCP server.

[Brad Weeks]

Within the M1XEP Setup under the TCP/IP Setting Tab make sure to check Enable Non-Secure Port 2101.  Home Assistant should be setup to communicate on the Non-secure Port 2101. In the 7TS Installer Setting, View Saved Profiles:

• IP Address is the M1XEP
• M1 User Code is a valid User Code programmed in the M1. Make sure Access, Duress and Temporary Code are not checked for this User Code
• Local Network Connection via “M1XEP”
• Port 2101
• Un-Check Use Secure Connection
• Un-Check Username/Password Required
• Check Connect Automatically on Startup
• Save and Connect

[Kristopher Farley]

Brad,
Thanks for the info.
This worked successfully.

i was able to get my home assistant instance back online as well as the touchpad – i’m still wondering what caused this sudden drop / change in the first place but as long as it’s working, i’m happy with it!

Cheers!

[Author]

Posts