CPU Temp. Reading -1º on macOS Big Sur

[WatEvsCevs]

Describe the bug🐛 CPU Temp is reading -1º.

To Reproduce Steps to reproduce the behaviour:

1. Open iGlance
2. Look at CPU Temp.

Expected behaviour Reports the current temperature status of the CPU.

Screenshots (Optional)

Desktop (please complete the following information):

• MacOS Version: 11.0 Beta [20A5384c]
• Version of the app: 2.1

Log io.github.iglance.iGlance 2020-10-06--05-00-03-372.log

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.98. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[D0miH]

Hey @WatEvsCevs, thanks for your bug report. This is very strange. Unfortunately I can't install the Big Sur beta on my machine at the moment. Can others confirm this bug?

[edwardbattistini]

it is actually working for me on latest public beta. This is my MacBook Pro config

[edwardbattistini]

@WatEvsCevs can you reboot and check if the issue is still happening for you?

[WatEvsCevs]

@edwardbattistini And what do you know, turning it off and on again worked. It was weird because when I opened my laptop iGlance had that weird -1º issue (even when updated with the latest version).

Looking through the logs I found this:

20-10-06 16:14:05:587 Error: [CpuInfo:72]: An unknown error occurred

It must be something to do with macOS Big Sur and how that particular process was mucking up before the restart. It seems that Big Sur in general has troubles waking up from sleep.

[edwardbattistini]

@edwardbattistini And what do you know, turning it off and on again worked. It was weird because when I opened my laptop iGlance had that weird -1º issue (even when updated with the latest version).

Looking through the logs I found this:

20-10-06 16:14:05:587 Error: [CpuInfo:72]: An unknown error occurred

It must be something to do with macOS Big Sur and how that particular process was mucking up before the restart. It seems that Big Sur in general has troubles waking up from sleep.

Big Sur is not yet in GM so its kind of ok. We can always check again when its officially out

[D0miH]

And what do you know, turning it off and on again worked.

Glad to hear that! 🎉

Big Sur is not yet in GM so its kind of ok.

Exactly. However, I will add the error message to the log in the next update. This will help to track down the issue if it reappearing.

[Keating950]

Hi all,

I'm noticing this issue appearing on my new M1 Mac Mini running MacOS 11.0.1. It also reports that my fan is running at 1700 RPM, even though the fan is not engaged. Unlike with WatEvsCevs, this wasn't fixed by a reboot.

[D0miH]

Hey @Keating950, at the moment the app is not optimised for M1 Macs. As far as I can see from googling the issue is that some of the values we are trying to read changed on the M1 Macs. I will have to investigate this and will come back to you.

[simonepignotti]

Hi, I have the same issue on an M1 Macbook Air. I believe the problem is that by running through rosetta 2 the processor that is detected is a virtual one (see screenshot from the dashboard).

[tvhung83]

Same issue on mac mini M1 (BigSur 11.2):

[dontcrash]

Same issue here, might try and look through the source and attempt to fix this issue if possible, any pointers on where would be a good starting point?

[D0miH]

Hey @dontcrash, that would be awesome. So I think the problem with the M1 macs is that the SMC (System Management Controller) key which we are using for reading the temperatures (and other things) changed for the M1 models. So a good starting point would be to find out if other open source apps managed to get the correct key.

[ChillarAnand]

Yes, your are right. @dontcrash

$ sudo powermetrics --samplers smc |grep -i "CPU die temperature"

Password:
powermetrics: unrecognized sampler: smc

Looks like it is issue with smc.

[ChillarAnand]

Have checked other software like glances, osx-cpu-temp, iStats. None of them seem to be working.

Relevant links: https://github.com/lavoiesl/osx-cpu-temp/issues/38 https://github.com/Chris911/iStats/issues/101 https://apple.stackexchange.com/questions/54329/can-i-get-the-cpu-temperature-and-fan-speed-from-the-command-line-in-os-x

[bassu]

The stats app does not have this issue. They use another version of SMC though:

https://github.com/exelban/stats/blob/master/SMC/smc.swift

Implementation details here: https://github.com/fermion-star/apple_sensors

[pavelnemirovsky]

stats show fans rpm equal to 0... same a iglance ...

[nathanneuro]

https://github.com/macmade/Hot/commit/005e4ce22dc394cbfb6db91bdc8ddf1ac66d60c1 The open source app "hot" has fixed the m1 chip temp reading. Here's the link to the commit that fixed it for them.

[h3n4l]

Same apperance on my mac(Monterey 12.1, m1 silicon), iGlance version 2.1 !_

[Skylinar]

Bug is still here with M1Pro Mac 2021 on Monterey 12.2.1 (21D62)

[rmortes]

Can confirm on MacBook Air (M1, 2020) on Monterey

[Uniowl]

Same issue on MacBook Air M2, 2022 (Ventura 13.1)

[sukhmel]

Same on MacBook Pro (M1, 2021) on Monterey 12.6.3

[frakman1]

Same on MacBook Pro M1 Max on Ventura 13.1 Beta