29 minutes ago, CkChong said:

External fan controllers vary a lot in hardware and protocols, so they’re unfortunately out of scope for this plugin.

Ok. I was just having a little hope since that controller is also open source.

4 hours ago, CkChong said:

External fan controllers vary a lot in hardware and protocols, so they’re unfortunately out of scope for this plugin.

You and @SasaKaranovic should team up, as OpenFanController does offer a simple API to control the fans, honestly with your plugin compared with the power OpenFanController would make an amazing combo!

Also @CkChong very nice plugin!

12 hours ago, CkChong said:

External fan controllers vary a lot in hardware and protocols, so they’re unfortunately out of scope for this plugin.

@CkChong I've been testing the plugin, and honestly, you managed to make something that works so much better than the Dynamix System AutoFan plug. I would like to ask, if you would consider extending the support to OpenFanController? Right now users are using the OpenFanController docker to manage access to the device and it's API, and a seperate control docker called OpenFanService to regulate the fan speeds, the latter being a purely text based configuration. Your plugin could be extended to support it via it's API, rather than the scripts you run to set the PWM on the fans at the moment.

I'd happily sponsor the OpenFanController, so you can test and build up the support.

Edited July 25, 2025Jul 25 by PeterDB

3 hours ago, PeterDB said:

@CkChong I've been testing the plugin, and honestly, you managed to make something that works so much better than the Dynamix System AutoFan plug. I would like to ask, if you would consider extending the support to OpenFanController? Right now users are using the OpenFanController docker to manage access to the device and it's API, and a seperate control docker called OpenFanService to regulate the fan speeds, the latter being a purely text based configuration. Your plugin could be extended to support it via it's API, rather than the scripts you run to set the PWM on the fans at the moment.

I'd happily sponsor the OpenFanController, so you can test and build up the support.

Thanks for the kind words and support — really appreciate it!

At the moment, I don’t have any plans to support OpenFanController. I’m just a hobbyist and beginner — FanCtrl Plus exists mainly because I personally use Unraid, and it helps me solve my own needs. I’m happy to share it with others who might find it useful, but I’m not aiming to cover hardware I don’t personally use.

I hadn’t looked into OpenFanController before, so I appreciate you bringing it to my attention. It seems like a solid system, though it also appears to be somewhat commercial in nature.

That said — nothing is ever off the table. I just want to be honest that right now, I don’t plan to support it. But I truly appreciate your interest, your encouragement, and your recognition of the work that’s gone into FanCtrl Plus.

Hope the next version brings even more improvements you’ll enjoy!

On 7/23/2025 at 8:38 PM, CkChong said:

Funny timing — I’m adding log toggle support for the next version, and each fan will have its own on/off switch for syslog logging.

I’m also working on a new feature that lets users identify and label each PWM controller more easily, to help with reference and setup. Currently finalizing the UI and testing before release.

Here’s a quick preview of the log toggle in action (upcoming version):

Oh this is awesome, one of my biggest gripes will be solved. Thank you!

Especially since solutions on the autofan plugin thread are along the lines of "fork it and change it yourself 🤷"

Hey, just found your plugin today and I was hoping for a little wishlist consideration:

I have 2 fans, 1 case and 1 cpu fan.. the cpu fan is controlled by bios and its ok but the case fan to be able to adjust based of hdd temps i need your app, but as i understand it will then override bios curve settings and wont react on mobo/cpu temps if this plugin is running.

So my wish is if you could add these sensors too, so the case fan could also react to cpu mobo.

Thanks for reading :)

12 hours ago, theusername said:

Hey, just found your plugin today and I was hoping for a little wishlist consideration:

I have 2 fans, 1 case and 1 cpu fan.. the cpu fan is controlled by bios and its ok but the case fan to be able to adjust based of hdd temps i need your app, but as i understand it will then override bios curve settings and wont react on mobo/cpu temps if this plugin is running.

So my wish is if you could add these sensors too, so the case fan could also react to cpu mobo.

Thanks for reading :)

Thanks for the feedback.

CPU temperature monitoring is planned for a future version, but not the upcoming release.

Just need a bit of time to figure out the logic and test things properly — stay tuned!

That would be great! Does FanCrtl Plus autostart after a restart?

