Comp temp monitor install#

Ensure that temperatures are expressed as integers.Get the headers from the CSV, remove characters that homeassistant won’t like, and rename duplicate headers where two sensors return the same data, like Core 0 Avg Temp C for each CPU.I haven’t found recent evidence of anyone implementing the SDK in a way that would help us here, so this is glaring flaw #1.

The developers have intentionally left this need unfulfilled, as is explained in this thread.įully automated monitoring/reporting is reserved for the HWiNFO SDK, which is a commercial product. If the computer reboots, you’ll have to go in and click this button again. We’ll massage this data before dumping it on the share. General : Set temperature units and polling rate. I reduced the monitored sensors to just what I wanted: core average and max temperatures.

Comp temp monitor install#

On the Windows hosts whose temps we want to monitor, we need to install HWInfo, set it to auto-run, set the sensors we want to log and start logging.įirst, the HWInfo config. You’d obviously need to enter your username or in valid users Then untarred into ~/.homeassistant/config.Ĭreate a share for the Windows hosts to write their sensor logs. I just tarred the whole config directory, copied it out of the container, built anew withĭocker run –v /home/cooldude/.homeassistant/config:/config etc etc etc

If you’re running a container, and you didn’t bind the /config directory to the host filesystem when you first built it, you’ll need to rebuild.

A Windows host running Powershell version 5+.

A share exposing a directory readable by HA to the rest of the network.

I resorted to something messy, probably error prone, and definitely not memory efficient. None of the WMI classes seemed to be available to me, and I was getting frustrated.