Hi there, I keep getting an update available for Home Assistant Yellow Radio firmware that popped up a few weeks ago.
According to the update popup it is for EmberZNet Zigbee
Installed version 6.10.3.0
Latest version 7.4.4.1
with a point to the release notes Release v2025.04.04-1 · NabuCasa/silabs-firmware-builder · GitHub
However it is the first time ever I get this update and it seems quite a big version jump.
I am currently running on * Core2025.4.2
- Supervisor2025.04.0
- Operating System15.2
- Frontend20250411.0
The update keeps failing with this error message
Failed to perform the action update/install. Failed to flash firmware
Does anyone has encountered similar issues and a possible fix?
I seem to be in a similar situation. I have the HA yellow as well and see the same update option. I tried to apply the update yesterday and it started, but must have failed or something. The update still shows as available, but when I try to update, I get the same error message.
Something must have gone really wrong with the update because all my automatons have disappeared, and the zigbee radio doesn’t seem to work. I did a factory reset and restored from a backup, but ended up in the same state.
Does your zigbee radio currently work?
I managed to fix my HA yellow by reflashing the radio firmware. Thanks to Jorg on discord for these directions:
- Deactivate ZHA on the integrations Page
- Install the Silicon Labs Flasher add-on
- Go to the add-on’s settings, set it to /dev/ttyAMA1 and save the changes
- Start the add-on and observe the progress on the logs page (it should finish with code 0)
- Reboot once the add on is done
- Reactivate ZHA on the integrations page
This got my radio working again. The radio firmware was still out of date, but I applied the pending update without any problems.
One problem I encountered was all the zigbee devices I had set up lost their firendly names. I’m not sure if this was caused by the initial firmware update failure, the successful flash, the reset/restore I did, or some other step. I just had to re-name all my devices, which gave me the opportunity to do it in a much more consistent manner.
Hopefully this helps you @diegofox82 or someone else in a similar situation.