13 hours ago, theusername said:

Hey, just found your plugin today and I was hoping for a little wishlist consideration:

I have 2 fans, 1 case and 1 cpu fan.. the cpu fan is controlled by bios and its ok but the case fan to be able to adjust based of hdd temps i need your app, but as i understand it will then override bios curve settings and wont react on mobo/cpu temps if this plugin is running.

So my wish is if you could add these sensors too, so the case fan could also react to cpu mobo.

Thanks for reading :)

Yes, exactly what I noticed, too. As soon as Fan Crtl Plus is running, my CPU fan no longer works as intended (bios controlled).

BTW: I just noticed a bug. Is it possible that Fan Crtl Plus wakes up my array from sleep although I did not access it?

Edited July 26, 2025Jul 26 by naddel81

3 hours ago, naddel81 said:

That would be great! Does FanCrtl Plus autostart after a restart?

Yes — FanCtrl Plus automatically starts with the Unraid array after a reboot. No manual action is needed.

3 hours ago, naddel81 said:

Yes, exactly what I noticed, too. As soon as Fan Crtl Plus is running, my CPU fan no longer works as intended (bios controlled).

If your CPU fan is being controlled by FanCtrl Plus instead of the BIOS, I would recommend not assigning the CPU fan’s PWM controller to FanCtrl Plus. You can use the “Pause 30s” button to help identify which PWM controls your case fan and exclude the CPU fan.

Even in future versions that may support CPU temperature input, it’s not advisable to control the CPU fan with FanCtrl Plus. A better approach—just like what theusername mentioned—is to use CPU temperature to help adjust your case fan speed if needed, while still letting the BIOS handle the CPU fan directly. This avoids unintended conflicts unless you’re absolutely sure of what you’re doing.

The upcoming version will allow you to label each PWM controller after identifying it, so you’ll avoid confusion going forward.

3 hours ago, naddel81 said:

BTW: I just noticed a bug. Is it possible that Fan Crtl Plus wakes up my array from sleep although I did not access it?

FanCtrl Plus does not wake up spun-down disks. It checks temperatures in a way that keeps sleeping drives untouched.

If all monitored disks are asleep, the fan will simply run at the minimum PWM (Fan Speed) you’ve configured.

On 7/23/2025 at 3:40 AM, CkChong said:

Hi. Thanks for the kind words, glad it’s working better for your NVMe temps!

Regarding the Temp=0°C on [HDD_bay], here are a few things to check:

• If the HDD is spun down, Unraid will report 0°C — that’s expected. At least one of the monitored drives must be active (spun up) for temperatures to be reported correctly.

• If the drive is active but still showing 0°C, it could be a SMART polling issue or an unsupported drive model for temp reporting.

• You can try accessing the drive (read a file) to see if it wakes up and reports a valid temperature.

As for [M2_bay_right_side] and [M2_bay_left_side] showing PWM=0 and RPM=0 even with valid temps — it’s likely due to your Low Temp setting being higher than the current temp (e.g. if Low = 35°C but current temp = 28°C), the fan will stay off as intended.

Let me know what your Low/High temp and Min PWM values are — happy to help confirm.

Hi :)

Yes the [M2_bay_right_side] and [M2_bay_left_side] PWM values are totally fine because I configured it like that so the fan should not spin. This is all right :)
It was just the issue with my HDD_bay where I have no HDD drives but SSD drives😉
It seems the awk command used in your plugin is not able to parse the smart attribute by its name correctly.
I created a more or less detailed issue in your repository -> https://github.com/ck9393/fanctrlplus/issues/23#issue-3265817330

46 minutes ago, s11 said:

Hi :)

Yes the [M2_bay_right_side] and [M2_bay_left_side] PWM values are totally fine because I configured it like that so the fan should not spin. This is all right :)
It was just the issue with my HDD_bay where I have no HDD drives but SSD drives😉
It seems the awk command used in your plugin is not able to parse the smart attribute by its name correctly.
I created a more or less detailed issue in your repository -> https://github.com/ck9393/fanctrlplus/issues/23#issue-3265817330

Thanks for the detailed report! I really appreciate it — I don’t have any SATA SSDs in my setup, so I completely missed this issue. I’ll fix it in the next version to better support drives like yours.

