Local Linux SBC health check

Read basic observations from a Linux host you administer. Processing stays in this browser. No report is sent to LeMaker, FleetCare, analytics or a third party. No account or email is needed.

This is a one-time local check. OpenWrt, HAOS and managed appliances are outside its supported runtime. Inside a container, readings may describe the container rather than its host. Containers, Home Assistant entities, security, backups, disk integrity and hardware failure are not inspected. A successful report does not certify FleetCare compatibility.

Choose your workflow

Use manual observations below if Python is unavailable. The optional collector needs Python 3.9 or newer on Linux and uses only its standard library. It does not install dependencies, escalate privileges, write files, contact the network or install a background service.

Download Python collector v1.0.0 and its SHA-256 manifest.
Open the script in a text editor and inspect its small file/command allowlist. Compare its hash with the separately reviewed release manifest. A hash from the same site detects accidental changes; it is not an independent signature.
Run it explicitly as your ordinary user. Do not use sudo.

python3 --version
sha256sum lemaker-health-check-v1.py
python3 lemaker-health-check-v1.py

The script prints every exported field first. Only if you want a local file, save that output yourself:

python3 lemaker-health-check-v1.py > lemaker-local-health.json

Exported fields: schema/collector version, runtime context, OS ID/version, architecture, kernel release (no hostname), uptime, memory totals/availability, root capacity/available space and read-only flag, up to eight numbered sensor aliases with readings, and a failed-system-service count. Unknown values are null; unavailable sensors form an empty list. No hostname, address, serial, raw mount path, service name, credentials, logs or process command line is exported.

The collector and manual commands work without JavaScript. Read their output locally. At 85% used, investigate expected storage growth; this is a heuristic. Unexpected read-only mounts warrant data-preservation and power/storage checks. No universal temperature threshold or security all-clear can be inferred. JavaScript is needed only for the optional browser assessment.

Local results and exact export preview

No report has been assessed.

Next checks

Investigate crashes, power and storage symptoms

Understand filesystem and recovery trade-offs

Review Linux SBC hardening guidance

Not tested

Filesystem integrity, SD-card life, SMART status, malware, firewall rules, updates, network reachability, storage performance and application/container health are not tested. Sensor aliases do not establish sensor identity or a safe platform temperature. Missing permissions/tools and timed-out service checks mean unknown, never healthy.