this post was submitted on 24 May 2026
1 points (100.0% liked)

Home Assistant

275 readers
1 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY...

founded 2 years ago
MODERATORS
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/redd2100 on 2026-05-23 16:33:40+00:00.


I'm running 2026.5.3 as a VM on Proxmox and all is going well. I upgraded to 2026.5.4 and the system appeared to still be functional, but it was consuming high amounts of CPU. I rebooted the HA VM to see if it just needed a fresh start and it came back with the high CPU usage immediately. So I restored the morning backup to get 2026.5.3 back and everything was working great again.

Anyone else have any similar issues with .4? If there's anything specific that someone can recommend I look for, I would be happy to upgrade again today and gather more details on what might be going on.

UPDATE:

Did the upgrade again and again the CPU usage was high. Brought up the console and noticed it was killing processes due to out of memory error. Went into shell and ran top and saw the following:

using 101% CPU - "python3 -m homeassistant --config /config"

using 36% CPU - "python3 -m wyoming_satellite --name assist microphone --uri tcp://0.0.0.0:10700 --mic-command..."

I have no idea why it appears to be stuck here, but I went into the Settings/Apps and stopped the "Assist Microphone" and "openWakeWord" addons, and set them to not start on boot. About 30 seconds later the CPU was fine. Did a fresh restart of HA to make sure it's all clean, but currently the 2026.5.4 appears to have broken my wyoming integration for the moment.

https://preview.redd.it/zbxcl2pqvz2h1.png?width=1273&format=png&auto=webp&s=0f4b7ae559ff0e4d0aca2c5f634118d3fd894a5b

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here