envisalink_new not authenticating

[rdpeterson-hacs]

I just successfully installed envisalink_new from HACS and installation seems to be OK but it fails to authenticate. I had the legacy version of envisalink installed and it authenticated with no problem. I am using the same parameters for the new installation as I did in the old installation.

[ufodone]

Have you disabled the envisalink integration by commenting out or removing the config from configuration.yaml and then restarting HA? The EVL devices only allow a single connection at a time so if the old integration is still setup that may be the issue.

Are there any errors in your HA logs?

[rdpeterson-hacs]

I removed the envisalink integration and restarted HA. I also tried to power the alarm panel off to clear the interface. Still says unable to authenticate with Envisalink at 192.168.1.151:4025 which was the address that worked for the legacy integration.

[rdpeterson-hacs]

Here is the log for last attempt:
2025-01-11 16:02:31.588 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to validate connection: ClientConnectorError(ConnectionKey(host='192.168.1.151', port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.151', 80)"))
2025-01-11 16:02:31.589 INFO (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Checking panel type for 192.168.1.151
2025-01-11 16:02:31.592 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to validate connection: ClientConnectorError(ConnectionKey(host='192.168.1.151', port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.151', 80)"))
2025-01-11 16:02:34.708 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to connect to 192.168.1.151: OSError(113, "Connect call failed ('192.168.1.151', 4025)")

[ufodone]

It is failing to connect to the EVL with a 113 error ("No route to host") which means there is a network problem between HA and the EVL. Since the stock envisalink was working for you, my first guess would be that you may have a typo in the IP address for the EVL or that the EVL device's IP address has changed recently (which could be possible if it's using DHCP).

[rdpeterson-hacs]

I tried to reinstall the legacy integration and it also would not connect. I am not sure now if it actually connected the first time. I am new to Home Assistant, so I will keep trying to get it to work. Thanks for your help.

[rdpeterson-hacs]

I use the EyezOn mobile apps with my DSC alarm system. Could using these apps interfere with the HA envisalink integration?

[ufodone]

Could using these apps interfere with the HA envisalink integration?

No, that would not cause a problem.

Have you double checked that the IP address you configured in HA matches what your device is currently using? If you don't know what it is currently using, it looks like the EyezOn portal at portal.eyezon.com will display the local IP address of your device under the Status page.

You can also check you have the IP address by trying to connect to the device directly via a web browser (e.g., http://192.168.1.151).

[rdpeterson-hacs]

I verified the IP address through my router and through the Eyezon app and both show 192.168.1.151. When I try to connect directly with a browser I get the login prompt but it will not authenticate. I can ping the device from my router and no issues with the ping. Probably a router issue but I am stumped.

[rdpeterson-hacs]

Solved it, I had to reset the default password on the envisalink. I am very impressed by this integration, works great.
Thanks for your help.