EyezOn Forum

Got it working, had to change the password to numeric-only. The only thing that changed was the firmware.

How long is your password? I changed mine to numeric only, rebooted through the web interface and still no dice.
[EDIT]
Changed my password to 4 digits (was 10 digits) and now it works. Looks like the firmware has changed something with the password configuration. Before the firmware change I used a 10 character password (numbers and letters)

Same! Was previously 10 alpha characters, now 4 digits.

@GrandWizard: Any plans to restore the previous password behaviour? The current restriction to 4 numeric digits is less secure than the previous longer alphanumeric version.

In addition, it would great to have some assurance that testing the password behaviour will be added to the automated tests in the future to prevent something like this happening again. I have a lot of integrations in my Home Assistant setup that hinge on knowing the alarm status. A lot of weird things started happening when the new firmware broke the integrations.

As expressed before, there are no issues with the new firmware. It has passed all tests and I personally have it working with my HA setup.

If there is a change it is with Home Assistant. Maybe bring it up on their forum to see if something has changed.

Chiming in, I had Home Assistant working fine until last week, I also have been upgraded to 1.05.208 and Home Assistant stop working. If I change the password to 4 numbers it works properly, with a longer/alpha password the integration doesn't work. The home assistant debug shows that the following

Password is 10 characters, the integration doesn't work
Queueing command '005' data: '**********' ; calling_task=queue_login_response
TX > b'005**********CB'
Command '005' failed due to timeout waiting for response from EVL

Password numeric 4 numbers, all works properly
Queueing command '005' data: '****' ; calling_task=queue_login_response
TX > b'005****63'
RX < 5000052A
DSC ack recieved. (note the misspelling !)

Thus clearly there is a problem when the password is longer than 4 character and alpha.
I also note that there is a difference in the TX code, the end characters are CB vs 63.

I am not a software expert thus I can't guess if the problem is in the integration or on the envisalink side. Cross posting this to the HA envisalink_new github, as we clearly want to have better security with passwords longer than 4 numbers

This is from 1.05.208. The local password I am using is "user00001".

Connected to 192.168.0.83
>5053CD
<005user0000145
>5000052A
>5051CB
>51110F8

GrandWizard wrote: ↑Fri Nov 17, 2023 6:38 pm We're not sure what the issue is but it seems a reboot fixes all issues with the "socket closed" error.

It is possible the firmware update left the TPI socket in an unknown state but this would be something in RAM so a reboot (software/hardware) will fix it.

We have found an issue with the login sequence for the TPI that can cause the TPI to lockup, or become unresponsive, and requires a reboot to fix. This only affects the DSC build. It has been fixed in 1.005.209 and we will patch all affected users.

My TPI password no longer works with 01.05.209.

looks like my EVL4 (DSC) got 01.05.209 pushed at 2023-11-30 14:19 UTC. (Today at 9:19 EST)

I've been using a password that is 8 chars alphanumeric. I can still log into the EVL4 HTTP interface directly.

EDIT: - FYI -- Unlike others that started having TPI login problems with .208 -- I didn't have a problem until today with .209. My last login was after .208 was pushed on 2023-11-16 and didn't get disconnected until now when it looks like the EVL4 got rebooted for .209.

EDIT 2: - I can confirm I'm getting back a 505-0 ("5050CA") from the EVL4. (That comes after the 500-005). I rebooted the EVL4 via the HTTP interface, given the comment above with the same results.

I haven't tried changing to a 4 digit numeric password. I'm assuming that shouldn't be required. The TPI 1.08 doc says

"The Envisalink 3 only supports 6 ASCII digits for a password but the Envisalink 4 supports 10."

I'm assuming digits in the doc is incorrect, the default password is actually alphanumeric.

FYI There is a .210 EVL4 DSC update that fixed the problem with longer passwords like mine (8 characters).

It was pushed out today (2023-11-30) at some point after .209, but I didn't get it until I contacted EyezOn support for a manual update.