Firmware update is temporarily unavailable

[brettinman]

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/

[github-actions]

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.

[brettinman]

Bump to prevent closure of the Issue per the bot.

[milas]

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.

EDIT: Updated to include a warning that you should NOT use this with ZBT-1 devices with the voltage regulator issue!

[puddly]

The voltage regulator problem is indeed why the web flasher is currently disabled. We found that a few people broke their ZBT-1s after plugging them into a desktop computer to use the web flasher. It took some time to identify the root cause but for the time being the web flasher will remain disabled.

The good news is that we're going to be adding ZBT-1 firmware updates directly to Home Assistant Core, which will replace the web flasher entirely. This will probably make it into the December release.

You can always update the firmware by using the flasher addon. Or directly use the universal-silabs-flasher tool and the correct firmware for your stick.

[Daasin]

Worth noting that it is back up now, albeit with a confusing warning about how only ZBT-1 sticks made after Oct '24 are supported for flashing.

Sorry to ping you @puddly but I'm just not really sure why this is the case though, because I thought it was said that the newer 'Connect ZBT-1' branded products weren't supposed to have used any different modules to the older models that just had the 'SkyConnect' name on its own, Could Nabu Casa's HASS Devs elaborate by pushing an explanation/reason of why alongside that warning box?

[milas]

(not affiliated with Home Assistant or Nabu Casa, don't take this as official)

I believe this is covered in the blog post:

Though Home Assistant SkyConnect is identical to the ZBT-1 under the hood, it is not affected. The design is not what’s at fault, but instead, a defective voltage regulator that was used in this specific production run that is causing the issue.

https://www.home-assistant.io/blog/2024/10/02/connect-zbt1-issue-and-replacement/

[milas]

Also, I think it's safe to close this issue now that the official docs have the updater available again! ❤️