According to analytics we had more than 1k users participating the RC phase (probably quite a bit more, since those are opt-in stats). Unfortunately, I had zero feedback/issues about Bluetooth issues. So either the problem is not that widespread, or the selection of people is just very very unlucky.
Should have, and I hope we will with you on board next time? 
What “core problem” are you referring to?
The big question is, how do we get from /dev to /stable, when nobody tests? 
@agners
Stefan,
Is there a way to open a discord beta channel for the OS similar to the core Beta channel? I believe you will receive much better inputs from the users / testers if you do. I tested each of the RC releases and had no issues with any of them. I did have a restart issue with 10.0. Once any issue is found in the discord, a GitHub issue can then be created.
I think this build is indeed a little bit unlucky.
I have been on the RC and didn’t have any issues. As soon as I updated to the final release my system died because of the mentioned problems.
Yesterday i went back to 9.5 and my HA is back online now.
Did you try updating motionEye to 0.19.0 instead?
What problems are you experience with HAOS 10?
The last 24h quite some problems I see here should be addressed.
The Bluetooth problem is still something I try to get a handle on. So far none of my test installation failed. Exact configuration and hints what might cause issues on your side are welcome (best posted in Bluetooth failing after upgrade to HAOS 10 on Raspberry Pi · Issue #2485 · home-assistant/operating-system · GitHub along with what Bluetooth hardware you are using).
Supervisor monitor completely unavailable, none of the docker containers are working, can’t SSH into my machine or anything. Will restart when I get the chance, but everything just hit the fan.
This all happened after updating a docker container (Z-Wave JS UI)
Everything working properly here in my NUC, only BT like other users is dead.
But checking my supervisor logs I can see the following:
23-04-20 21:22:58 WARNING (SyncWorker_7) [supervisor.store.data] Can’t read /data/addons/core/whisper/config.yaml: Service wyoming not found @ data[‘discovery’][0]. Got ‘wyoming’
What is this?
Thanks!!
It is already at that version
When I downgraded to OS 9.5 all was working fine.
I noticed that motionEye was not responding every time for about 40-45 minutes. Afterward, it was responding, but the cameras were not working. When I tried to add a camera… it went again non-responding for 40-45 minutes. During the non-responding time, the Pi CPU is 100%, and temp increases from 40 to 65-70°C
I am running HA OS on an Pi CM4 with 8Gb ram using the official Raspberry Pi CM4 IO board with an NVMe boot drive. When I updated to 10.0 my system would not boot properly. I could not get to the web interface at all and I could only ping the system briefly when it first booted then it went offline completely. I tried a fresh image of 10.0 and the system would not boot at all. Then did a fresh image of 9.5 and all is working fine again.
Something is definable wrong with this build.
What’s strange is I just tried out the RC’s and none of them have the problems I have experienced on the final release.
the PI has now no functioning bluetooth wihtin HA. However an add on i use, (theengsgateway for bluetooth mqtt transport) is working fine.
I’m running HAOS as a VM inside Proxmox, running on a Dell micro pc with 8GB RAM and an i5-8500T CPU. I noticed, while still running OS9.5, that updating to the latest core 2023.4.5 caused my CPU to spike to 100% and temps to rapidly climb to 60-65 degrees. Before the Core update, I ran a recorder purge and repack which I’ve started doing, as recent Core updates seem to take an age to complete, and running this before each update seems to help a little.
During this state, the frontend became unresponsive. I reverted to my backup from before the Core update and all was well again. I figured it was maybe my recorder database sorting itself out and doing migrations (aroung 700MB size), so I gave the Core update another try and left it running for an hour. The CPU usage eventually came down gradually to around 20% and temps to 55 degrees - still way higher than they should be. Each VM or host reboot would see high usage again for several minutes before settling to these levels again.
Proxmox processes only showed the main CPU usage coming from the KVM process, and no warnings or errors in the HA logs.
I tried disabling integrations and addons, until they were all disabled, and nothing seemed to affect the CPU usage, even after a vm restart.
Then HAOS v10 was released, so I thought I’d see of updating to that had any impact on the issue.
After several reboots, and just letting it run, the CPU has finally come back down to normal levels - idling around 2 or 3%, with the odd spike that lasts a minute or two, however idle temps are still higher than when running the previously Core version, and sit around 48 degrees, possibly due to the seemingly random processor usage spikes, and so it never gets a chance to get any lower. It used to idle around 38 degrees prior to the Core update.
On OS v10 my Bluetooth seems to all be running fine, using an external USB dongle passed through to the VM, running BTHome for several BLE devices. None of my integrations or addons appear to be broken, like some of the above reports, I’m just left with a higher CPU temp, but feel this is the latest core rather than OS.
i initially also had BT running, but it dies after some time. How long is your running on OS10 now?
Guys you are the best ! I’m running HA on a HP T630 Thin Client and after the update the CPU temperatures went from 50-60ish to 30ish 
Well done !
I am running HAOS on a VM in proxmox, with 4G Ram allocated.
Keeping the same version of HA (2023.4.1) the OS upgrade from 9.5 to 10.0 resulted in a ram usage spike from a steady 1G to around 3.5G. Reverting to 9.5 takes it back to 1G.
This is not my normal HA machine, it only has a few integrations and one addon (SSH & Web Terminal).
Here is a graph of the RAM usage when I reverted
@agners This is an experimental install - if you want further experiments, let me know what I can do to help.
Hi,
I had issues when updating from 9.5 to 10.0, my service didn’t restart. I ended up restarting the physical device a few times (was moving it so I could connect an external monitor).
No clue why it started working after about 5 maybe 6 restarts and just letting it sit each time until I knew it was done.
Was running 9.4 on a Pi 4 with external USB SSD. Made a full image from the SSD and a full backup before even considering updating.
Update went smooth. After restart almost nothing worked. Z-Wave and Zigbee dead, EMS-ESP via MQTT dead. What helped was patience - after a while Zigbee came back on it’s own. Z-Wave still dead. So I shut down the Pi, switched off Power (important!), waited a few seconds and switch on again.
After that all was working again - except EMS-ESP via the MQTT integration. Further investigation showed that HA renamed (and doubled) almost all EMS-ESP and Z-Wave entities with ‘_2’, ‘_3’ or ‘_4’. It was a mess. So I removed the integrations, restarted HA and added them again. Had to edit some of the automations to adjust entity names. All was working fine then. So I spent a whole day with this update and fixing all the various ‘problems’ here and there.
The reason I jumped ship from ioBroker to HA was the broken ioBroker updates who almost always broke my system (especially Z-Wave).
But anyway, now my system runs fine and I can continue with my visualizations.
Great update team, went from 9.5 to 10.0 on a bare metal NAS, no issues, and no increase in resources. Thank you!
HA OS 10 update disappeared. Triggering manual update search did not bring it back. Has the rollout been paused?
Thanks
