Repository navigation
No actual temperature display in the thermostat window. #386
Description
Hello
I tested the thermostat today after the update; the target temperature setting works fine, but the actual temperature shows as 0.0°.
I tried it using both the Sonoff NSPanel's internal temperature sensor and an external one integrated via OpenHAB.
The temperature display on the screensaver works perfectly.
I would also like to change "Room" to "Living Room".
Thanks
Activity
tpanajott commentedon Sep 20, 2026
Are you using Home Assistant or OpenHAB? The temperature that is supposed to be displayed on that window is the one reported back from the thermostat itself.
pationair commentedon Sep 20, 2026
Hello, I use openHAB to control a water-based underfloor heating system.
My temperature sensor is an Aqara Zigbee sensor.
I don't have a traditional thermostat on the heating system itself.
tpanajott commentedon Sep 20, 2026
Hmm, intresting. I've now good way to actually test OpenHAB on my setup and do it as a "best effort". What type of item have you added as the "OpenHAB target termperature item"? But as you said changing the target worked as expectedly it's simply not display the actual set point?
pationair commentedon Sep 20, 2026
I created a Number Item in openHAB to serve as the target temperature.
I set the target temperature using this item and switch Relay 1 on whenever that value falls below the actual temperature reported by the Aqara sensor.
I’ve linked these two temperatures in such a way that I can also query or adjust the settings via Alexa.
If it helps—and provided you’re reasonably familiar with openHAB—I can send you my two item files.
pationair commentedon Sep 20, 2026
The simplest solution would probably be to add an option to select the actual temperature during configuration.
After all, I can specify the target temperature as well.
tpanajott commentedon Sep 20, 2026
Yeah, I believe so too. Home Assistant reports both temperature and set point back. As it is currently the display is configured to simply display the set point but I will probably update is to that it can display either the set point or the current temperature.
Just a question, if you update the set point from OH does the NSPanel then pick up the new value?
tpanajott commentedon Sep 20, 2026
It's also a bit strange as looking at the code it should use the room temperature item (given you've selected one) and if you have not then it will use the internal thermistor to show the room temp. Having a valid of 0 is a bit strange. It could happen if you go to that page in the first 30 seconds after a panel reboot as it has not yet read a stable mean temperature from the thermistor.
pationair commentedon Sep 20, 2026
I think it would be good if it displayed both values—the target value and the actual value.
I remember seeing a picture of that somewhere here.
Regarding your question: yes, when I change the value in openHAB, it changes on the NSPanel too, though it seems to round it up. For instance, if I set it to 22.5 in openHAB, it changes to 23°.
If I tap 22.5 on the display, for example, it shows that for a brief moment, but then switches back to displaying 23—even though 22.5 is actually sent to openHAB.
I just rebooted it again; now the display shows the temperature from the internal sensor. Unfortunately, that sensor is very inaccurate and, in my case, located in a spot that gets too hot from the sun.
tpanajott commentedon Sep 20, 2026
Well, yes. Both are meant to be display. The large number beneath "Room" is supposed to be the current temperature and the smaller numbers beneath "Set" shows the current set temperature. I'm working on adding support for user choice in what is displayed as the current temperature.
Regarding the rounding, I think that might be because it's "22.5" and not "22,5". I'll try and fix that.
pationair commentedon Sep 20, 2026
That might be the source of the problem.
I also noticed that the screensaver screen always displays the value from the internal sensor; it would be better if it showed the value from the sensor I selected instead.
Thanks a lot for your great work.
tpanajott commentedon Sep 27, 2026
This should have a working solution now in the latest beta released today. Please report back if solved or not.