1 hour ago, konmeu said:

Hey there!

Great Plugin for unraid - I love using it! Especially the "identify"-feature is absolutely great!

Only a little thing that bugs me is the minimum interval time of 1 minute. Would it be possible to allow it to cycle every 30 seconds or so?
Thank you very much!

Thanks! Glad you like the Identify feature 😊 For now I’m keeping a 60-second minimum because HDD temps change slowly, and shorter loops can cause fan hunting and extra SMART polls with little benefit. If you need faster reaction, enabling the CPU sensor or slightly raising the per-fan minimum speed usually helps.

Once 7.2 is officially out and I’ve finished adapting to the new responsive UI, I can revisit a shorter interval.

Out of curiosity, what’s your use case where 1 minute feels too slow?

Finally got a chance to try it out, works great!

One thing I noticed is that with Dynamix Autofan the fan speed indicator on the little bar on the bottom of the screen would read: Fan RPM (%). As soon as I deleted the autofan plugin the (%) went away, and it just shows the RPM. Small nitpick, but it was nice knowing what percent the fan was running at. At this point I can't remember if that little indicator is default unraid behavior or from some other plugin I have installed.

1 hour ago, mattalat said:

Finally got a chance to try it out, works great!

One thing I noticed is that with Dynamix Autofan the fan speed indicator on the little bar on the bottom of the screen would read: Fan RPM (%). As soon as I deleted the autofan plugin the (%) went away, and it just shows the RPM. Small nitpick, but it was nice knowing what percent the fan was running at. At this point I can't remember if that little indicator is default unraid behavior or from some other plugin I have installed.

Glad it works!

Regarding the footer: the % indicator isn’t from FanCtrl Plus or Dynamix AutoFan. It comes from Dynamix System Temp when you select “Array fan speed”. If i remember correctly, AutoFan itself doesn’t add a % there—only RPM.

I do plan to add a small footer widget for FanCtrl Plus, but I’ll revisit that after 7.2’s new responsive UI is officially released and I finish the adaptation.

9 hours ago, CkChong said:

Glad it works!

Regarding the footer: the % indicator isn’t from FanCtrl Plus or Dynamix AutoFan. It comes from Dynamix System Temp when you select “Array fan speed”. If i remember correctly, AutoFan itself doesn’t add a % there—only RPM.

I do plan to add a small footer widget for FanCtrl Plus, but I’ll revisit that after 7.2’s new responsive UI is officially released and I finish the adaptation.

Oh interesting - yes I have Dynamix System Temp installed, not sure why the % went away when I deleted autofan. Anyways it's not a big deal, much happier with this plugin. Being able to disable syslog for the fan changes is fantastic.

On 8/21/2025 at 2:01 PM, CkChong said:

Thanks! Glad you like the Identify feature 😊 For now I’m keeping a 60-second minimum because HDD temps change slowly, and shorter loops can cause fan hunting and extra SMART polls with little benefit. If you need faster reaction, enabling the CPU sensor or slightly raising the per-fan minimum speed usually helps.

Once 7.2 is officially out and I’ve finished adapting to the new responsive UI, I can revisit a shorter interval.

Out of curiosity, what’s your use case where 1 minute feels too slow?

Thanks for your answer and even more for considering revisiting the interval time!

I manage all fans in my case with your plugin since the BIOS Fan Control sucks. When I import my photos to immich and using face recognition on them, my cpu gets very hot very fast and I think it would be nice if the fans could ramp up a little sooner.

But I totally understand that there's a problem with the polling of SMART Values.

Thank you!

On 8/22/2025 at 12:51 AM, CkChong said:

Glad it works!

Regarding the footer: the % indicator isn’t from FanCtrl Plus or Dynamix AutoFan. It comes from Dynamix System Temp when you select “Array fan speed”. If i remember correctly, AutoFan itself doesn’t add a % there—only RPM.

I do plan to add a small footer widget for FanCtrl Plus, but I’ll revisit that after 7.2’s new responsive UI is officially released and I finish the adaptation.

I'd been having problems with the Autofan plugin for some time, and I went hacking at the script a while back to make NVME drives work. If I remember correctly, the "System Temp" plugin calls on the AutoFan plugin to get the % value. In the AutoFan script there's a function that calculates "CURRENT_PERCENT_SPEED" and gets fed back. For me the % always showed "0" anyway after hacking at the script to make it work on my system.

Either way, I can do without the % showing since this plugin just works great right out of the box. Plus the "Identify" with the ability to make quick labels to identify PWM controllers is also invaluable! Thank you for your work on this!

