Open A-Yaskevich opened 3 years ago
Hi!
Thanks for the feedback!
Will consider for future versions to change the temp readings from current API to probably powermetrics output directly..
Best!
MacBook Pro (Retina, 15-inch, Mid 2015) here running TBS Pro 2.10.2, seeing a similar issue, TBS temperature readings still seem completely unreliable. After a long sleep (10-12 hours) the app will always show some seemingly arbitrary 55-65C but restarting TBS will fix it and it will show the correct value (usually 70-80C, as reported by other apps). Have to restart the app every time I open my Mac if I want to see accurate temperatures.
Hey, I have a similar problem with my app. The app seems to display the CPU Proximity temperature and not the real CPU temperature after Macs Fan Control and Intel Power Gadget. The correct temperature is only displayed after you close the app and restart it. I hope this issue will be fixed with future updates. It's 2022 and the bug is still not fixed. There are posts from 2018 describing the same problem.
Hey, I have a similar problem with my app. The app seems to display the CPU Proximity temperature and not the real CPU temperature after Macs Fan Control and Intel Power Gadget. The correct temperature is only displayed after you close the app and restart it. I hope this issue will be fixed with future updates. It's 2022 and the bug is still not fixed. There are posts from 2018 describing the same problem.
I'm not sure that it's the best idea to use raw cpu core temperature, because it raises to 90C in a second. You will have constant switching of TB on and off. CPU Proximity is a nice sensor. But sure it will be great if we can choose sensor that can be used in the rule. BTW. Issue I was talking about in the first post is still here :)
issue still exists, and appologies, but for a paid piece of software having to restart the app after every wake is pretty annoying.
First of all, I know there is similar issue closed, but I face strange sensor behavior too (MBP 13 2020 10th gen, 10.15.7)
After some period of time (hours, days) and several wake-sleep counts (with no OS restart) TBS temperature sensor shows lower temperature than it used to show when OS was just restarted and several hours more.
Here is what I mean: After the OS restart and during the day (before putting machine to sleep) the TBS sensor shows exactly the same value as the output of:
sudo powermetrics --samplers smc | grep -i temp
which shows CPU die temperature, for example:CPU die temperature: 55.72 C
The next day, when machine wakes, the sensor shows lower temperature than expected and no longer matches 'sudo powermetrics --samplers smc | grep -i temp' command output, it's (TBS) value is typically 10C-15C degrees lower. For me (of course, I can be wrong), it seems that after some amount of time or after waking for some reason other sensor is used (like CPU Proximity), which is truly lower than CPU die.
The strange thing is that after the OS restart TBS sensor matches 'powermetrics --samplers smc' again, and shows expected values.
The problem for me is that I can't set temperature-based rule that turns off TB, because before sleeping it easily reaches threshold temperature and turns of TB, but next day it always stays lower (but the real temperature is the same as the day before) and never reaches threshold.
P.S. I know there is a lot of temperature influencers, but in this case load average, processes running, etc. are all the same. P.S2. Moreover, I've tested temperature sensors with redirecting 'yes' to /dev/null. Just after the restart and some minutes idling