Skip to content

Conversation

@ChaosInfinited
Copy link
Contributor

Currently, the temperature module relies on hwmon paths, which can change when new devices are added or kernel driver order changes. This makes configurations fragile; for example, adding a USB device like a new gaming controller can break the CPU or GPU temperature readings.

What this PR does:

  • Introduces a new hwmon-name option for the temperature module.
  • Allows users to select a hwmon device by its stable name (from /sys/class/hwmon/*/name) instead of a potentially shifting path.
  • Requires input-filename to be set.
  • Ensures hwmon-name cannot be used with hwmon-path or hwmon-path-abs to avoid conflicts.
  • Updates documentation to reflect the new option.

This provides a more stable and predictable way to configure temperature sensors, preventing breakage due to dynamic hwmon ordering.

Let me know what you think!
Kind regards.

Allow selecting a hwmon device for the temperature module by its
name instead of a fixed hwmon path.

This avoids fragile configurations that break when new hwmon
devices are added and the kernel changes hwmon ordering.

The hwmon-name option is mutually exclusive with hwmon-path and
hwmon-path-abs to prevent ambiguous configurations.
@ChaosInfinited ChaosInfinited changed the title temperature: add hwmon-name option for stable sensor selection feat(temperature): add hwmon-name option for stable sensor selection Dec 27, 2025
@ChaosInfinited
Copy link
Contributor Author

The nix fail seems to be coming from upstream, from cava.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant