After update of pihole to v6 the display of CPU temperature has gone. And so has the load average. It worked fine before so please reimplement it. It is extremely useful to monitor the raspberry’s and therefore pihole’s health. This is a regression.
Obviously, you did not read the release notes about version 6.
Excerpt from the link above:
Temperature no longer on the web interface
During the development of v6 – we took a decision to remove the temperature from the web interface. It was never consistently displayed on every user’s interface – sometimes we couldn’t get the correct sensor reading, and sometimes we couldn’t get a sensor reading at all. We would find ourselves spending a lot of time debugging issues with sensors for very little gain.
There are other tools that are better suited for monitoring servers and hardware in general, and really an ad-block DNS server is not the place for that. We kept the CPU and RAM usage stats because they are arguably much more meaningful to the operation of Pi-hole than knowing what the temperature is.
Some enterprising users have created web interface mods already to add the temperature back, and you’re more than welcome to run them, but keep in mind the standard Pi-hole upgrade process will stash any modified files on the web interface – so you’ll need to apply them again manually. (If anyone has ever used the speedtest mod – you’ll be used to this…)
You'll find an answer here but the script will be overwritten on each update.
https://www.reddit.com/r/pihole/s/4LmC5SDPR2
But the change is quite simple.
Hover over the CPU%.
But also see Fix CPU% by DL6ER · Pull Request #3262 · pi-hole/web · GitHub
This should be implemented either in 6.0.3 or 6.0.4 of the web interface.
It depends on Add total CPU % to /info/system endpoint by DL6ER · Pull Request #2297 · pi-hole/FTL · GitHub, which has not yet been approved
See above for temperature.
I wouldn't go that far
I do.
On my 3 piholes the temperature has been displayed consistently until you removed it. People who enjoyed the info and found it useful are now required to patch pihole, whenever there is an update. And if they don't patch it, they will have to get the info by taking additional steps. (e.g. ssh session -> padd.sh or cat /sys/....)
Either way, the convenience of having this info on the dashboard is gone. And with all due respect, you cannot decide whether this info is important to users or not.
I call this a regression.
You could have easily added an option with the default to not showing the temp.
Pull request always welcome!
1 Like
Yea, if it were still PHP, I'd go for it. But now, I pass.
With all due respect - we can make whatever changes we like, and we don't really owe anyone an explanation as to why we have or haven't done something.
That we provide a reasoning at all is a bonus - that not everyone likes that reasoning... is just life.
5 Likes
This info is still available via PADD if its that important to have it displayed. Wild levels of entitlement in this thread.
3 Likes
Of course you can. However, knowing that users actually found this info useful, makes you ignorant towards your user base. Basically, you are sending a big FU - take it or leave it.
Nope, not a regression in my books. A feature determined by the development team as non-essential, yes.
To me the tone of your responses to the development team of a essentially free piece of software, is more of a FU, than anything. That is my opinion, and that is all.
CPU temperature has nothing to do with the core functionality of Pi-hole. The fact that you were provided an invitation to implement the feature, and declined as it was no longer PHP, shows how really important the feature is to you.
6 Likes
Another one of those who can't deal with factual statements. Read my comments again. Did I attack someone personally? I said, if one ignores someone, it makes one ignorant. This is a fact.
Free software, yes, but I have donated since I use it daily. This doesn't give me the right to strongarm a dev into something, but I can at least state my opinion. If you don't like my opinion, feel free to ignore it.
Never said it did. Maybe read my previous comments more slowly.
I said people found it useful.
I really dislike people who don't read what I write and then complain about or comment on stuff I never wrote in the first place.
I have a patch (I found on reddit), which I apply after each update.
I am sorry that I am not familiar with the new code base and don't know how to create a setting which is then used in the templates. I would have known in PHP. But I don't have the time to learn the new code base and how to use lua.
Me too:
Seriously? I read it which prompted me to reply in the first place and state that people found it useful though. I also mentioned that it always worked on my 3 piholes (opposed to not working or not consistently working). It was also the reason why I said that this explanation is not the same as what users think in terms of importance (for them, not in general).
Let me explain: The reason for removing it is valid. However, for users, whose piholes displayed the temp correctly, it was a nice feature, which is now missed.
All I said was that the devs could have easily added an option with the default to not showing the temp, instead of just removing it.
I used the term "easily", because if one is familiar with the code base it takes probably less than 5 minutes to implement. For me looking into the new code base and into lua would take me at least a few hours.
PS.: I have unsubscribed from this topic, since it's not useful to me and I am just wasting my time.
1 Like
Seriously you want the devs to spend precious time on this instead of focusing on other more important core features?
Plus having to support this feature here on Discourse/Github with folks that have problems with the sensors.
2 Likes
No they could not have "easily" added the option back. They completely reworked the web code from php to C. The amount of QA and effort must have been tremendous.
The notion that "it's way easier for the devs to do it, so why should I?" is quite frankly ridiculous. If everyone thought that way, absolutely nothing would get done in this world.
The entire codebase is open-source, there is nothing stopping you from contributing your knowledge to the project to make it better for everyone. Maybe you'll even thank yourself later for learning something new.
2 Likes
Agree. It's always been a hanger-on. I recall it was originally put in as a troubleshooting aid, but CPU's rarely overheat and getting the temperature from the host OS to the dashboard is not always reliable. Lots of potential code for little benefit.
Similar to uptime - a potentially interesting bit of data, but should not be included in the Pi-hole dashboard, because it is unrelated to the core funcionality of Pi-hole.
3 Likes
I agree.
Most CPU's get clock throttled to prevent damage from heat.
This temperature throttling threshold differs between different pieces of HW.
So knowing the temperature still doesnt tell you allot.
A better indicator would be to know if the CPU is/was throttled like with Raspi's:
$ man vcgencmd
[..]
get_throttled
Returns the throttled state of the system.
But these sensors also differ between HW so coding for this can also be a bit tricky.
You need to invest in a better dictionary. That is a fact.
4 Likes
This is an endless discussion about a tiny patch as described on Reddit. It's as simple as that.
Nobody asks for a 100% compatibility for any temperature sensor except the raspberry pi ones.
Remember, this is a PI hole piece of software. If there are any struggles with container apps, it simply doesn't matter.
The golden path would be a selection of system Infos in the upper left corner but that's only my wish for a better User experience.