The Pi 5 Hardware Monitor is a lightweight Cockpit plugin designed specifically for Raspberry Pi 5 systems, providing a clean, real-time view of critical hardware and system metrics directly within the Cockpit web interface. It displays CPU, I/O, PMIC, and NVMe temperatures, fan speed and power levels, detailed power/throttling status from vcgencmd, system load, memory usage, storage health (NVMe, SD, USB), PCIe link data, voltages, clocks, and firmware info, all formatted into easy-to-read cards with clear status indicators. The plugin uses efficient, on-demand polling that only runs while the page is open, minimizing system impact, while an optional background history collector tracks trends over time for deeper diagnostics—making it ideal for monitoring performance and stability on headless or remote Pi 5 nodes such as those used in AllStarLink setups. Screenshots are at the bottom of the ReadMe.
Jeff - KE2HNI
If you run into any bugs please post it on /github so I can track them & fix them and help you get it working... I am working on a version for Pi 4 also, just waiting on a fan for my Pi 4... I also have a version for anyone using the Dell Wyse 3040, & I have a version for the current Raspberry Pi OS (Pi 5) - (Pi 4) coming soon...
Thank you, glad you like it, I occasionally update it if you have the newest version it should show you when and update is needed, also I have 1 for the Pi 4 and even the OS's... If you have any questions just post on Github
As long as it's a Pi 5/ASL 3 and you choose the Pi 5 version you'll be fine, if you grab the wrong 1, the installer has built-in checks to make sure the unit is compatible, and if there are any missing requirements when related to other software packages the installer will install them, also during the install make sure you answer the questions correctly about the user and permissions, if you have any install issues, post the issue on GitHub so I can monitor and assist you.
Correct—the application currently supports only the standard Raspberry Pi 5. That is why I built hardware verification into the installer: it prevents the application from being installed on untested or incompatible hardware and potentially causing problems with the user’s system.
Although the Compute Module 5 uses much of the same core hardware, some sensor names, hardware paths, and available readings differ. I currently do not have a CM5 available to test and properly adapt the application for it.
However, the complete project is available on GitHub. If you would like to experiment with CM5 support, you can download it and use ChatGPT to help modify the hardware detection and sensor-handling code.