Skip to content

Enhance firmware update instructions with flasher reference#818

Open
lattice0 wants to merge 1 commit intoNabuCasa:mainfrom
lattice0:patch-1
Open

Enhance firmware update instructions with flasher reference#818
lattice0 wants to merge 1 commit intoNabuCasa:mainfrom
lattice0:patch-1

Conversation

@lattice0
Copy link

Added a reference to NabuCasa's universal-silabs-flasher for advanced users.

I found this by inspecting the web flasher on the toolbox website, by looking into the javascript code. Way too hard to find such information.

Added a reference to NabuCasa's universal-silabs-flasher for advanced users.
@netlify
Copy link

netlify bot commented Jan 18, 2026

Deploy Preview for nabucasa-support-content ready!

Name Link
🔨 Latest commit 03ba22e
🔍 Latest deploy log https://app.netlify.com/projects/nabucasa-support-content/deploys/696c4f895ba7440008267c23
😎 Deploy Preview https://deploy-preview-818--nabucasa-support-content.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Collaborator

@TheJulianJES TheJulianJES left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, most users should be able to update firmware using Home Assistant directly.
Otherwise, the OHF Toolbox is recommended to be used for everyone that needs to install custom firmware. As you've found out, it uses the same underlying universal-silabs-flasher.

There's a separate "Reinstalling firmware on ZBT-2" article abut that, but I think it might make sense to have this article include the following as a related topic:

What was the reason you needed to use the CLI flasher tool in the first place? Did the web-flasher not work for you?


If you want to switch from the Zigbee to the Thread firmware, follow the steps on [Switching from Zigbee to Thread](/hc/en-us/articles/31347057208989).

For more advanced users, you can use NabuCasa's [universal-sibals-flasher](http://github.com/NabuCasa/universal-silabs-flasher)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, there's a double space here:

Suggested change
For more advanced users, you can use NabuCasa's [universal-sibals-flasher](http://github.com/NabuCasa/universal-silabs-flasher)
For more advanced users, you can use NabuCasa's [universal-sibals-flasher](http://github.com/NabuCasa/universal-silabs-flasher)

@lattice0
Copy link
Author

Generally, most users should be able to update firmware using Home Assistant directly. Otherwise, the OHF Toolbox is recommended to be used for everyone that needs to install custom firmware. As you've found out, it uses the same underlying universal-silabs-flasher.

There's a separate "Reinstalling firmware on ZBT-2" article abut that, but I think it might make sense to have this article include the following as a related topic:

What was the reason you needed to use the CLI flasher tool in the first place? Did the web-flasher not work for you?

I wanted to do an offline rewrite of the firmware before plugging into my trusted setup. The website is not easily auditable, any javascript and firmware could be there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants