Feature

See what the board sees

in this fork since v2.7.0

The Turing Pi 2 has a temperature sensor. Upstream's device tree never described it, so nothing could read it and the fan ran against nothing.

5trip points the fan follows

40metric families the board exposes

0temperature readings upstream can take

the board's own thermal zone and /metrics, 2026-09-12.

See it in the demo →The Cooling page, with real readings from a board.Do it on your board →The metrics port, a scrape config and the dashboard.The evidence →Every family the board can measure, catalogued.The board describes its own API →Where the readings on this page come from.

The Cooling page: the BMC's temperature against the points where the fan steps up, with the fan's step and mode below it.

The argument

A fan speed nobody can explain is a fault waiting to be misdiagnosed. The board now reports the temperature, the trip points and which trip put the fan where it is, so "why is the fan at step 4" has an answer. Nothing here writes to the sensor; a held fan is taken back by the daemon above the hottest active trip.

The full argument, with every measurement →