The system monitor runs inside the container so it doesn’t know what is going on outside of it unless there is an external service that provides the data.
2 Likes
In that case, the new System Metrics feature provides a more accurate picture of what is actually being reported:
- Core CPU usage
- Supervisor CPU usage
where System Monitor’s processor_use is Core CPU usage and has never represented the total CPU usage when part of Home Assistant OS, Supervised, or Container.
That would indeed explain why tom_I’s system was reporting high temperatures but processor_use was very low; something beyond the homeassistant container’s boundaries was monopolizing the CPU.
@tom_l
If your system overheats again, let us know what Supervisor CPU usage indicates. Even at idle, it already consumes more CPU time on my RPI3 than Core.
1 Like
Great release! I love the improvements to the Synology component. Thanks to the whole team and double extra special thanks to @shenxn for the Synology work!!
1 Like
Install very smooth. I tried the new Raspberry PI power supply integration and it would not install. Clicked on install and it closes without installing. No errors in log. Should I open an issue on github? Error showed up today: Error occurred loading configuration flow for integration rpi_power: No module named 'custom_components.rpi_power.config_flow.
I had a custom component that I forgot I installed. Removed and it installed correctly.
2 Likes
Hate to be “that guy” but it worked for me. Installed on RPI3.
Anyone wanting to pull these metrics into the frontend, I created some examples here.
6 Likes
The integration of the Raspberry PI power supply works well for me. Created the entity and monitors the resource
I have the same, it doesn’t install.
update:
Got it solved. The custom component was still installed on the device. After deleting and reboot it worked.
I have a pi 4. Looks like it works for some and not for others. Tried again this morning and get Error occurred loading configuration flow for integration rpi_power: No module named 'custom_components.rpi_power.config_flow.
I had a custom component that I forgot I installed. Removed and it installed correctly.
Seeing this as well. My stream in lovelace is freezing as well. Rolled back to 0.115.6 and all good again.
are you guys using the synology dsm component for cameras?
I’m using the amcrest ad110 doorbell camera
rtsp is stable outside of HA
stream:
amcrest:
- host: 192.168.86.209
name: Doorbell Camera
username: !secret amcrest_username
password: !secret amcrest_pw
stream_source: rtsp
binary_sensors:
- motion_detected
- onlineYes, I’m using it. And it works ok
Yay Hyperion is fixed!!!
thanks!
Edit: awesome performance metrics, if I could make 1 feature request/suggestion to add to it: Uptime
then I can remove all the manual stats I made in one of the panels.
It does not work for me too… Did anyone find anything on this?
Is that because we had custom component for rpi_power before? I tried removing it too, but did not work for me. Entity name is same as that of custom component.
Has anyone else noticed issues with zha lights reporting status correctly? I’m still looking, but it looks like my hue lights that are using the zha intergration, are not reporting on/off after a restart. They show as off. Then if I do turn them off/on they show on, but dont report brightness level. Unless I manually change the level.
Just updated from 0.115.6
Has anyone else ran into this issue. Not in a rush to roll back if this is a simple fix.
Most likely CTRL-F5 your browser.
2 Likes
I had a custom component also.
If it were only that simple 