2021 Round PoE coordinator stops and unresponsive.

[tube0013]

@tube0013 I ran a similar setup to onedr0p with the same coordinator (he recommended it and I got it).

It looks like mine started failing this week. I tried to update ESPHome and the firmware, it runs for a little bit but then locks up completely.

None of the actions are functioning, you can still push an OTA Update and it comes back to life for a bit.

Originally posted by @kashalls in #138 (comment)

[tube0013]

@kashalls

I moved this to a new issue as the other one was 10 months old.

Can you confirm all function in the web front end are non operational, besides the OTA? Are you a ble to control any if the ESPHome device is in HA?

Does power cycling bring it back or only the OTA flash?

Can you try flashing over the microUSB port on the olimex by opening the case and lifting the pcb partially out?

I'll also post an alternate firmware based on esp-idf platform to try that will need to be flashed via USB next time I'm at a computer.

[kashalls]

Can you confirm all function in the web front end are non operational, besides the OTA? Are you a ble to control any if the ESPHome device is in HA?

I first recognized this issue after z2m started crash looping. Sometimes it was the ping after 6000ms issue and sometimes it just couldn't do it's socket.

I tried the energy scan and it failed as it couldn't connect to the socket.

Rebooting the coordinator after stopping z2m brought it up. Thing to note was that the panel showed an active connection even though nothing was connected.

Does power cycling bring it back or only the OTA flash?

Both bring it up. I just did the OTA flash for the 3rd time today and it's up for now.

Can you try flashing over the microUSB port on the olimex by opening the case and lifting the pcb partially out?

I'll also post an alternate firmware based on esp-idf platform to try that will need to be flashed via USB next time I'm at a computer.

I can, please provide the firmware and some information on how I can flash it this way.

[tube0013]

I've added flashing instructions and an esp-idf bin of the esp32/ESPHome FW here:
https://github.com/tube0013/tube_gateways/tree/main/models/retired/tubeszb-cc2652-poe/firmware/esphome

Note the web interface with esp-idf loses the ability to do OTA updates, if you adopt the device to esphome you can do OTA from the ESPHome dashboard.

Let me know how this goes.

[kashalls]

I've added flashing instructions and an esp-idf bin of the esp32/ESPHome FW here: https://github.com/tube0013/tube_gateways/tree/main/models/retired/tubeszb-cc2652-poe/firmware/esphome

Note the web interface with esp-idf loses the ability to do OTA updates, if you adopt the device to esphome you can do OTA from the ESPHome dashboard.

Let me know how this goes.

I haven't gotten around to doing this, but I ended up figuring out I still had another device connecting to the serial at the same time the updates were occuring. Once I offline'd that device, I don't have any more zigbee disconnects. It sounds like Z2M was fighting this device and locked up the coordinator to the point where it needed to be reset.

[WarmCatUK]

I haven't gotten around to doing this, but I ended up figuring out I still had another device connecting to the serial at the same time the updates were occuring. Once I offline'd that device, I don't have any more zigbee disconnects. It sounds like Z2M was fighting this device and locked up the coordinator to the point where it needed to be reset.

How did you figure this out? I’ve been having the same problem lately, and thought it was due to a HA update, After years of stability. Perhaps I also have a naughty device.