I came across your plugin today and immediately downloaded it! I have been hoping to incorporate this functionality native in Unraid for a while and I'm really happy you developed this application and it's continued development. Up till now I have been using liquidctl with the LaaC docker to control my fans with a Corsair Commander Pro, but this lets me also track drive temps for cooling. This is great especially when running array intensive tasks like array parity checks which gives me much more piece of mind.

One thing I miss is the ability to also use the temperature sensors I have scattered around my case to add additional temperature dependency for my fan curves. Specifically, my temperature sensors from my ASUS motherboard and my Corsair Commander Pro. I have included the output from the sensors command on my system to illustrate the outputs I'm getting on these drivers, and also to highlight how the ASUS reporting driver differs from the k10 temp driver I'm currently using to supply FanCrtl Plus with data.

Thanks again and I will continue to track this project!

root@SERVER:~# sensors
...
corsaircpro-hid-3-2
Adapter: HID adapter
in0:          12.03 V  
in1:           5.05 V  
in2:           3.45 V  
fan1 4pin:   1240 RPM
fan2 4pin:   1302 RPM
fan3 4pin:   1110 RPM
fan4 4pin:    939 RPM
fan5 4pin:   1253 RPM
fan6 4pin:   1316 RPM
temp1:        +28.4°C  
temp2:        +21.2°C  
temp3:        +22.5°C  
temp4:        +24.8°C  

k10temp-pci-00c3
Adapter: PCI adapter
CPU Temp:     +61.1°C  
MB Temp:      +54.0°C  
Tccd2:        +31.5°C  

asusec-isa-0000
Adapter: ISA adapter
CPU Core:      1.44 V  
Chipset:     3199 RPM
Chipset:      +64.0°C  
CPU:          +51.0°C  
Motherboard:  +30.0°C  
T_Sensor:     +35.0°C  
CPU:          36.00 A  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +40.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +40.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +44.9°C  (low  = -273.1°C, high = +65261.8°C)

The plugin works great, thank you for developing it.

However, it's generating the following (benign?) boot log errors related to /tmp/inline.sh:

/tmp/inline.sh: line 13: name: command not found

/tmp/inline.sh: line 14: name: command not found

rm: cannot remove '/var/tmp/': Is a directory

/tmp/inline.sh: line 14: /bin: Is a directory

I confirmed that those errors are only generated when the plugin is installed.

Thank you.

I have what may be 2 related issues. First, I have two PWM controllers that I cannot identify the fans attached. I have 5 fans in the case, and one on the CPU. When I run the "identify fan " function for PWM 2 and PWM 8, nothing happens. Second issue, I cannot identify GPU fans. I have 2 GPU's installed (GTX 1660 Super and Intel ARC). The plugin does not seem to find those fans. I am guessing that the two PWM that I cannot identify are the GPU fans, but they do not respond to the "Identify Fan" test.

On 10/5/2025 at 12:55 AM, BL76 said:

The plugin works great, thank you for developing it.

However, it's generating the following (benign?) boot log errors related to /tmp/inline.sh:

/tmp/inline.sh: line 13: name: command not found

/tmp/inline.sh: line 14: name: command not found

rm: cannot remove '/var/tmp/': Is a directory

/tmp/inline.sh: line 14: /bin: Is a directory

I confirmed that those errors are only generated when the plugin is installed.

Thank you.

Thanks for the feedback. I found a typo in the .plg. You can ignore this error for now—it doesn’t affect usage. I’ll release an update soon (today or in the next few days) with the fix.

10 hours ago, crusemm said:

I have what may be 2 related issues. First, I have two PWM controllers that I cannot identify the fans attached. I have 5 fans in the case, and one on the CPU. When I run the "identify fan " function for PWM 2 and PWM 8, nothing happens. Second issue, I cannot identify GPU fans. I have 2 GPU's installed (GTX 1660 Super and Intel ARC). The plugin does not seem to find those fans. I am guessing that the two PWM that I cannot identify are the GPU fans, but they do not respond to the "Identify Fan" test.

