Few problems with installation

[afalout]

First - thank you for this project. It is very much appreciated and needed.

I have limited experience with Docker so would appreciate any help getting this to work.

After running sensors-detect and docker compose up, I open http://mynas:5002 in web browser.

Under "Status", I see:

Active Profile: Loading...
Uptime: Loading...
CPU Load: Loading...

Above never changes.

Clicking on any Fan Profiles, (Silent, Cool. Aggressive) results in "Not Found" page.
Fan Speed graph is empty.

Under "Temperatures" i see:
temp1: 27.8°C
temp2: 29.8°C
... but the graph shows only one line, at 28.8 (I suppose that is the average of 2 sensors?)

Running $ sudo sensors in SSH session shows:
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +38.0°C (high = +80.0°C, crit = +100.0°C)
Core 0: +27.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +24.0°C (high = +80.0°C, crit = +100.0°C)
Core 2: +38.0°C (high = +80.0°C, crit = +100.0°C)
Core 3: +30.0°C (high = +80.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1: +27.8°C
temp2: +29.8°C

In the code, I see: HWMON_PATH = "/sys/class/hwmon/hwmon4"
However, on my system I have only:
hwmon0/ hwmon1/ hwmon2/
$ sudo cat /sys/class/hwmon/hwmon0/name
acpitz
$ sudo cat /sys/class/hwmon/hwmon1/name
asus
$ sudo cat /sys/class/hwmon/hwmon2/name
coretemp

Any help appreciated!

Thanks,
Andrej

[Rocketplanner83]

Hi Andrej,

Thanks for the detailed write-up — that helps a lot.

From what you’ve described, this is almost certainly due to the older hard-coded HWMON_PATH behavior. Early versions assumed a fixed hwmon index (e.g. /sys/class/hwmon/hwmon4), which varies between systems and causes exactly the symptoms you’re seeing:

• Status fields stuck on “Loading”
• Fan profile routes returning “Not Found”
• Temperature graph showing only one value
• Empty fan graph

In v1.1 this has been corrected. The application now dynamically detects hwmon devices instead of assuming a fixed path.

Specifically:

• It enumerates /sys/class/hwmon/*
• Matches based on the name file (e.g. coretemp, asus, nct6775, etc.)
• Falls back gracefully if a sensor class is missing

Given your output:

hwmon0 → acpitz  
hwmon1 → asus  
hwmon2 → coretemp

The older version would fail because it was pointing at a non-existent index.

I recommend:

1. Pull latest code
2. Rebuild the container:

   docker compose down
   docker compose build --no-cache
   docker compose up -d
   

3. Ensure /sys/class/hwmon is mounted into the container

After upgrading to v1.1, the UI should populate correctly and fan routes should resolve.

If it still fails after updating, please share:

docker logs truefan
curl http://localhost:5002/status

That will tell us exactly where detection is breaking.

Thanks again for the report — this was a valid issue in earlier revisions and is now addressed.