What happened

The 1.5.23 release notes list these changes:

  • Fixed CPU core sensors showing a wrong fixed temperature while their cluster is idle on M2 Pro, M2 Max and M2 Ultra, M3, M3 Pro and M3 Max, and M4 Pro and M4 Max Macs. The notes say this also skewed CPU Core Average and sensor-based fan control.
  • Fixed performance core sensors on M4 Pro and M4 Max, M3 Max, and M5 Pro and M5 Max Macs.
  • Fixed GPU Cluster temperature sensors on M4 Macs.
  • Added CPU core and GPU temperature sensors for the M5 Ultra Mac Studio.
  • Added enclosure and power supply temperature sensors for the M4 Pro Mac mini.

Read the release listing here

CrystalIDEA lists 1.5.23 as the latest version on its support page: crystalidea.com/macs-fan-control/support

What this means for your Mac's thermals

A fan curve is only as good as the number it follows.

Most Macs report many CPU core sensors, not one CPU temperature. Tools often combine them into an average so the fan reacts to the chip as a whole instead of chasing one hot core. That is a sensible design, until one input stops telling the truth.

If an idle cluster reports a fixed value, three things can go wrong:

  1. The average is pulled toward the stuck value, so it reads too high or too low for the work the Mac is actually doing.
  2. A sensor-based fan rule fires at the wrong time. Fans can start early for no load, or start late because the average never crossed the threshold you set.
  3. The reading looks stable, so nothing appears broken. A missing sensor is obvious. A stuck sensor hides in plain sight.

This is not a claim that every Mac on the list showed the bug, or that any other fan app, including Smart Breeze, had the same bug. The release notes describe a Macs Fan Control fix. The wider lesson applies to any tool that builds a curve on an average: check the inputs before you trust the output.

How to spot a stuck reading

Try this check on your own Mac. It takes about ten minutes and needs no load test software.

  1. Open your temperature monitor and show the individual CPU core sensors, not only the average.
  2. Leave the Mac idle for a few minutes. Note any core that sits at exactly one value while its neighbours drift up and down by a degree or two.
  3. Open a few apps or a busy web page and watch again. A healthy sensor moves. A stuck sensor stays pinned until its cluster wakes up, then jumps.
  4. Compare the average against the individual cores. If the average is flat while most cores are moving, one input may be dragging it.
  5. Update your fan control app before you retune a curve. A curve built on bad data will still be wrong after you move the points.

If a sensor never appears at all, that is a different problem. Read our guide to missing readings here

Practical takeaways

  • Update first, tune second. If you use Macs Fan Control on an M2 Pro, M2 Max, M2 Ultra, M3, M3 Pro, M3 Max, M4 Pro or M4 Max Mac, move to 1.5.23 before you judge your current curve.
  • Watch individual cores for a week after any major app or macOS update. Sensor mappings change as new chips arrive, as the new M5 Ultra Mac Studio and M4 Pro Mac mini sensors in this release show.
  • Pick your curve sensor on purpose. Our guide explains when to use a single sensor, the highest core, or an average: Which Mac temperature sensor should control a fan curve?
  • Learn what a normal reading looks like on your model before you call a reading wrong: How to check Mac temperature and keep the reading honest
  • Do not pin fans to a fixed speed to work around a reading you do not trust. Fix the reading, then let a curve do its job.

Sources

Sources

Free monitoring shows temperatures and fan activity from the menu bar, so you can spot a reading that never moves. Download Smart Breeze