Hi — FanCtrl Plus doesn’t read or control GPU fans; it only works with the motherboard PWM headers (CPU_FAN / CHA_FAN).

For PWM2 and PWM7: if Identify shows no response, they’re most likely unused headers. Your board exposes 8 PWM channels and you’ve connected 6 (one CPU fan + five case fans), so that matches. If nothing is connected to PWM2/7, it’s fine to leave them unassigned.

@CkChong Thank you for making this robust plugin!

Motherboard: Gigabyte Technology Co., Ltd. Z690 GAMING X DDR4

I'm in the process of trying to get this up and running, but I'm not able to identify any of my fans using the identify command (they don't respond to any of the commands).

Using your Github command to identify hardware monitoring devices:

echo "=== hwmon devices ==="
grep -H . /sys/class/hwmon/hwmon*/name

echo ""
echo "=== k10temp sensors ==="
kdir=$(dirname "$(grep -l k10temp /sys/class/hwmon/hwmon*/name 2>/dev/null)")
if [ -n "$kdir" ]; then
  ls "$kdir"/temp*_label "$kdir"/temp*_input 2>/dev/null
  echo ""
  echo "---- labels and values ----"
  paste -d' ' <(cat "$kdir"/temp*_label 2>/dev/null) <(cat "$kdir"/temp*_input 2>/dev/null)
else
  echo "k10temp not found under /sys/class/hwmon"
fi

OUTPUT:

/sys/class/hwmon/hwmon0/name:gigabyte_wmi

/sys/class/hwmon/hwmon1/name:coretemp

/sys/class/hwmon/hwmon2/name:nvme

/sys/class/hwmon/hwmon3/name:acpitz

/sys/class/hwmon/hwmon4/name:it8689

I did install ITE IT87 Driver by ich777 and I'm still not having any luck with detecting and identify my fans with your plugin.
Is there something I need to change or have set in the motherboard BIOS?

8 hours ago, xDmOx said:

@CkChong Thank you for making this robust plugin!

Motherboard: Gigabyte Technology Co., Ltd. Z690 GAMING X DDR4

I'm in the process of trying to get this up and running, but I'm not able to identify any of my fans using the identify command (they don't respond to any of the commands).

Using your Github command to identify hardware monitoring devices:

echo "=== hwmon devices ==="
grep -H . /sys/class/hwmon/hwmon*/name

echo ""echo "=== k10temp sensors ==="
kdir=$(dirname "$(grep -l k10temp /sys/class/hwmon/hwmon*/name 2>/dev/null)")
if [ -n "$kdir" ]; thenls "$kdir"/temp*_label "$kdir"/temp*_input 2>/dev/null
  echo ""echo "---- labels and values ----"paste -d' ' <(cat "$kdir"/temp*_label 2>/dev/null) <(cat "$kdir"/temp*_input 2>/dev/null)
elseecho "k10temp not found under /sys/class/hwmon"fi

OUTPUT:

/sys/class/hwmon/hwmon0/name:gigabyte_wmi

/sys/class/hwmon/hwmon1/name:coretemp

/sys/class/hwmon/hwmon2/name:nvme

/sys/class/hwmon/hwmon3/name:acpitz

/sys/class/hwmon/hwmon4/name:it8689

I did install ITE IT87 Driver by ich777 and I'm still not having any luck with detecting and identify my fans with your plugin.
Is there something I need to change or have set in the motherboard BIOS?

Hi,

First of all, that script you ran is actually for AMD (k10temp) systems.

Your motherboard looks like Intel, so it’s normal that it didn’t show anything under k10temp.

Let’s check a few things step-by-step:

1. Did you install the System Temp plugin and click Detect and Load Driver?

2. In your BIOS, are the fan headers set to PWM / Manual, not Smart or Auto mode?

3. Just to confirm — in FanCtrl Plus, you can see PWM controllers in the dropdown list, but the Identify button doesn’t make the fans react, right? (or are the PWM options completely missing?)

4. If System Temp is loaded correctly and BIOS is already in PWM/manual mode, please share the outputs of the following safe diagnostic commands (these won’t change fan speeds):

echo "=== hwmon devices ==="
grep -H . /sys/class/hwmon/hwmon*/name
echo ""
echo "=== Available PWM controllers (safe check) ==="
for d in /sys/class/hwmon/hwmon*; do
name=$(cat "$d/name" 2>/dev/null)
echo "-- $d ($name) --"
ls "$d"/pwm* 2>/dev/null
done

That will help confirm which hwmon chip exposes the PWM interfaces (usually it86xx or nct6xxx for Gigabyte boards).

Once we know which one actually has PWM entries, we can test Identify safely from there.

Edited October 7, 2025Oct 7 by CkChong

On 10/5/2025 at 12:55 AM, BL76 said:

However, it's generating the following (benign?) boot log errors related to /tmp/inline.sh:

Hi @BL76 , new version is out! It should fix the issue you reported — let me know if anything else comes up. Thanks again for the feedback!

15 hours ago, CkChong said:

Hi @BL76 , new version is out! It should fix the issue you reported — let me know if anything else comes up. Thanks again for the feedback!

@CkChong I had to reboot today after doing some maintenance and that fixed it. Thank you!

Another request -- would it be possible to offer more fine-grained "Interval" options (less than 1 minute - on the order of seconds)?

I've been allowing the BIOS to control my CPU and exhaust fans, but would like to allow this plugin to do it instead.

However, CPU temps can change abruptly (depending on load) and need quick response in terms of adjusting fan speed(s).

Allowing an interval as low as 1 second would be ideal, as long as it wouldn't introduce additional burden / load on the system from the higher rate of temperature polling, and as long as it doesn't break the existing architecture of the code.

What are your thoughts?

Thanks.

Thanks for getting back to me! You are correct with my Intel board - I knew I should have looked at that better. Good Catch!

1.) I did install the System Temp plugin - Detect and Load Driver does work


2.) BIOS has fan headers set to PWM (with the exception of the CPU Fan - That's set to Auto)

3.) Correct - The PWM Controllers load up, but the Identify function does not appear to work - I've tried all 6 controllers and all 3 identification types with no success.

