Rpi Cooling
Raspberry Pi official-case PWM fan telemetry (RPM, PWM duty cycle, discrete cooling state) via hwmon/thermal sysfs, as a typed, versioned Swamp model — catches a fan that's been commanded to spin but the tachometer reports it isn't.
Documentation, descriptions and setup brought up to date with running every workflow under a single swamp serve (2026-11-05).
Global Arguments
| Argument | Type | Description |
|---|---|---|
| hwmonBasePath? | string | Base sysfs path to search for the fan's hwmon device. |
| thermalBasePath? | string | Base sysfs path to search for the fan's cooling_device. |
| fanHwmonName? | string | The hwmon "name" file value identifying the fan device. Confirmed as |
| fanCoolingDeviceType? | string | The thermal cooling_device "type" file value identifying the fan\ |
Resources
Read PWM fan RPM/duty/cooling-state from cooling-local and assert the fan hasn't stalled — commanded to spin (pwmDuty > 0) but the tachometer reports 0 RPM. That combination is the entire point of this extension: it's a real failure mode that produces no other symptom until the SoC starts thermal throttling. Scheduled every 5 minutes, same cadence as the telemetry-focused @aaronge/host-health/@aaronge/rpi-health workflows, since a stalled fan is time-sensitive in a way boot configuration isn't.
Ship the workflow in the package so a single ops repo can pull it and run it under swamp serve's own scheduler.
Added 1 workflows
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault1/1earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License1/2partial
no SPDX license declared
- Verified public repository2/2earned