20 minutes ago, CkChong said:

Thanks for the detailed report! I really appreciate it — I don’t have any SATA SSDs in my setup, so I completely missed this issue. I’ll fix it in the next version to better support drives like yours.

Not a problem :) Im looking forward 👍
I thought about creating a PR but unfortunately I felt not that familiar with SmartAttibutes and if there are standards for different types of drives, so if its always right to have Temperature_Celsius for HDDs or Airflow_Temperature_Cel for Sata SSDs.

9 minutes ago, s11 said:

Not a problem :) Im looking forward 👍
I thought about creating a PR but unfortunately I felt not that familiar with SmartAttibutes and if there are standards for different types of drives, so if its always right to have Temperature_Celsius for HDDs or Airflow_Temperature_Cel for Sata SSDs.

Thanks, no worries — you’ve already provided really helpful info!

I’m still learning too, especially when it comes to the different SMART attributes across HDDs, SATA SSDs, and NVMe.

I’ll try testing with some older SSDs I have on hand and see how they behave. Hopefully they’re still alive. 😅

Appreciate your input, it helps improve the plugin for everyone!

Amazing plugin — thanks for sharing it!

Two suggestions that would make it even better:

1. Allow using other temps (like CPU or motherboard) to control case fans.

2. Let us display RPMs for fans not controlled by the plugin in the dashboard (e.g., CPU fan via BIOS).

Appreciate the great work!

1 hour ago, gabbro246 said:

Amazing plugin — thanks for sharing it!

Two suggestions that would make it even better:

1. Allow using other temps (like CPU or motherboard) to control case fans.

2. Let us display RPMs for fans not controlled by the plugin in the dashboard (e.g., CPU fan via BIOS).

Appreciate the great work!

Thanks — really glad you’re enjoying the plugin!

CPU temp support is already on the roadmap — just need a bit of time to work through the logic.

As for showing RPMs for fans not controlled by the plugin, I’ll definitely look into it.

In the meantime, I think the Airflow dashboard panel already shows all detected fan RPMs by default.

On 7/26/2025 at 12:49 AM, Scheev said:

Oh this is awesome, one of my biggest gripes will be solved. Thank you!

Especially since solutions on the autofan plugin thread are along the lines of "fork it and change it yourself 🤷"

Just dropping in to let you know — the new version is out now, with per-fan syslog toggle included.

Hope it does the trick — feel free to report back if you hit any issues.

Thank you for your work, your plugin is excellent! I have a feature request—would you consider adding it? Could you possibly include sensors for CPU, network cards, or PCIe devices as monitorable options?

1. I’m currently using a CX4421 network card with an attached fan. I can already detect this NIC’s temperature via the System Temp plugin, and I’d like your plugin to automatically control its fan based on that data.

2. If CPU monitoring were available, I could use the plugin to manage the case fans, which would lead to better heat dissipation.

Edited July 27, 2025Jul 27 by hehaibo444
修改

8 hours ago, hehaibo444 said:

Thank you for your work, your plugin is excellent! I have a feature request—would you consider adding it? Could you possibly include sensors for CPU, network cards, or PCIe devices as monitorable options?

1. I’m currently using a CX4421 network card with an attached fan. I can already detect this NIC’s temperature via the System Temp plugin, and I’d like your plugin to automatically control its fan based on that data.

2. If CPU monitoring were available, I could use the plugin to manage the case fans, which would lead to better heat dissipation.

Thanks for the great feedback!

I haven’t looked into reading NIC or PCIe device temps yet, so I can’t say for sure how that would work.

That said, CPU temp monitoring is already on the roadmap, and will definitely help with case fan control in setups like yours. Just need a bit of time to design and test it properly!

Sharing settings for my TS-873A using the QNAP-EC plugin. Went with aggressive 28°C → 38°C cooling for HDD array fans to prioritize drive longevity, and 38°C → 55°C for M.2/chipset cooling. Just implemented these settings so too early for performance data, but wanted to share the configuration in case it helps others.

4 hours ago, Trunkton said:

Sharing settings for my TS-873A using the QNAP-EC plugin. Went with aggressive 28°C → 38°C cooling for HDD array fans to prioritize drive longevity, and 38°C → 55°C for M.2/chipset cooling. Just implemented these settings so too early for performance data, but wanted to share the configuration in case it helps others.

