Unavailable can describe three different boundaries

Unavailable can describe three different boundaries: reference table
PatternLikely boundaryMeaning
One category is unavailableKnown keys for that aggregate were not readableOther categories may still provide live monitoring
Selected category falls backRequested input is absent but another live input existsUse is possible only when the fallback is clearly labeled
Every category and Hottest are unavailableThe hardware snapshot or discovery path produced no usable temperatureDo not make temperature-based control decisions
Value appears but never refreshesFreshness or transport may be brokenTreat stale data as unavailable for control

Run the safe monitoring checklist

  1. Confirm Smart Breeze version 1.0.0 Build 37, the exact model identifier, and macOS version/build.
  2. Choose Any Sensor and note whether a fallback label appears.
  3. Start an ordinary known workload and verify whether any category updates.
  4. Restart once, reopen the canonical copy in /Applications, and repeat the read-only observation.
  5. 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 37 status on the tested M5 MacBook Air

WarningAll temperature categories remain unavailable

On one tested fanless M5 MacBook Air, Build 21 downloads and installs, but its snapshot stops after the Mac does not expose the FNum fan-count key. Model, CPU, GPU, Memory, Battery, and Hottest remain unavailable instead of continuing to independent temperature-key discovery.

Build 37 now treats missing FNum as an explicit unknown fan topology, keeps fan control ineligible, and continues read-only temperature discovery into the new Thermal Sensors explorer. This path has been verified on that M5 Air.

The lack of a fan is expected for this Mac. Build 21's monitoring failure was not. Build 37's temperature discovery has been verified on the M5 Air.

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 37 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 fan-control hardware discovery.

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.

MethodKeep sensitive identifiers out

The model identifier is useful; a serial number, hardware UUID, Apple ID, administrator password, and personal files are not. Send only what the compatibility investigation needs.

Sources

Related docs: Read the dated M5 Air issue, Interpret unavailable categories

Fanless Macs get full temperature monitoring and the sensor explorer. No fan helper, no fan controls. Download Smart Breeze