4.) Your requested Output:

=== hwmon devices ===

/sys/class/hwmon/hwmon0/name:gigabyte_wmi

/sys/class/hwmon/hwmon1/name:coretemp

/sys/class/hwmon/hwmon2/name:nvme

/sys/class/hwmon/hwmon3/name:acpitz

/sys/class/hwmon/hwmon4/name:it8689

=== Available PWM controllers (safe check) ===

-- /sys/class/hwmon/hwmon0 (gigabyte_wmi) --

-- /sys/class/hwmon/hwmon1 (coretemp) --

-- /sys/class/hwmon/hwmon2 (nvme) --

-- /sys/class/hwmon/hwmon3 (acpitz) --

-- /sys/class/hwmon/hwmon4 (it8689) --

/sys/class/hwmon/hwmon4/pwm1 /sys/class/hwmon/hwmon4/pwm3_freq

/sys/class/hwmon/hwmon4/pwm1_auto_channels_temp /sys/class/hwmon/hwmon4/pwm4

/sys/class/hwmon/hwmon4/pwm1_auto_point1_temp /sys/class/hwmon/hwmon4/pwm4_auto_channels_temp

/sys/class/hwmon/hwmon4/pwm1_auto_point1_temp_hyst /sys/class/hwmon/hwmon4/pwm4_auto_point1_temp

/sys/class/hwmon/hwmon4/pwm1_auto_point2_temp /sys/class/hwmon/hwmon4/pwm4_auto_point1_temp_hyst

/sys/class/hwmon/hwmon4/pwm1_auto_point3_temp /sys/class/hwmon/hwmon4/pwm4_auto_point2_temp

/sys/class/hwmon/hwmon4/pwm1_auto_slope /sys/class/hwmon/hwmon4/pwm4_auto_point3_temp

/sys/class/hwmon/hwmon4/pwm1_auto_start /sys/class/hwmon/hwmon4/pwm4_auto_slope

/sys/class/hwmon/hwmon4/pwm1_enable /sys/class/hwmon/hwmon4/pwm4_enable

