After upgrading to supervisor 2026.03.3, my Phoscon Deconz integration stopped working on my Raspberry Pi 4. I tried rebooting the system, but no change. I noticed in All Hardware that the Conbee II dongle was not recognized, so I switched to another usb-port and reboote the whole system again: it stil did not show up. I tested the dongle on my Windows pc and it works fine. Then I noticed my other usb-device (DSMR smart meter) wasn't found either. Before the upgrade they both worked fine...
What ca I do? I understood you cannot fall back to a previous version of the Supervisor (I've tried restoring serval backups an the Supervisor version stays the same 🙁 )
#No USB ports after upgrading to supervisor 2026.03.3
ember flax
ebon condor
Have you tried to shut it down gracefully and un-/repowering the Pi afterwards (powercycling and not just rebooting)?
ember flax
Yes, I have (2 times)
Choose Shut down, after stopping: removed the power cord (even replaced with another) and plugged in after some 20-30 secs
ebon condor
You can try to downgrade the supervisor with ha supervisor update --version 2026.03.2
ebon condor
Either using one of the Terminal apps via the UI or configuring those to open an SSH server.
ember flax
Advanced SSH & Web Terminal ok?
ebon condor
Yes. Or keyboard and HDMI to the Pi and use supervisor update --version 2026.03.2 in the shell.
ebon condor
Have you added the --version 2026.03.2 part?
ebon condor
If that doesn't help, I would download a backup and the encryption key, reinstall HAOS (maybe on a new microSD - those can easily fail) and restore the backup.
ember flax
Still doesn't work 🙁
Ok, restore backup then to another SD 😭
Thnx Jorg, I was afraid that answer would come
ebon condor
Well... it could be worse. A hardware failure of the Pi's USB chip would also be possible.
You could check that by flashing one microSD with Raspberry Pi OS and see if the USB ports are working.
ember flax
Shht, don't jinx it 😉
ember flax
SUCCESS!!
My Zigbee network is reachable again 🙂
But it appears not to be th Supervisor version (still 2026.03.03), but Home Assistant Operating System (17.2)
My working HA is on 17.1
strange sonnet
For anyone else hitting this issue, the os GitHub repository starts to have open issues reporting the same problem.
The current workaround is to downgrade home assistant OS with:
ha os update --version 17.1
See https://github.com/home-assistant/operating-system/issues/4627 for details
willow owl
FWIW I'm following up in the linked issue, if you have developer SSH enabled or if you can hook up a display and keyboard, I'll be interested in output of some commands. Most likely some older hardware revisions (with old firmware?) are affected, but the exact combination needs to be figured out.
craggy bronze
If enabling developer SSH scares you here's a trivial way to get the same access via the Advanced SSH Addon: https://gist.github.com/Impact123/e9a4a07b184eb393d2ff762e3b1b0a05#through-advanced-ssh-addon
weak raft
I got this issue on a x86 VM, so the fix of updating the rpi bootloader won't work for me. I downgraded to 17.1 for now and it's working, but would like to figure this out to not be stuck going forward.
weak raft
Seems the fix is upgrading the VM from using pc-q35-6.2 to pc-q35-10.1
craggy bronze
I just always use the latest machine version for linux guests. HAOS doesn't need Q35, by the way.