Disambiguate hwmon chips with duplicate names (#33)

[eous]

When multiple hwmon sysfs devices share the same name (e.g. jc42 DIMM temp sensors, multiple NVMe drives), they produced identical SensorIds and collided in the HashMap — only one reading survived.

Detect duplicate chip names during discovery and append the sysfs device symlink basename to disambiguate (e.g. jc42-9-0018, nvme-nvme0). Falls back to the hwmon directory index when no device symlink exists.

Also fixes is_gpu_hwmon_chip to use prefix matching so multi-GPU systems still get "GPU " label prefixes, and pre-expands board template label overrides so unqualified names continue to match disambiguated chips.

#33

[Copilot]

Pull request overview

This PR addresses hwmon sensor ID collisions when multiple sysfs hwmon devices share the same name (e.g., multiple jc42 DIMM sensors or multiple NVMe drives), ensuring each sensor remains uniquely addressable and readable across discovery/polling.

Changes:

• Detects duplicate hwmon chip names during discovery and disambiguates them by appending a sysfs-derived suffix (device symlink basename, with a fallback).
• Updates GPU hwmon chip detection to also match disambiguated multi-GPU chip names (prefix match).
• Pre-expands board-template label overrides so existing unqualified overrides continue to apply after chip disambiguation.

Comments suppressed due to low confidence (1)

src/sensors/hwmon.rs:154

• discover_type for current sensors is still passed label_overrides instead of the newly built effective_overrides. For disambiguated chips (e.g. jc42-9-0018), this prevents board template label overrides from applying to curr* sensors and makes behavior inconsistent with temp/fan/in/power discovery. Pass &effective_overrides here as well.

            discover_type(
                hwmon_dir,
                display_name,
                "curr",
                SensorCategory::Current,
                SensorUnit::Amps,
                1000.0,
                label_overrides,
                &mut entries,
            );

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.