/sys/class/hwmon/hwmon4/pwm1_freq /sys/class/hwmon/hwmon4/pwm4_freq

/sys/class/hwmon/hwmon4/pwm2 /sys/class/hwmon/hwmon4/pwm5

/sys/class/hwmon/hwmon4/pwm2_auto_channels_temp /sys/class/hwmon/hwmon4/pwm5_auto_channels_temp

/sys/class/hwmon/hwmon4/pwm2_auto_point1_temp /sys/class/hwmon/hwmon4/pwm5_auto_point1_temp

/sys/class/hwmon/hwmon4/pwm2_auto_point1_temp_hyst /sys/class/hwmon/hwmon4/pwm5_auto_point1_temp_hyst

/sys/class/hwmon/hwmon4/pwm2_auto_point2_temp /sys/class/hwmon/hwmon4/pwm5_auto_point2_temp

/sys/class/hwmon/hwmon4/pwm2_auto_point3_temp /sys/class/hwmon/hwmon4/pwm5_auto_point3_temp

/sys/class/hwmon/hwmon4/pwm2_auto_slope /sys/class/hwmon/hwmon4/pwm5_auto_slope

/sys/class/hwmon/hwmon4/pwm2_auto_start /sys/class/hwmon/hwmon4/pwm5_enable

/sys/class/hwmon/hwmon4/pwm2_enable /sys/class/hwmon/hwmon4/pwm5_freq

/sys/class/hwmon/hwmon4/pwm2_freq /sys/class/hwmon/hwmon4/pwm6

/sys/class/hwmon/hwmon4/pwm3 /sys/class/hwmon/hwmon4/pwm6_auto_channels_temp

/sys/class/hwmon/hwmon4/pwm3_auto_channels_temp /sys/class/hwmon/hwmon4/pwm6_auto_point1_temp

/sys/class/hwmon/hwmon4/pwm3_auto_point1_temp /sys/class/hwmon/hwmon4/pwm6_auto_point1_temp_hyst

/sys/class/hwmon/hwmon4/pwm3_auto_point1_temp_hyst /sys/class/hwmon/hwmon4/pwm6_auto_point2_temp

/sys/class/hwmon/hwmon4/pwm3_auto_point2_temp /sys/class/hwmon/hwmon4/pwm6_auto_point3_temp

/sys/class/hwmon/hwmon4/pwm3_auto_point3_temp /sys/class/hwmon/hwmon4/pwm6_auto_slope

/sys/class/hwmon/hwmon4/pwm3_auto_slope /sys/class/hwmon/hwmon4/pwm6_enable

/sys/class/hwmon/hwmon4/pwm3_auto_start /sys/class/hwmon/hwmon4/pwm6_freq

/sys/class/hwmon/hwmon4/pwm3_enable

8 hours ago, BL76 said:

Another request -- would it be possible to offer more fine-grained "Interval" options (less than 1 minute - on the order of seconds)?

may as background, cron triggers 1 minute max, so i had the same point with my pwm fan plugin (which will be obsolete once here all features are included, better layout here, more flexible here, just nicer ;) ).

it is surely possible, but yes, it ll call a little more load (but end user wise not really noticeable)

sample notes (also be aware about logging)

last note

always also remind, CPU Fan is always recommended to be controlled in hardware (BIOS), once the OS hangs, your CPU Fan will also hang ;) most likely nothing will happen as CPU's throttle once heated, but its YOUR decision ;)

In my homelab are 3 fans (basically 1x front and 1x back for hdd bay and just 1x back for cpu chamber). I connected these fans with a y cable to my mainboard so i can control the 2 hdd bay fans together. Just see my screenshot, pwm2 is basically the 1x front and 1x back fan of my hdd bay connected together. pwm4 is the back fan for the cpu.

This is basically working.

Right now, my temps are okayish/low, so the fans only run at 10%. But the rpm value is still huge, like 1600 rpm (which seems to be the maximum with my noctua fans). The fans are running and they are pretty loud. I wouldn't expect that while running at 10% pwm. What am i missing? Fans are pwm and in bios every header is in manual mode and pwm mode.

