![]() In a 3-hr gaming session, I measured some case temps with a thermal probe. It won't be much different even after you increase fan speeds. The TG warning is because GPUs heatpipes and some of the fins are close to it. Only if its hot to touch, like actually burming, it would be issue. Please just get thermometer and check the actual temps with that. PSU - Thermaltake Smart DPS G 700W 80+ Bronze Motherboard - MSI B450M MORTAR TITANIUM Micro ATXĬase fans - 3x Be Quiet Shadow Wings 2 120mm I don't mind paying a bit if that's what the good applications require. Extra bonus points if it's possible to cast realtime data to a phone or tablet so I can see temps and RPM in real time. What Windows applications will do a good job of recording ambient temp, CPU temp, GPU temp, and all case or cooler fan RPM? Bonus points if they include fan RPM controls so I can try and work out hysteresis problems without having to reboot and mess with BIOS. Before I start thinking about other problems and solutions, I want to gather good baseline data. I've already set the case fans to be at 100% RPM when the CPU temp is over 45° C. My whole case is really warm to the touch, which tells me it's not doing a very good job of moving fresh air in to replace hot air coming off the CPU and GPU coolers. If the config passes validation, restart HA.I put together a new system recently and I think my air cooling needs improvement. $headersRaw = Get-Content $logFile | Select-Object -First 1 ![]() Clean unfriendly characters and whitespace. $values = value headers here as they appear in the CSV #Set trap to unmount PSDrive if breaking error is encountered $outFile = "HALogging:\config\filesensors\deathknell.txt" $logFile = "$env:ProgramData\Logs\HWInfo\sensors.CSV" New-PSDrive -Name HALogging -PSProvider FileSystem -Credential $credential -Root $sharePath -ErrorAction Stop $credential = Import-Clixml -Path "$PSScriptRoot\Cred_HALogging.xml" Use the names that appear in the CSV.Ĭreate a schedule task to run Powershell on startup with -WindowStyle Hidden -File C:\Scripts\LogTemps.ps1. ![]() Plug your values into $sharePath ( '\\\'), $logFile (the log coming from HWInfo) and $outFile (the file to be read by homeassistant).Īdd the attributes you want to extract to $values. If not, you’ll want to remove -Credential $credential. If your share is secured, you’ll want to create your own $credential object to import. If you’re getting value_json.whatever is not defined in your HA log, you probably have some junk data on your final line. A file sensor only reads the last line of a file, so all our values need to be there. Construct a JSON object of our desired parameters and write it out to a single-line text file at the directory homeassistant is configured to check (HALogging:\config\filesensors).Mount our homeassistant share as a PSDrive.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. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |