jermcee

FanCtrlPlus widget showing wrong/blank fan sensor instead of configured it8696 fan sensor Hi, I’m having an issue with the FanCtrlPlus dashboard/widget showing an incorrect fan reading. I’m using Unraid on a GIGABYTE B860I AORUS PRO ICE motherboard. The board’s real fan readings are coming from the it8696 sensor chip, but the FanCtrlPlus widget appears to be picking up a blank/bogus acpi_fan entry instead. The actual fans are working and reporting correctly from terminal: root@UnraidNas:~# for h in /sys/class/hwmon/hwmon*; do echo "===== $(cat "$h/name" 2>/dev/null) : $h =====" for f in "$h"/fan*_input; do [ -e "$f" ] && echo "$(basename "$f"): $(cat "$f" 2>/dev/null) RPM" done done ===== nvme : /sys/class/hwmon/hwmon0 ===== ===== acpi_fan : /sys/class/hwmon/hwmon1 ===== fan1_input: RPM ===== gigabyte_wmi : /sys/class/hwmon/hwmon2 ===== ===== coretemp : /sys/class/hwmon/hwmon3 ===== ===== acpitz : /sys/class/hwmon/hwmon4 ===== ===== it8696 : /sys/class/hwmon/hwmon5 ===== fan1_input: 1121 RPM fan2_input: 1229 RPM fan5_input: 1403 RPM The problem is that the widget shows FAN 1 = 0 RPM, even though the actual CPU fan is clearly reporting correctly under: /sys/class/hwmon/hwmon5/fan1_input Confirmed directly: root@UnraidNas:~# cat /sys/class/hwmon/hwmon5/fan1_input 1126 The bogus/blank sensor appears to be this ACPI fan device: root@UnraidNas:~# readlink -f /sys/class/hwmon/hwmon1 /sys/devices/platform/INTC1042:00/INTC1063:00/hwmon/hwmon1 root@UnraidNas:~# udevadm info -a -p $(readlink -f /sys/class/hwmon/hwmon1) | head -80 looking at device '/devices/platform/INTC1042:00/INTC1063:00/hwmon/hwmon1': KERNEL=="hwmon1" SUBSYSTEM=="hwmon" DRIVER=="" ATTR{name}=="acpi_fan" looking at parent device '/devices/platform/INTC1042:00/INTC1063:00': KERNELS=="INTC1063:00" SUBSYSTEMS=="platform" DRIVERS=="acpi-fan" The actual usable motherboard fan sensor is: root@UnraidNas:~# readlink -f /sys/class/hwmon/hwmon5 /sys/devices/platform/it87.2624/hwmon/hwmon5 So it looks like the widget is either: Grabbing the first fan1_input it finds, even if it is blank/unreadable. Not honoring the configured/identified FanCtrlPlus sensor labels. Not allowing the user to exclude bad hwmon devices like acpi_fan. Showing stale/wrong sensor mapping in the dashboard widget. Feature/fix request: Could the widget ignore fan inputs that return blank/unreadable values, or allow users to explicitly select/exclude hwmon sources for the widget? In my case, the plugin should use: it8696 / hwmon5 / fan1_input = CPU fan it8696 / hwmon5 / fan2_input = Top exhaust it8696 / hwmon5 / fan5_input = Array fans and ignore: acpi_fan / hwmon1 / fan1_input = blank This seems like either a widget bug or a sensor-selection issue. The real fan readings are correct from /sys/class/hwmon, but the widget is displaying the wrong source. Thanks.

Can we add the ability to change the backup order for the container's?