Thanks for sharing your setup — always great to see how others are using the plugin!

Hope you’re happy with how it’s working so far!

Hello! I'm not sure if I'm doing something wrong, or I found a bug? I noticed that the widget started showing inactive, but I'm pretty sure it's running. Pls the see attached files.

4 hours ago, theusername said:

Hello! I'm not sure if I'm doing something wrong, or I found a bug? I noticed that the widget started showing inactive, but I'm pretty sure it's running. Pls the see attached files.

Hi! Thanks for reporting — if the FanCtrl Plus UI shows “Running” but the Dashboard widget says “Inactive,” it usually means the background update script may not be writing data correctly.

Could you try the following steps:

1. Go to the Syslog On/Off section and make sure Syslog is enabled.

2. Wait for 1–2 intervals, or click “Run Now” to force an update.

3. Then go to Tools → System Log, and search for any lines containing fanctrlplus.

Please paste any recent log entries here — especially lines like:

fanctrlplus: [CASEFAN] Temp=XX → PWM=XXX → RPM=XXXX

Also, just to help narrow it down — do you remember if the Dashboard started showing “Inactive” after any recent change, such as editing fan settings, renaming a fan, updating Unraid, etc.?

Thanks again — with a bit more info I’ll help you get it sorted.

Edit: One more thing to check — did you happen to rename the fan's Custom Name using the same name with different capitalization? (e.g. casefan→ CASEFAN)

If so, there’s a known issue where this might cause config mismatches. In that case, you may want to delete the fan block and re-create it using a completely new name.

P.S. This only applies to Custom Name. You don’t need to worry about the PWM Label — it’s purely for display purposes and can be freely named. It does not affect functionality or cause this issue.

Let me know if that might apply — just to help rule it out.

Edited July 29, 2025Jul 29 by CkChong

All day yesterday it was saying offline, i tried rebooting etc, but today (sofar) it's saying status:running! All I did was let some time pass. I did rename the fan labels, from casefan to CaseFan for example, but that was 2 ish days ago.

Everything seems ok at the moment syslog was on and log is just a bunch of this:

"Jul 29 08:56:51 N fanctrlplus: [CASEFAN] Temp=31°C → PWM=230 → RPM=1333

Jul 29 08:58:56 N fanctrlplus: [CASEFAN] Temp=44°C → PWM=245 → RPM=1397

Jul 29 09:01:00 N fanctrlplus: [CASEFAN] Temp=34°C → PWM=230 → RPM=1328

Jul 29 12:03:03 N fanctrlplus: Manual Run [CASEFAN] Temp=53°C → PWM=255 → RPM=1433"

I did rename a unused CPU fan, and the fan went inactive since i dont use it in your plugin, rebooted and fans worked as expected, but still the widget said inactive, until today.

Strange!

Edited July 29, 2025Jul 29 by theusername
added info

49 minutes ago, theusername said:

All day yesterday it was saying offline, i tried rebooting etc, but today (sofar) it's saying status:running! All I did was let some time pass. I did rename the fan labels, from casefan to CaseFan for example, but that was 2 ish days ago.

Everything seems ok at the moment syslog was on and log is just a bunch of this:

"Jul 29 08:56:51 N fanctrlplus: [CASEFAN] Temp=31°C → PWM=230 → RPM=1333

Jul 29 08:58:56 N fanctrlplus: [CASEFAN] Temp=44°C → PWM=245 → RPM=1397

Jul 29 09:01:00 N fanctrlplus: [CASEFAN] Temp=34°C → PWM=230 → RPM=1328"

Strange!

Thanks for the update! Just to clarify — you mentioned renaming the label, but it’s possible the issue was actually related to the Custom Name, which is different from the PWM Label.

I left a note above about this — feel free to refer back to confirm which one was changed.

PWM Labels are just for display and don’t affect functionality, but renaming the Custom Name (especially with only case changes) can currently cause temporary issues in the Dashboard. That bug has been identified and will be fixed in the next version.

Since things are working fine now, feel free to keep an eye on it — and if it happens again, any extra details would be super helpful. Thanks again!