Latest ESPhome update seems to have broke my LocalDeck

beeldubz

I tried to do an OTA update for my LocalDeck, it went through the whole thing and said complete. When I went back to esphome it said my localdeck was unavailable. I tried power cycling and still unavailable. So I downloaded my esphome code and took apart the localdeck to do an update through web.esphome.io. I held the boot button until it connected and it said the configuration was loaded. I power cycled the localdeck and plugged it in and still unavailable. Has anyone come across this or know of a fix?

AAllport

Hi beeldubz,

Please let us know which version of ESPHome & LocalDeck Configurator you are using?
We’ve tested the configuration on ESPHome 2024.07 and LocalDeck v0.4, and everything seems to be working.

Thanks!

beeldubz

I’m using ESPhome 2024.7.2 and configurator v0.4

beeldubz

Also, only the top left 4 led light up when I press on them.

jms

This is the same behaviour as I’m experiencing. I’ve reflashed ESPHome several times, and whilst the device is on the network and I can ping it, the API and Web UI don’t appear to be responding.

I’ve since recovered the device by:

Reflashing ESPHome using “web.esphome.io”, remembering to set the WiFi password here
Device should show up in HASS “ESPHome” awaiting adoption
Adopt device and re-install latest ESPHome firmware
Open Localdeck Configurator, select new ESPHome configuration
Save Localdeck Configurator, go back to ESPHome
Clear Build Files using three-dot menu on ESPHome item
Compile and install Localdeck config

jms

Running ESPHome 2024.7.3, Configurator v0.4.

AAllport

Admittedly, this is a real head-scratcher as to why this is happening.

I’ll start by noting that log spam is a known quirk that was a workaround for a bug in ESPHome.
This has been fixed (expecting it to hit in 2024.8).
That said, the log-spam should have no impact on functionality.

If you’re experiencing disconnects, it would suggest you’re in an RF-unkind environment.
As such, you can find the instructions to disable the WiFi power-save which should result in a more stable connection here LocalDeck Disconnects - Sending keepalive failed!

jms

AAllport Thanks. It seems to stabilise after a few hours and has been working after several reboots.

I will disable WiFi power save and get back to you. I’m not sure about RF-unkind, I’m running Unifi AP7 and AP6+. It could be trying to roam, so I’ll also try pinning the Local Deck to a single AP are get back to you.

AAllport

Unifi sounds familiar with an issue we’ve seen on the plug.
I vaguely recall there’s a feature where the APs can kick off low signal devices to force them to roam, I am wondering if this could be the culprit here

jms

AAllport I don’t actually use that feature, but I will check my logs to see if there are any AP roaming events going on