As far as I understand the first two use the universal-silabs-flasher and the last one has its own repository. But only forked from the other to be used as addon with Homeassistant if I get that correctly.
It seems the current firmware version pushed on all three options is 7.2.2.0. At least verified on my part with the Web Flasher and the Homeassistant Addon.
However if I head over to the silabs-firmware repository we can clearly see that the current firmware is 7.3.0.0 - actually with a decent amount of bugfixes and improvements. The same goes for 7.2.3.0.
Edit: The old silabs-firmware repository is now EOL. The new place to look for is in the NabuCasa repo here.
I’d probably give it a go as I have some sensors that are acting up a bit at times with the skyconnect. What is the way?
In the Web Flasher it tells you the current firmware afaik, also I think the Addon failed while trying to update telling me that the current version is the most recent one.
As far as I know, you are on the right track with the repository for the various flash versions being at silabs-firmware repository and you have identified the latest Beta versions (for Zigbee). I use the SiLabs Multiprotocol Add-On and have it configured for auto-update, so I don’t pay much attention to this. If you are using ZHA, I don’t know but it may auto-update Skyconnect as well??? If you are using Zigbee2MQTT, you’ll probably have to manually update it.
If you are asking what is the best way to update the flash…Here is a thread that may be of interest:
Well that’s not really promising to try using ssh. At least considering all those seemingly bricked Skyconnects in the thread you linked.
I use it only for ZigBee with ZHA atm. as it seems the hybrid version has its drawbacks. Also, apart from my Google and Nanoleaf devices, I have none using Thread/Matter.
In the long run i was hoping to directly expose some entities to Google over Matter. But thats a bit off topic and still not possible at this moment.
I didn’t know those firmwares on the silabs repository were betas though. Where did you spot that?
Due to all those issues with the SSH way I was hoping to somehow feed the new firmwares into the Homeassistant Addon. Is there a particular reason the addon is using 7.2.2.0. Unless of course these are betas as you mentioned.
As the autouodate won’t update anything besides the plugin itself, you’d need to manually start it after disabling ZHA (or the multiprotocol thingie) before it would flash the stick.
Well that’s certainly interesting considering 7.2.2.0 seems to be a beta firmware as well.
I would have expected the official flashers to use the most recent stable version but here we are.
I might actually open an issue on github on that one.
Today the Homeassistant Silicon Labs Flasher Addon was updated to 0.2.0 which includes the most recent firmware 7.3.1.0 (I didn’t check the web flasher). I took the plunge right away and updated my Skyconnect. After disabling the ZHA integration and starting the plugin everything went seamless according to the addons logs. So far it seems stable - no hickups. According to the firmware logs it seems there were a few sevurity relevant changes along the way so I think the new firmware should probably be generally recommended for the Skyconnect.
Thanks a lot to @agners as it seems he did the necessary commits on github.
Got here while searching for how to update this thing. Reading through these posts, I still don’t know how to do it. What is the official or recommended way to go about updating the firmware please?
I recommend doing it with the homeassistant addon which is the third solution in my initial post. Disable the ZHA integration in devices, then start the addon, check the logs and wait for it to finish.
Provided it finished without errors, stop the addon and reenable ZHA in the devices section. That’s it.
So either it’s been removed, it only exists for you for some reason, or you’ve forgone instructions that maybe you don’t realise other people might need. No offence.
No it’s an official addon in the “normal” addon store as you can check yourself here. Nothing more to add really… maybe enable advanced mode as it says in your screenshot?
While the flasher addon works, it doesn’t actually update. My stick is still on 7.1.1 after letting the addon do its thing and stopping itself automatically afterwards:
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[10:26:33] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[10:26:33] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 115200)
2024-12-02 10:26:34.482 core-silabs-flasher universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version='7.4.4.0', ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.ZIGBEE_NCP: 'zigbee_ncp'>, fw_variant=None, baudrate=115200)
2024-12-02 10:26:34.482 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-02 10:26:36.520 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-12-02 10:26:37.715 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected ApplicationType.EZSP, version '7.4.4.0 build 0' (7.4.4.0.0) at 115200 baudrate (bootloader baudrate None)
2024-12-02 10:26:43.877 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-02 10:26:43.938 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected bootloader version '2.1.1'
2024-12-02 10:26:43.939 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200)
skyconnect_zigbee_ncp_7.4.4.0.gbl
[10:27:16] INFO: universal-silabs-flasher-up script exited with code 0
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
If I read this correctly (which is not a given) it looks like it claims the stick is on 7.4.4, which is not the case if I re-enable the ZHA integration and take a look at the firmware version reported there. It’s still on 7.1.1.
So I now got two conflicting reports on the firmware version. Which one is right?
Hard to tell, from what I can see in your logs it seems the flash was successful. At least “exited with code 0” would implicate such a thing. You could try to flash it again. Ususally if it is already on the most recent firmware it’ll will tell you so and not attempt another flash. Maybe try a reboot of your system as well?
Next step would be to try the webflasher but you’d have to unplug your stick then.
Edit: I checked my logs and they seem to be particularly more verbose than yours. Apart from that they are identical though. These are my settings:
