Does anyone know of a simple one-liner script for command line sensor to show CPU fan RPM (speed)?
My temps are usually at 39-40 but I wonder if that’s because of the regular ambient temperature in the room or because the fan is working hard to keep it that way.
I don’t need any control of the fans, I just want HASS to show and record the history of it, like it does with cpu temperature using this:
- platform: command_line
name: CPU Temperature
command: "cat /sys/class/thermal/thermal_zone0/temp"
unit_of_measurement: "°C"
value_template: '{{ value | multiply(0.001) }}'
The problem is, however, that I run HASS.IO inside docker on Ubuntu, and docker images does not seem to have lm_sensors installed. Gotta figure out how to install it into a docker container.
If you’re on a NUC I’d recommend running Proxmox as host OS and HA OS inside a VM or container. Then you can run Glances on the host and use that to get all info about the host sensors.
Thanks for the reply! I do have Glances running as an HA addon, but I guess that since the HA addons are running in Docker containers, that version of Glances doesn’t have access to such “bare metal” info?
I don’t want to run any kind of VM because of the downtime involved in updating or restarting the host OS, by running HA OS more as an “appliance” on the NUC, I have 100% uptime outside of the monthly updates to HA itself.
It could be, could also be that HA OS itself does not have the required libraries or firmware to access it.
What are you talking about? You don’t have to restart host OS after updating it. Only kernel upgrades require restart, and you generally don’t need to do it unless there’s some known serious security issue in the version you’re running.
My current home Proxmox’s server uptime is 79 days. At my dad’s house it’s at 49 days and I think there was just some power outage back then. I also have a Lenovo ThinkCentre Tiny I use for running some game servers, it’s uptime is 217 days.
So if anything, in my experience, virtualizing your appliances help improve your uptime. Because, say you run a Hass OS in one VM and something like Blue Iris in another. If, for whatever reason, you need to restart your Blue Iris VM - your Hass OS VM remains operational. They are separated.
It is extremely rare for you to have to restart virtualization host OS.
What I meant is that I would want to update the host OS, not just leave it as is indefinitely, so it just adds a layer which I don’t actually need…I realized it wouldnt’t force me to update, I’d just want to
I have another server for various other self-hosted things and prefer keeping the HA box only for it and its addons.
Proxmox actually runs security updates automatically, and it’s trivial to schedule a script on any linux distro with a cron job to run auto updates however often you like.
I get the mindset of keeping the HA box as it’s own appliance, but I don’t share it Missing out on too many conveniences, and the cost of overhead of running it in a VM is so negligible, I was able to run it all on an old “nettop” with 2Gigs of ram
But hey, if you prefer it that way, sure. I just don’t know of any other way to get rpm readings in this case.