Since 27th of November my HAOS (on RPi4) is running at ~30% cpu use instead of as earlier, around 10%. Unfortunately I just noticed so I can’t recall if I changed something particular on that date…
I have tried disabling addons and integrations, and also booting in safe mode, but the high CPU usage persists. I’ve browsed through the log files but nothing really stands out (to me at least).
I tried following this guide (Instructions to install Py-spy on HAOS) to install and run py-spy, but I run into the similar (unanswered question/problem) as the last poster:
$ ./py-spy top --pid 67
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: PosOverflow }', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/proc-maps-0.2.1/src/linux_maps.rs:81:65
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: receiving on a closed channel
If I just run top (after docker exec -it homeassistant /bin/bash) I get the following:
…which doesn’t really tell me much. Maybe the go2rtc is somewhat fishy? Not sure what it is, but it does not seem to be the source of the CPU usage anyways, that is homeassistant.
I have also tried running ha dns options --fallback=false (as mentioned here: https://www.reddit.com/r/homeassistant/comments/1bklg68/psa_got_consistently_high_cpu_usage_here_is_a_fix/) but that did not help neither.
I’d be really happy if I can somehow avoid needing to reinstall everything I have built… Can anyone point me on how to continue my trouble-shooting?
(Lesson learned: perform regular backups, not just after fresh installation…)
(Some other thing I have noticed but I don’t think is the cause of the problem:
- after booting, my mqtt2zigbee devices are not responsive, until I restart mqtt2zigbee. I have however tried stopping mqtt2zigbee entirely and that did not help
- I am not able to create a full or partial backup (the job fails, I have not dug deeper yet…)
Thanks in advance,
RD
1 post - 1 participant