Edit: Just restarted my system and now my fans looks like this, weird

Edit 2: Just for test purpose, i go down to 5% pwm as min value / idle. Now get this 5% also in the web ui but rpm doesn't changed at all, still at ~700 rpm / ~800 rpm

Edited October 19, 2025Oct 19 by JohnDoe777

Hello!

HPE ProLiant ML310e Gen8 Server - Will this plugin work with the specified server?

On 10/6/2025 at 5:11 AM, crusemm said:

I have what may be 2 related issues. First, I have two PWM controllers that I cannot identify the fans attached. I have 5 fans in the case, and one on the CPU. When I run the "identify fan " function for PWM 2 and PWM 8, nothing happens. Second issue, I cannot identify GPU fans. I have 2 GPU's installed (GTX 1660 Super and Intel ARC). The plugin does not seem to find those fans. I am guessing that the two PWM that I cannot identify are the GPU fans, but they do not respond to the "Identify Fan" test.

My motherboard has a similar thing, but it is just that the board was designed with some unused PWM channels. it shows 5 PWM channels (labelled 1,2,4,6,7 just for fun), has 4 physical ports, but only 3 can be fully controlled.

In my case, one of them is labelled CPU_OPT on the board which can have its RPM read independently of the CPU_FAN pin, but its PWM value cant be set separately as far as I can see. The Bios treats both of those as one, but with two RPM readouts.

the other unused PWM channel on my motherboard is simply not there at all, a higher end version of the same motherboard has an extra connector for chassis fans.

Awesome plugin, are you planning to add support for the MB temperature? In my case it more accurately reflects the case temperature.

thank you!

Great plugin! It works awesome when you figure out how to set BIOS to give away control to the system.

I am missing one option though.

It has been discussed here previously to include the option to keep the fans spinning when the drives are spun down ("Fan Speed on Idle" option)

But can we have also the possibility to stop the fans when the temperature is lower than defined range minimum?

Like in the example below, I would like to have an option to stop the fans completely if all drives are cooler than 30°C and kick in with 40% only when this temp is reached...

(right now all my fans connected to SYS_FAN2 header controlled by PWM2 keep spinning even if all the drives are cold and they stop only when all drives are spun down)

I have a strange issue on one of them on reboot it will change to a diffrent pwm controller.

CPU is set and labled to it8686 - pwm1 on reboot it will move to corsairpsu - pwm1 including the label.

The fan also are not auto controlled untill the run buttons are presses.

Any ideas how to fix this?

On 10/2/2025 at 5:34 PM, JesterEE said:

One thing I miss is the ability to also use the temperature sensors I have scattered around my case to add additional temperature dependency for my fan curves. Specifically, my temperature sensors from my ASUS motherboard and my Corsair Commander Pro. I have included the output from the sensors command on my system to illustrate the outputs I'm getting on these drivers, and also to highlight how the ASUS reporting driver differs from the k10 temp driver I'm currently using to supply FanCrtl Plus with data.

Are you talking about sensors you have added to your server? As in external devices?

Can you explain?

The best I've been able to come up with is a Aqara Temp sensor in the case

Hey @CkChong , I just wanted to say thank you for your amazing work! Your plugin is now running perfectly and has everything I was hoping for. Thanks a lot! ❤️

Edited November 6, 2025Nov 6 by RedOrange

3 hours ago, Arbadacarba said:

Are you talking about sensors you have added to your server? As in external devices?

Can you explain?

The best I've been able to come up with is a Aqara Temp sensor in the case

I use the Corsair iCUE Commander Pro for my fan controller. This controller (shown in the image attached) has connectors for 4 temperature sensors that you can route throughout your case. On Linux, the individual temperature readings are easily read by the sensors command with the fan speeds as shown in my previous post. Currently, FanCrtl Plus doesn't read these temperatures to adjust fan curves, but I'm holding out hope @CkChong sees the value in reading external temperature sensors and adds that functionality in a future release.

Tempting...if only there was a one with just the temp sensors

