Workaround Script for OTA Update Issues with Z2M

[soif]

Hi @Koenkk

First off, a huge thank you for your incredible work on Zigbee2MQTT! This project is a cornerstone of the home automation community, and your dedication is truly appreciated. 🙌

I’ve recently released a small open-source project, z2m_helpers, which includes a script (z2m_ota.sh) designed to work around the OTA update issues that many Zigbee2MQTT users, particularly those with Ember-based coordinators, encounter (ie: #11138, #24807, #22463, #22873, #25002, #23704, #19916, #10352, ....) .

The script automates retries for failed OTA updates, leveraging the fact that devices retain partial update data, allowing updates to complete without hours of manual intervention or needing to switch coordinators. While it doesn’t fix the underlying issue, it’s a helpful time-saver for users facing OTA crashes or stalls.

I’m sharing this in case it’s useful for the community.
Would you consider adding a link to the script in the Zigbee2MQTT documentation (e.g., in the OTA section) as a temporary workaround for affected users?

[Koenkk]

hi!

Would you consider adding a link to the script in the Zigbee2MQTT documentation (e.g., in the OTA section) as a temporary workaround for affected users?

I think it would be better to integrate a fix directly in Z2M, that will give a much better user experience.

[soif]

For sure, it would definitively be the best thing to do. 👍

I unfortunately doesnt have enought TS skills to code this feature myself, and I cant evaluate if that's an easy task or not. So in the meantime, I shared this solution, that should certainly help some users.

On the otherhand if you wish to temporarely integrate this script in your project, until you cleanly rewrite it in pure TS, fee free to use it, mofify it, the way you want.

Best regards