rcourtman 267ffcc3af Keep node temperature selection when details lack a CPU reading ...

The first version of this change walked every temperature source and
took the first usable one, which changed two cases that worked before.
Details holding only NVMe or GPU readings displaced a valid scalar CPU
reading, so the node lost its CPU temperature. An unusable earlier
record no longer fell back to the scalar; the walk went on to a later
record that was marked unavailable and suppressed the display.

The record selection is back to exactly what it was. Only when it yields
nothing usable does the adapter use proxmox.temperatureDetails, and
only if that holds a current CPU reading; otherwise it falls back to the
scalar as before, still without inventing a low or record. The contract
notes now say the adapter forwards the poller's low and record values
and that keeping them across polls is the poller's job.

2026-10-06 17:45:10 +01:00

..

internal

Describe releases as the fixed release train everywhere

2026-10-06 12:06:18 +01:00

v6

Keep node temperature selection when details lack a CPU reading

2026-10-06 17:45:10 +01:00

control_plane.json

Cut 6.5 and later releases from main

2026-10-04 18:37:43 +01:00

control_plane.schema.json

…