Short answer
If one category is unavailable, choose Any Sensor and verify whether Smart Breeze can use another live reading with a labeled fallback. Expand Thermal Sensors to see which individual validated readings Build 22 discovered. If CPU, GPU, Memory, Battery, Hottest, and the explorer are all unavailable, confirm the exact model, restart once for a fresh session, and copy diagnostics. Do not install the privileged fan helper: it cannot create missing read-only keys. Build 21 had a confirmed M5 Air monitoring defect; the changed Build 22 path awaits physical verification on that Mac.
Run the safe monitoring checklist
- Confirm Smart Breeze version 0.3.13 Build 24, the exact model identifier, and macOS version/build.
- Choose Any Sensor and note whether a fallback label appears.
- Start an ordinary known workload and verify whether any category updates.
- Restart once, reopen the canonical copy in /Applications, and repeat the read-only observation.
- Check Known issues, then copy Smart Breeze diagnostics if the state persists.
Do not move between duplicate app copies, run from the DMG, or change fan-helper state while diagnosing a read-only sensor problem. Those variables add noise without creating temperature-key compatibility.
Build 21 result and Build 22 status on the tested M5 MacBook Air
The lack of a fan is expected for this Mac. Build 21's monitoring failure was not. Treat Build 22 temperature availability as unverified on the M5 Air until a physical run confirms which readings the Mac exposes.
Why the privileged helper is not a sensor fix
Smart Breeze reads monitoring data without administrator access. The privileged helper exists for authenticated, bounded fan-control writes and verified System handoff on qualified fan hardware. Installing it does not change which read-only keys the app discovers.
- It cannot create a temperature key that Build 22 does not discover.
- It cannot turn aggregate private keys into Apple-supported sensor metadata.
- It cannot add fans to a fanless Mac.
- It cannot bypass exact-model fan-control qualification.
Temperature-driven control must fail closed
Smart Boost depends on a current temperature input. Smart Breeze's helper safety model requests verified System control when temperature data remains missing for about ten seconds during manual ownership. A stale or absent source must never be replaced with an invented low value that keeps a fan target active indefinitely.
Unknown topology follows the same principle. Missing fan count, bounds, or ownership readback means no fan write. Monitoring compatibility and control qualification are separate gates, and either can stop an action safely.
Send a report that can improve compatibility
Copy diagnostics from Smart Breeze and include the exact steps, whether any category ever appeared, whether the issue followed sleep or was present at first launch, and whether the Mac is fanless. The diagnostic report contains hardware and app state, not personal files, and is never sent automatically.
Sources and scope
Primary references and product scope
Apple sources define macOS and hardware behavior. Smart Breeze behavior is checked against the signed release and its documented safety boundaries. Where a conclusion is an inference or a method, this guide labels it as such.
- Smart Breeze Build 22 known issuesSmart Breeze
- Smart Breeze compatibility and exact-model qualificationSmart Breeze
- Smart Breeze monitoring and control troubleshootingSmart Breeze
- Smart Breeze safety modelSmart Breeze
- Keep your Mac laptop within acceptable operating temperaturesApple Support
Monitoring-only cohort
Help test fanless sensor compatibility
Owners of fanless Apple-silicon Macs can join a read-only test plan. It never installs the fan helper or enables fan control.