Both my ESPHome LocalBytes PM Plugs have become unresponsive

ESPHome
1

I updated the latest ESPHome Builder (2024.12.4) this morning and I noticed that both my LocalBytes PM Plugs were not updated.

Both of these ESPHome plugs were originally Tasmota devices that I have updated to ESPHome and they have been running without issue for several (4-6?) months. I also have 2 Tasmota LocalBytes PM plugs and they reporting as expected this morning.

Now they may have become unresponsive in the last 1-2 months and I hadn’t noticed so it’s not likely to be the latest ESPHome update. Both devices have been powered on continuously for months but these have not been actively used to control or monitor anything for about 2-3 months. Having said that one has been ON and a coffee machine connected, the other OFF and nothing connected.

I disconnected one them from my network and the AP pops up and I can connect and change the WiFi settings but not upload new firmware. So ESPHome is running on the device.

I then removed the same device from HA and it’s rediscovered by HA when reconnected to my network, but it has no entities and the firmware reported in HA is Firmware: 1.2.0 (ESPHome 2024.12.2).

Any ideas of what I can try to rescue these devices, if indeed they are rescuable?

Chris

2

Logs?

3

I’m embarrassed to say that I have no logs from when I discovered this as I thought it was just a senior moment, hangs head in shame…

Today I returned to this after a few days with both devices unplugged and removed from my network. After connecting back to my network, each device is discovered by HA when they reconnect I’m asked for an encryption key BUT when I enter (my standard key) both devices now give me this error when I try and ADD
Can't connect to ESP. Please make sure your YAML file contains an 'api:' line..
However after power cycling one device now connects to HA/ESPhome and I have this message in the HA logs

Logger: homeassistant.components.update
Source: helpers/entity_platform.py:366
integration: Update (documentation, issues)
First occurred: 14:38:11 (1 occurrences)
Last logged: 14:38:11

Error while setting up esphome platform for update
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/usr/src/homeassistant/homeassistant/components/esphome/update.py", line 64, in async_setup_entry
    assert entry_data.device_info is not None
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError

No errors appear in the ESPHome logs from the adoption. In ESPHome the now added device has no entities and ESPHome reports it as

Device info
plug-pm
by localbytes
Firmware: 1.2.0 (ESPHome 2024.12.2)

So the device updated recently and has the latest version of firmware from LocalBytes.

Am I right in assuming these are bricked?

4

So it was my error, I’ve managed to mess the ESPHome configuration on BOTH devices. To make matters worse when I tried to revert back to Tasmota to give me a clean start, I managed to flash one device with a corrupted/wrong bin file. The other one is now Tasmota’d and I will ESPhome it later once I’ve stopped shouting at myself.

Note to self: READ VERY CAREFULLY ALL CHANGES BEFORE INSTALLING, THEN READ AGAIN!