How to fix device state after crash during OTA update?

[janpieper]

I had a short power outage while I was updating some devices (OTA). Now those devices are still in "updating" state although no update is running.

The state.json contains the following for one of these devices:

{
  // ...
  "0xa4c138dc0f11229a": {
      "state": "ON",
      "indicator_mode": "on/off",
      "child_lock": "UNLOCK",
      "power_outage_memory": "off",
      "power": 109,
      "current": 0.76,
      "voltage": 231,
      "energy": 216.49,
      "update": {
          "state": "updating"                   // <----- Wrong state
      },
      "update_available": false
  },
  // ...
}

I already tried to edit the file and change the state to available or idle, but after restarting z2m, the state was updating again 🤷‍♂️

I found #12794 which seems to describe the same issue, but there is no fix as the state was magically fixed after some time.

Is there anything else I need to do? Or is there another way to fix the state? I am currently running the following z2m version:

[ptheofan]

I have a similar issue. I was doing OTA of a TuYa socket. At some point zigbee2mqtt crashed (I renamed a different device and crashed due to database error, id already exists). After I restarted zigbee2mqtt the OTA is stuck to almost zero (was 41% before crash) and it will not go away (30mins have already passed).

It would be great if there was some button somewhere to reset the OTA state so we can click to restart it (and take responsibility for it of course)

Regardless, the device works fine.

Update
Clicking the check all button again appears to fix the issue and cleared the OTA state.