I've got a Gigabyte UD 790 board that runs Smart Fan 6. I've set PWM mode, full speed, and fan stop disabled. ITE driver installed.

I was able to identify the fans using the plugin, but everything goes to idle when the service is running (cpu fans still spin at minimum). I set 'fan speed at idle' to 40 percent. Curiously, when I now try to change either that value or the low value in 'fan speed range' it just goes back to 40 percent, no chance to apply or save. The upper 'fan speed range' value can be changed. But the fans aren't going to 40 percent at idle, they are just off, and the identify commands no longer function.

I've tried a reset and a cold boot. Fans run full speed during boot as expected, then when Unraid comes alive the fans tied to disk temperature go to 0 and the fans tied to CPU temp are full speed. When I change a setting in the plugin the fans tied to CPU temp then go to idle.

From the logs it appears the commands are being sent:

Nov 7 20:38:27 Goose fanctrlplus: [Intake] Temp=*°C (Idle) → PWM=102 → RPM=0

Nov 7 20:40:31 Goose fanctrlplus: [CPU_Rear] Temp=47°C (CPU) → PWM=132 → RPM=320

Nov 7 20:40:31 Goose fanctrlplus: [CPU_Front] Temp=47°C (CPU) → PWM=132 → RPM=307

Nov 7 20:40:31 Goose fanctrlplus: [Rear_Exhaust] Temp=47°C (CPU) → PWM=132 → RPM=0

Any ideas? TIA

Edited November 8, 2025Nov 8 by jargo

Hi.

So I have installed Fan Control, Dynamix Temp sensor and Nuovoton drivers to be able to see my PWM sensors. My problem is that when identifying my fans they dont turn off/turn up to 100% or pulse. I only have 3 PWM fans setup like this:

The fans are what I expect the to be, I have not been able to verify for sure, but from visually checking it looks like this.

My BIOS settings are like this:

As you can see both chassis fans are set to PWM mode. They are also both set to CPU as "source" which probably is wrong, but I don't know what I should choose here.

Any help is appreciated:

These are the found PWMS, however I think there is only something available fans at 1,3 and 7. Or do I actually need to test all of them to be sure? (Just thought of this now...)

On 11/7/2025 at 11:41 PM, jargo said:

I've got a Gigabyte UD 790 board that runs Smart Fan 6. I've set PWM mode, full speed, and fan stop disabled. ITE driver installed.

I was able to identify the fans using the plugin, but everything goes to idle when the service is running (cpu fans still spin at minimum). I set 'fan speed at idle' to 40 percent. Curiously, when I now try to change either that value or the low value in 'fan speed range' it just goes back to 40 percent, no chance to apply or save. The upper 'fan speed range' value can be changed. But the fans aren't going to 40 percent at idle, they are just off, and the identify commands no longer function.

I've tried a reset and a cold boot. Fans run full speed during boot as expected, then when Unraid comes alive the fans tied to disk temperature go to 0 and the fans tied to CPU temp are full speed. When I change a setting in the plugin the fans tied to CPU temp then go to idle.

From the logs it appears the commands are being sent:

Nov 7 20:38:27 Goose fanctrlplus: [Intake] Temp=*°C (Idle) → PWM=102 → RPM=0

Nov 7 20:40:31 Goose fanctrlplus: [CPU_Rear] Temp=47°C (CPU) → PWM=132 → RPM=320

Nov 7 20:40:31 Goose fanctrlplus: [CPU_Front] Temp=47°C (CPU) → PWM=132 → RPM=307

Nov 7 20:40:31 Goose fanctrlplus: [Rear_Exhaust] Temp=47°C (CPU) → PWM=132 → RPM=0

Any ideas? TIA

Sounds like the driver is fighting for control of the fans on the backend and getting stuck in an odd state. Have you disabled motherboard control of all fans except your CPU? Do you have any other plugins or containers installed that poll the fans?

Holy crap is this plugin nice. Just so easy to use. I installed it on a backup server we're setting up for offsite and it was so easy to get going that I immediately went to my main server and replaced the Dynamix pluggin and had the setup replicated in maybe 2 minutes. Thank you, thank you, thank you!!!!