Has anyone managed to get this working with a Gigabyte motherboard? I have the Z690 AERO G DDR4 mobo which includes "Smart Fan 6" in the BIOS and no matter what setting I choose, I can't get the fans to be controlled from this plug-in or the Dynamix one.

There's no option to actually disable this automatic fan control in the BIOS so I assume I'm SOL.

1 hour ago, Turge said:

Has anyone managed to get this working with a Gigabyte motherboard? I have the Z690 AERO G DDR4 mobo which includes "Smart Fan 6" in the BIOS and no matter what setting I choose, I can't get the fans to be controlled from this plug-in or the Dynamix one.

There's no option to actually disable this automatic fan control in the BIOS so I assume I'm SOL.

From a quick look, your Z690 AERO G DDR4 is likely using an ITE (it87 family) Super I/O.

Try the IT87 driver from Community Apps and then:

1. Install “ITE IT87 Driver” from Community Apps, then reboot the server (a full reboot, not just stopping/starting the array).

2. BIOS: set each fan header to PWM/Manual, disable Fan Stop and any auto/Smart Fan curve (or set Full Speed) so the BIOS/EC doesn’t fight the OS.

3. Test in Unraid: open FanCtrl Plus → check if PWM controllers show up in the dropdown; set a temporary higher minimum speed to confirm the RPM actually changes.

If no PWM controllers show up or RPM doesn’t respond, that board’s EC may be locking fan control and neither plugin can override it. Hope it helps!

20 hours ago, CkChong said:

From a quick look, your Z690 AERO G DDR4 is likely using an ITE (it87 family) Super I/O.

Try the IT87 driver from Community Apps and then:

1. Install “ITE IT87 Driver” from Community Apps, then reboot the server (a full reboot, not just stopping/starting the array).

2. BIOS: set each fan header to PWM/Manual, disable Fan Stop and any auto/Smart Fan curve (or set Full Speed) so the BIOS/EC doesn’t fight the OS.

3. Test in Unraid: open FanCtrl Plus → check if PWM controllers show up in the dropdown; set a temporary higher minimum speed to confirm the RPM actually changes.

If no PWM controllers show up or RPM doesn’t respond, that board’s EC may be locking fan control and neither plugin can override it. Hope it helps!

I just tried this and was able to identify the fans (the fans turned off and back on) but it seems like trying to control the speed of the fans appears to disable them and only a reboot will re-enable the fans.

My case does have 8 fans along with another fan used to cool the HBA.

There are 3 fans at the front and 3 in the middle of the case (all Noctua NF-S12B PWM fans). The HBA fan is a Noctua NF-A9x14 PWM fan.

Each series of 3 fans are connected to a fan splitter and are reporting the RPMs properly but I'm not sure if this is related to my issue, although I have tried just a single fan with the same problem.

10 hours ago, Turge said:

I just tried this and was able to identify the fans (the fans turned off and back on) but it seems like trying to control the speed of the fans appears to disable them and only a reboot will re-enable the fans.

My case does have 8 fans along with another fan used to cool the HBA.

There are 3 fans at the front and 3 in the middle of the case (all Noctua NF-S12B PWM fans). The HBA fan is a Noctua NF-A9x14 PWM fan.

Each series of 3 fans are connected to a fan splitter and are reporting the RPMs properly but I'm not sure if this is related to my issue, although I have tried just a single fan with the same problem.

You’re likely still fighting the BIOS/EC.

In BIOS, set each fan header to PWM in Smart Fan (not Auto or DC), then try again in FanCtrl Plus.

I haven’t used that specific Gigabyte board, so names may differ — just look for PWM mode and avoid Auto/DC.

Thanks for this great plugin!
Small feature request:

I had problems using the identify feature. The plugin worked, but it was really hard to tell which fan was being affected as they didn't stop completely, only slowed down (I assume the bios/hw kicked in with a minimum safe level).

Could you add an option to set the fan to max speed for identification instead of attempting to stop it?

On 8/31/2025 at 7:31 AM, Jorgen said:

Thanks for this great plugin!
Small feature request:

I had problems using the identify feature. The plugin worked, but it was really hard to tell which fan was being affected as they didn't stop completely, only slowed down (I assume the bios/hw kicked in with a minimum safe level).

Could you add an option to set the fan to max speed for identification instead of attempting to stop it?

Thanks for the suggestion! Give me a bit of time to think about the best way to do this — I’ll most likely revisit it after the 7.2 responsive UI work.

