SiteAssemble
-
Posts
11 -
Joined
-
Last visited
SiteAssemble's Achievements
Noob (1/14)
2
Reputation
-
AutoFan works perfectly for me, but it took some work to get it to work just right. Truth is that each system is unique so you need to be patient and keep trying, but accept the fact that there's always a possibility that you will not be able to control every fan header. I have two headers that seem to be tied together when I try to use AutoFan to control them, so I just let the BIOS settings control those. Lastly, I'm using all Noctua PWMs which work better for my setup than the stock fans. I have no unassigned devices so can't speak to that.
-
Do this... go to Settings > System Temp - check the 'Array fan speed' selector. If all of the fans aren't showing in that select list, then it'll mess up the fan list in the dashboard. The way to fix this (at least in my case) is to make sure all fans are spinning (you can do this by disabling all autofan PWM controllers, or during the few seconds all the fans are spinning when you make a settings change in autofan), then refresh the System Temp page and toggle off all the fans listed (they should all be listed while they're all spinning). It's a bit of a quirk, but I found that if you made changes to the Array Fan Speed list when any fans weren't spinning, it would modify the fan list in the dashboard. PM me if this doesn't work.
-
Oh I see what you mean. Yeah, it's probably looping through the array of devices, the first index being zero. Glad you got it working.
-
So look at the attached image. This is what it looks like without the javascript. What you're doing is replacing the text marked "FAN 0" (or whatever yours is called) with the new label. So... $( ".fan_view td:contains('FAN 0')" ).text("DRIVES (exhaust)"); ... means you're looking for 'FAN 0' and replacing it with the text 'DRIVES (exhaust)' Make sense? You have to match YOUR old labels, not mine, since they may be different. If you still need help, PM me so we don't take up more space in this thread.
-
Well I guess it's time for us to learn to make Unraid plugins so we can make this one more to our liking.
-
See my update above. Forgot you have to enable the custom.css
-
Is Theme Engine enabled? Settings > Theme Engine > Enable Theme Engine (YES) EDIT: Also, forgot you need to enable 'Advanced View' under 'Theme Settings' - then set 'enable custom.css' to Yes
-
Anyhow, if you decide to try it out, install Theme Engine, then edit this file (create if not already created): /boot/config/plugins/theme.engine/custom.css </style> <script type="text/javascript"> document.addEventListener("DOMContentLoaded", function() { $( ".fan_view td:contains('FAN 0')" ).text("DRIVES (exhaust)"); $( ".fan_view td:contains('FAN 1')" ).text("DRIVES (intake)"); $( ".fan_view td:contains('FAN 2')" ).text("CPU"); $( ".fan_view td:contains('FAN 3')" ).text("CASE (rear)"); $( ".fan_view td:contains('FAN 4')" ).text("NVMe / PCIe"); }); </script> <style> Of course, you'll have to modify your fan names. Easiest way to do that is to go to the dashboard, and while the fans are all spinning, stop them one at a time and note which go to zero. Then that fan number gets replaced with whatever text you want. And yeah, I know this is super hacky putting it into the CSS file, but since this is just inserted into the <head> I figured why not. Maybe Theme Engine will allow for custom js down the road.
-
I actually disabled the fan display in the footer, but my guess is it's probably controllable in a similar way. Yes, Theme Engine is in the apps. It's really meant to modify the GUI styles, but I use the custom.css option to insert the javascript and to add some responsive CSS so that the GUI is somewhat usable on mobile. I'm still playing around with it, and honestly I'm brand new to Unraid so I've not yet had a chance to see if the changes persist through updates. I agree that requests here are probably mostly unseen considering it's for a number of plugins, but maybe we'll get lucky.
-
It's a bit of a kludge, but I renamed those on the dashboard using the Theme Engine plugin with some javascript. document.addEventListener("DOMContentLoaded", function() { $( ".fan_view td:contains('FAN 0')" ).text("DRIVES (exhaust)"); $( ".fan_view td:contains('FAN 1')" ).text("DRIVES (intake)"); $( ".fan_view td:contains('FAN 2')" ).text("CPU"); $( ".fan_view td:contains('FAN 3')" ).text("CASE (rear)"); $( ".fan_view td:contains('FAN 4')" ).text("NVMe / PCIe"); }); Yeah, would be cool if those were nameable in the plugin itself, though.
-
Loving System AutoFan, but have one small issue when rebooting. I've tried searching to see if this has been answered, so apologies if it has. When I reboot the server, the drives typically get different assignments. Example: Drive1 in the array may have been '/dev/sdd' then after a reboot it's '/dev/sde' - unfortunately since AutoFan uses these assignments in the exclude list, that exclude list will inevitably be changed after a reboot and cause the list to be wrong. Case in point... I have 4 fans mapped to exclude all but the array drives, but after a reboot there's at least one excluded drive that swaps its drive assignment with an array drive. The last time I rebooted, the exclusion list swapped the cache drive with Disk1, which caused the fans to stop even while Disk1 was still spun up. At first I thought maybe it would be possible to keep drive assignments the same after a boot, but apparently it's not possible - - and then I wondered if it were possible if the exclude list in AutoFan used either the drive name or serial number so that it was less affected by a reboot. If I've made any sense, feedback would be appreciated. Is there something I'm not doing right, or is this just the way it is? Thanks!
