search

haywirecoder / homebridge-envisalink-ademco

Homebridge plug-in for Envisalink Ademco module
MIT License
16 stars 6 forks source link

No TPI session established. #25

Closed HerbM3 closed 2 years ago

HerbM3 commented 2 years ago

I had to do a complete Ubuntu 18 reinstall. Now the plugin no longer seems to work.

EnvisaLink: Error: connect ETIMEDOUT 192.168.x.xxx:4025 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '192.168.x.xxx', port: 4025 }

haywirecoder commented 2 years ago

Hi

This is a low level network error from Nodejs when plug-in is trying to connect to EVL.

  1. Confirm that no other devices are connected to EVL, only one device can be connected to the module.
  2. Confirm that TPI is enable on EVL
  3. On the same device that you're running Homebridge, I would try to telnet into port 4025 to see if you are able to connect and/or do trace to see why a TCP handshake not completing.
HerbM3 commented 2 years ago

Here is the result of telnet: Trying 192.168.xx.xxx Connected to 192.168.xx.xxx. Escape character is '^]'. Login: uTimed Out! Connection closed by foreign host.

HerbM3 commented 2 years ago

I also am running old firmware - Version: 01.04.176A. I cannot find the update ling on the EVL4 local page, not on the Eyezon page. Obviously not your problem, but it might be causing and issue.

haywirecoder commented 2 years ago

Hmm... Telnet is indicating you can connect to EVL module and you are getting prompted for login, assuming this is being done on the terminal Homebridge server.

  1. Confirm your configuration for the plug-in looks something like this: "name": "Envisalink-Ademco", "host": "192.168.X.Y", "port": 4025, "deviceType": "15P", "password": "user", "pin": "XXXX", "changePartition": false, "openZoneTimeout": 30, "heartbeatInterval": 30, "commandTimeOut": 10, "autoReconnect": true, "sessionWatcher": true, "chimeToggle": true, "maintenanceMode": false

The password should always be "user", unless it was changed on EVL4 module. You can also just use the UI and press save to assure everything is set correctly.

  1. Additional questions
  1. If this is occurring at start up place Homebridge in debug mode and post resulting output. Note: The debug mode will print out a lot more detail, so you want to review and make sure item such as your PIN is XXXX out.
HerbM3 commented 2 years ago

I found what it was by reading the debug several times... I'm totally embarrassed. User error. I had a "1" in the IP triad octet, instead of the correct two digits. I was myopically focused on the last three digits.

Apologies for the headache. I appreciate the support.

haywirecoder commented 2 years ago

Glad you found the issue :-). Happy alarming...