Open brettinman opened 1 month ago
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Bump to prevent closure of the Issue per the bot.
In case anyone else is having trouble with this, I am hosting a small static site with the same firmware management tool that is temporarily unavailable here: https://zbt1.notaphish.fyi/
I successfully used it to change a new ZBT-1 dongle to the Thread firmware.
The problem
Can someone shed some light on why the firmware update utility was hidden? It happened in a direct commit rather than a PR, so there's no information explaining the change. Is that best practice?
Is this related to the voltage regulator failure in some way?
Context: I needed to upgrade the EZSP protocol version in order to use Zigbee2MQTT (which I think has a required minimum version of 13; the ZBT-1 I received was on 9). This required updating the device firmware. The only user-friendly and well-documented way to do that is the web firmware update tool. I had to edit the html in Chrome Inspect to essentially reverse that commit, and was able to update firmware that way and get z2m working. Not a great user experience.
Alternatively, I would suggest documenting detailed instructions on how to safely update the firmware with command line or other tools.
Link to the page
https://connectzbt1.home-assistant.io/firmware-update/