[Feature Request] CPU Temperature on GL.iNet Mobile app (Android)

Hello,

I would kindly ask for the feature to show the CPU Temperature on GL.iNet Mobile app (Android) to be considered, same as we get it on the website version. I am not sure the iPhone version of the App has this feature or not.

Would also be nice to have more information like the other sensors temperatures that you can get from LuCI + Plugins.

Thanks a lot for your consideration.

Hi

This feature has been implemented. You can find it under System - System Overview.


Does not show on mine. Flint2. Android App

Could you please let us know the current firmware version of the Flint 2 and the version of the Android app?

Sure

We have reproduced the issue on MT6000 v4.8.3 and will confirm with the R&D team.
Your version appears to be op24? Please verify this under System - Upgrade so we can request the R&D team to investigate accordingly.

Thanks a lot for looking into this.

Indeed, I'm using the op24 version.

But I remember I had the same issue when I was using the Stable 4.8.3 version.

OK, thank you for your report.
We have already requested the R&D team to investigate and fix.

1 Like

Latest beta of the app added the requested feature.

Thank you!

1 Like

@will.qiu Hello again.

Latest version of the app removed the feature again

After discussing with the product manager, we have a udpate on this.

Following a recent policy review, we have established a new standard for our interface: temperature will now be displayed in the GL.iNet Web UI and App only for devices equipped with an internal fan. This allows users to monitor thermal performance and adjust fan profiles accordingly.

Since the MT6000 is a fanless, passively cooled device, temperature information will be removed from its future firmware and App versions. This decision was made to prevent potential misunderstanding among our broader user base regarding normal operating temperatures.

For Advanced Users: If you wish to continue monitoring system temperatures, this data remains accessible through the LuCI interface by installing the relevant system plugins.

We appreciate your understanding.

@will.qiu

I really don`t understand this decision and I think is counterproductive. Instead of giving us more options they are removed?

If I want to check when I`m away from home how my device is behaving I have to open Goodcloud, log in … then open luci and then check? Instead of the App showing me straight away ?

What confusion? The button to set the fan speed is NOT there anyway on passively cooled devices.

I would ask for the product manager to reconsider this.

This is Goodcloud + Luci causing this:

Tue Feb 10 19:31:17 2026 daemon.info procd: Instance uhttpd::instance1 s in a crash loop 6 crashes, 124 seconds since last crash
Tue Feb 10 19:32:25 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:25 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:25 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:25 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:25 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:29 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:29 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:29 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:29 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:31 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:31 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:31 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:31 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:33 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:33 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:33 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:33 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:33 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:33 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:36 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:36 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:37 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:37 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:38 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:39 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:39 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused
Tue Feb 10 19:32:39 2026 daemon.err rtty: (net.c:95) connect '127.0.0.1:8443' failed: Connection refused

Luckily. I had remote SSH access and I could reboot uhttpd and nginx.

We have discussed your concern with the product manager. However, considering the number of customer reports related to misunderstandings about temperature (where the device was operating within a normal temperature range, but users were concerned because it felt warm to the touch or showed a "relatively high" CPU temperature), this decision was made.


Regarding the issue of accessing LuCI via GoodCloud:

  1. Could you please confirm whether you have made any changes to the uhttpd configuration?
  2. Please export the logs after the issue occurred and send it to us via private message.