Strange behaviour here on my server. The fan control worked quite well and I am using it just for monitoring two array fans together with hdd temps. They spin up when the drives are active and switch off when they are asleep.

But: Now one fan is on full speed even if the hdds are still sleeping... where can I have a look into? The log does not point me to any direction unfortunately.

BTW: I am on a Gigabyte Mainboard and they tend to be tricky to setup with fan control... but as it worked flawless for over 10 days I am wondering what causes that issue.

11 minutes ago, buscopina said:

Strange behaviour here on my server. The fan control worked quite well and I am using it just for monitoring two array fans together with hdd temps. They spin up when the drives are active and switch off when they are asleep.

But: Now one fan is on full speed even if the hdds are still sleeping... where can I have a look into? The log does not point me to any direction unfortunately.

BTW: I am on a Gigabyte Mainboard and they tend to be tricky to setup with fan control... but as it worked flawless for over 10 days I am wondering what causes that issue.

Could you try adjusting the BIOS fan settings?

Set the used headers to PWM/Manual (not Auto/DC) and disable Fan Stop/auto curve, then test again in FanCtrl Plus. This might sort it out.

1 hour ago, CkChong said:

Could you try adjusting the BIOS fan settings?

Set the used headers to PWM/Manual (not Auto/DC) and disable Fan Stop/auto curve, then test again in FanCtrl Plus. This might sort it out.

I did reboot the server and jumped into the BIOS. Unfortunately all settings have already been set properly: PWM / Manual plus Fan Stop disabled... so this was not the issue... Any further ideas?

After the reboot the plugin works again as intended but I do suppose that the error will occor after some time again.

16 hours ago, buscopina said:

I did reboot the server and jumped into the BIOS. Unfortunately all settings have already been set properly: PWM / Manual plus Fan Stop disabled... so this was not the issue... Any further ideas?

After the reboot the plugin works again as intended but I do suppose that the error will occor after some time again.

Since it’s back to normal after the reboot, let’s keep an eye on it.

If it happens again, please note which header it is and what FanCtrl Plus shows at that moment (PWM %, RPM, disk state). As a simple mitigation, try a small non-zero minimum (e.g. 30–40%) on that header, and make sure no other controller (e.g. Dynamix AutoFan) is active.

4 hours ago, CkChong said:

Since it’s back to normal after the reboot, let’s keep an eye on it.

If it happens again, please note which header it is and what FanCtrl Plus shows at that moment (PWM %, RPM, disk state). As a simple mitigation, try a small non-zero minimum (e.g. 30–40%) on that header, and make sure no other controller (e.g. Dynamix AutoFan) is active.

I will do.

When the issue occured it was the rear fan that went up to 1280rpm with no reason as the hdds were asleep and therefor the fans should be switchef off - but I could not manage to get it switched off at all even if I turned off and on the plugin.

At this very moment the fans are both setup with a minimum of 20% when the hdds are spinning/in use.

@CkChong is anyway we can use temperature from file in future maybe?

I mean I got working method to get 9207-8i temperature that can be posted to file, but can't use storcli tool or sensors for it.

I tried this out but it doesn’t see any of my PWM fans at all, I am using an Asus W680 Ace IPMI motherboard. I have made sure to manually set all fans in PWM mode but they don’t show up at all.

They do show up via the ipmi plugin but I can’t control them with your plugin or even the dynamix plugin. I attached my bios settings so you can see they are set to PWM mode.

4 hours ago, Android_18 said:

I tried this out but it doesn’t see any of my PWM fans at all, I am using an Asus W680 Ace IPMI motherboard. I have made sure to manually set all fans in PWM mode but they don’t show up at all.

They do show up via the ipmi plugin but I can’t control them with your plugin or even the dynamix plugin. I attached my bios settings so you can see they are set to PWM mode.

I haven’t used an IPMI board myself, but from what I’ve seen these boards usually don’t expose normal hwmon pwm* controllers to the OS. The BMC/IPMI tends to own the fan headers instead, which is why FanCtrl Plus (or Dynamix) can’t see them. It might be worth checking with other IPMI users on how they adjust fans under Unraid — most likely through the IPMI plugin or the board’s BMC interface rather than standard hwmon.

.

Edited September 10, 2025Sep 10 by CkChong

Hello,
i'm on a Gigabyte Z790 AORUS ELITE AX , Version 1.1...
It seems that i'm not able to control the fans...

In the BIOS i have set everything like you already written...

i have the Dynamix Temp plugin installed, the IT87 Plugin and all set up...

Can someone help here?!
I have made an issue on github...

