new evl4 firmware? 1.05.208

[groovejumper]

My HA integration stopped working. I noticed the fw version on my EVL4 is now 1.05.208, by any chance is this a new version released in the last day or two? I don't see it in the firmware change log thread.

Just trying to figure out what broke.

PS: I can still log in to the EVL4 directly, and integration with eyez-on is still fine, monitoring is good. But homeassistant is timing out trying to connect. Haven't touched any of this in over a year (closer to 2).

[DigitalMaestro]

Same issue with my HA integration as of last night

[rct]

The firmware change log thread has nothing in it about 208 for the EVL4.

The last entry is for .204.

[GrandWizard]

Hi, that firmware was just released to Sidekick owners yesterday to improve LTE troubleshooting. I will get the updates from the team and post today.

We tested the TPI on EVL4 1.05.208 on DSC, Honeywell, and SA platforms and they passed the automated tests.

If you are still having issues submit a tech support ticket so we can look at your telemetry. As well, you can try opening a raw socket to port 4025 and see if you get the login prompt(s). Use something like PuTTY with RAW socket mode, not Telnet.

[groovejumper]

I do indeed have a Sidekick.

I tried Putty with Connection type set to Other/Raw (I assume that's how to do it?), to port 4025 on the EVL4's IP, but I immediately get an error popup "Network error: Software caused connection abort". Not having tried to connect to it that way before I'm not sure if there's some other setting that's needed.

[GrandWizard]

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.

[DigitalMaestro]

Tried the reboot. Still have the issue.

[groovejumper]

Same here. I had rebooted earlier, as well, after I opened a support ticket I was told it was rebooted. Still can't connect via raw socket in Putty, or homeassistant.

[groovejumper]

fwiw I've only rebooted through the web interface. Would a cold boot make a difference? Is there a specific method to do this?

[GrandWizard]

Same here. I had rebooted earlier, as well, after I opened a support ticket I was told it was rebooted. Still can't connect via raw socket in Putty, or homeassistant.

Connection Abort is different. That means there is already something attached to the TPI so your connection was aborted. The issue people are reporting is a socket timeout, no response at all.