## Description I am using CoolerControl 3.1.1 on CachyOS (6.18.7-2-cachyos) with multiple hwmon devices: * Motherboard Super I/O (IT8696 via it87) where fan control is enabled and working * AMD GPU (amdgpu) where fan control is handled by the GPU firmware * Corsair PSU (corsairpsu) where fan control is handled by the PSU firmware For some devices such as the GPU and PSU, fan control is possible in principle, but I intentionally want these devices to manage their own fan behavior. My use case is monitoring only (RPMs and temperatures), not overriding their control logic. During startup, CoolerControl probes pwm\* attributes on all detected hwmon devices. For GPU and PSU hwmon devices, some PWM nodes are read-only or not writable in the current configuration. This results in warnings such as: `PWM fan at /sys/class/hwmon/hwmonX/pwm1 is NOT writable` These warnings are technically correct, but not actionable for users who explicitly want these devices to remain self-managed. --- ## Current limitations In CoolerControl 3.1.1: * Disabling a device removes it entirely from the UI, including RPM * There is no per-device option to disable fan or PWM control while keeping sensors visible * PWM probing failures generate WARN-level log messages and trigger a warning state in the UI, prompting the user to acknowledge issues. * The only workaround is lowering the global daemon log level, which also suppresses unrelated warnings --- ## Requested feature Add a per-device monitor-only mode or equivalent option that: * Keeps temperature and RPM sensors visible * Disables PWM probing and fan control attempts for that device * Prevents PWM write failures from being logged as warnings for that device * Avoids triggering false issue or error indicators in the UI This would allow users to explicitly choose which devices CoolerControl is responsible for controlling, versus which devices remain self-managed. --- ## Why this matters This is not a hardware or driver failure. Fan control works correctly where enabled. The current behavior mainly impacts user experience by creating persistent warnings for configurations that are intentional and valid. Providing a monitor-only mode would reduce log noise, eliminate false alarms, and give users clearer control over responsibility boundaries between CoolerControl and device firmware or drivers. --- ## System context * CoolerControl 3.1.1 * Fan controller: IT8696 via it87 (h2ram-mmio) * GPU: AMD (amdgpu hwmon) * PSU: Corsair (corsairpsu hwmon) * Daemon running as root