GitHub

Gigabyte Z790 AORUS ELITE AX , Version 1.1 no Fan Control...

Hello i have a Gigabyte Z790 AORUS ELITE AX , Version 1.1 i have set in the Bios the settings like you described in the issue #34 The SYS_FAN Mode has just the options "slope" or "stairs" I'm using...

On 9/5/2025 at 5:23 PM, CkChong said:

Since it’s back to normal after the reboot, let’s keep an eye on it.

If it happens again, please note which header it is and what FanCtrl Plus shows at that moment (PWM %, RPM, disk state). As a simple mitigation, try a small non-zero minimum (e.g. 30–40%) on that header, and make sure no other controller (e.g. Dynamix AutoFan) is active.

Okay, same error. HDDs are spun down, so no temperature is shown and the two fans should remain off. Unfortunately the front fan is spinning at full speed at 1280rpms. Tried to disable the plugin and the rear fan is spinning up (as intended) but after activating the plugin only the rear fan goes down again whereas the front fan is just spinning at 1280rpms.

That said: It seems that the connection from the plugin to the front fan is somehow interrupted. Unfortunately a simple deactivate acticate procedure does not get the fan to work normal and neither does a manual operation (run now) changes anything. Only a reboot does the job.

But as my server idles when I am away it's a bit of a nuisance if this happens regularly - in this particular case after 9 days - and the log does not show anything unfortunately. Last spinup of disks has been on the 9th, full speed of one array fan on the 12th not following the plugin's parameters.

1 hour ago, buscopina said:

Okay, same error. HDDs are spun down, so no temperature is shown and the two fans should remain off. Unfortunately the front fan is spinning at full speed at 1280rpms. Tried to disable the plugin and the rear fan is spinning up (as intended) but after activating the plugin only the rear fan goes down again whereas the front fan is just spinning at 1280rpms.

That said: It seems that the connection from the plugin to the front fan is somehow interrupted. Unfortunately a simple deactivate acticate procedure does not get the fan to work normal and neither does a manual operation (run now) changes anything. Only a reboot does the job.

But as my server idles when I am away it's a bit of a nuisance if this happens regularly - in this particular case after 9 days - and the log does not show anything unfortunately. Last spinup of disks has been on the 9th, full speed of one array fan on the 12th not following the plugin's parameters.

When the fan gets stuck at full speed, can you try Identify — does it still pause the fan?

Also, if you click Run Now, do you see a “Manual Run” entry in syslog a few seconds later? And does the log show correct temps and the right PWM output?

If the log looks normal but the fan still ignores control (and only a full reboot fixes it), that usually points to the BIOS/EC taking control back, or sometimes a hardware quirk.

Maybe try moving that fan to a different CHA_FAN header, re-Identify, and select the correct PWM again in Fan Configuration. That way you can check if it’s always the same fan misbehaving, or if it’s always the same header/socket that loses control.

1 minute ago, CkChong said:

When the fan gets stuck at full speed, can you try Identify — does it still pause the fan?

Also, if you click Run Now, do you see a “Manual Run” entry in syslog a few seconds later? And does the log show correct temps and the right PWM output?

If the log looks normal but the fan still ignores control (and only a full reboot fixes it), that usually points to the BIOS/EC taking control back, or sometimes a hardware quirk.

Maybe try moving that fan to a different CHA_FAN header, re-Identify, and select the correct PWM again in Fan Configuration. That way you can check if it’s always the same fan misbehaving, or if it’s always the same header/socket that loses control.

Identify does not work, this fan just ignores the command(s).
When doing the "Run Now" the log shows the Manual Run entry with the correct RPMs in the log but does not trigger the adjustment based on hdd temperature.

I probably will open the NAS and try a different header as you suggested and work it over.

To my understanding it's just a bit weird that only one fan "misbehaves" and this also only after a certain period of time (couple of days) where it worked flawlessly.

59 minutes ago, buscopina said:

Identify does not work, this fan just ignores the command(s).
When doing the "Run Now" the log shows the Manual Run entry with the correct RPMs in the log but does not trigger the adjustment based on hdd temperature.

I probably will open the NAS and try a different header as you suggested and work it over.

To my understanding it's just a bit weird that only one fan "misbehaves" and this also only after a certain period of time (couple of days) where it worked flawlessly.

Yeah, sometimes hardware just acts weird and it’s hard to pin down.

If possible, try swapping the two fans between headers — if the issue follows the fan, then it’s the fan itself.

If the same header misbehaves again, it’s more likely the motherboard/BIOS side taking control back.