I need to flash my new skyconnect from the recall but it doesnt show up in my HA to flash, so I need to do it manually but cannot
#Is there a reason the skyconnect/ZBT-1 web flasher is down?
spark leaf
fallen dawn
hollow thicket
The OP said that this is the replacement, though
fallen dawn
Right, but this is the reason the web flasher is disabled
hollow thicket
But if there are now good ones out in the wild and NC is actively replacing defective ones, why would the web flasher still be unavailable?
inner yew
Because it is causing users to plug bad ones into a computer and breaking. We’re preparing firmware updates to be added to Home Assistant in the January release (just missed cut off)
Not breaking is still better than breaking and replacing
inner yew
I need to flash my new skyconnect from the recall but it doesnt show up in my HA...
Why do you need to flash it ?
spark leaf
Because the way I forward the USB to a VM does not allow me to flash it with the add-on
Worked previously with my defective unit, after flashing to thread with the web UI
civic scarab
Why do you need to flash it ?
I came from virtual box and it's not possible to setup with usb-passthrough HAOS crashes. Hyper-V doesn't support usb passthrough, skimming google it seemed to be a common problem with the recommendation of using the web-flasher but since it's down from my end I gave up and got a green.
inner yew
That’s a good point. Let me take it back to the team
odd mural
Just off the back off this, I'm trying to use mine with Zigbee2MQTT and it tells me that zh:ezsp: 'ezsp' driver is deprecated and will only remain to provide support for older firmware (pre 7.4.x). Migration to 'ember' is recommended. I presumed flashing it would give me the new ember adaptor?
random veldt
Hopping in here because I wanted to switch mine to thread mode but I'm not running HAOS so I couldn't use this page (running home assistant container and exposing devices as needed)
marsh aurora
Hopping in here because I wanted to switch mine to thread mode but I'm not runni...
You need to run Home Assistant OS to use Thread. Container is not possible
random veldt
You need to run Home Assistant OS to use Thread. Container is not possible
Sorry, not trying to hijack the thread, but is this just because the addon is not (pre-)built for container? I have experience digging into the existing addons and migrating them to standalone CRI already and was already aware I may need to build out my own open thread router container.
marsh aurora
Sorry, not trying to hijack the thread, but is this just because the addon is no...
Well, that is one thing but more important is host-OS level requirements. You need certain (kernel and networkmanager) patches on the host. If you use a super recent (e.g. debian) distro with a recent kernel and make sure all patches are applied you will be able to have success with Thread (if you also configure ipv6 correctly) but reality is that many people run docker contains on stuff like unraid or other NAS os-es which lack all these patches.
Its the most important reason that we do not officially support running matter in HA other than with HAOS. We cant guarantee all requirements are present on the host OS for Matter (over Thread), its a minefield basically.
But yeah, I'm 100% sure the community would love it if you would step up and try to make it work
random veldt
Gotcha. Good to know. I'm happy to do terrible things lol
Just need a working radio and can't flash it 😭 (I use ubuntu as my basis and am... plenty capable to do delightful OS level patching)
Thanks a ton for the info @marsh aurora, gave me some much needed context (I probably would have floundered a little bit until I realized heh)
finite root
as a reminder, the web flasher is not the only option, it was just the most dummyproof for a time
https://github.com/NabuCasa/universal-silabs-flasher
https://github.com/NabuCasa/silabs-firmware-builder/releases
