# The thermostat is a disaster **URL:** \ **Category:** NSPanel Pro\ **Created:** [October 3, 2026, 3:49pm UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323 "2026-10-03T15:49:26Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [October 3, 2026, 3:49pm UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/1 "2026-10-03T15:49:26Z")
How is it possible that they can’t make a simple thermostat that turns the heating on or off when the target temperature is reached? This malfunctioning thermostat is a never-ending saga. An example of how much energy that endless mistake of theirs cost me. ![Screenshot_20261003-173913_FusionSolar](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/7/7b069beeb3e0bcc5078f05bafec0d744c86d9502.png) Log files showing the disaster in action. ![Screenshot_20261003-174047_Moto App Launcher](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/5/53e3d5e8e74472716adb52d0aaf36406dbb5b7a5.png) ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 4, 2026, 4:33am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/2 "2026-10-04T04:33:26Z")
The energy statistics show a series of regular drops in the green “Spotrebované z fotovoltiky” curve around midday and in the afternoon, from approximately 3–3.5 kW to 1–1.2 kW. This suggests that a load of roughly 2 kW is being switched on and off repeatedly. The graph itself does not establish that this is the heating load, although the correlation with the reported issue is worth investigating. What I find particularly interesting is the log around 17:14, where two different types of entries appear: Zariadenie spustené → ON/OFF [j\*\*\*\*s@azet.sk](mailto:j **** s@azet.sk) spustené → ON/OFF Do these entries represent two different sources of commands or triggers? What exactly does each type of entry mean? I think establishing this is important before concluding that the thermostat itself is responsible for the repeated switching. ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [October 4, 2026, 6:28am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/3 "2026-10-04T06:28:20Z")
The heating turned on at midnight and stayed on until I manually switched it off. These commands are executing on their own, without any input from me. I’ve identified one of the reasons why the heating doesn’t turn off. The NSPP can switch the heating on, but pressing the “Disable” button on the thermostat does nothing. That button is non-functional; even when the target temperature is exceeded and the display indicates that heating is off, the actual heating system remains active. He simply turns on the heating but is unable to turn it off. J ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 4, 2026, 7:42am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/4 "2026-10-04T07:42:56Z")
That clarifies the problem considerably. The unexpected activation and the failure to switch the heating off should probably be treated as two separate issues. The second one is particularly clear: if Disable changes the thermostat state to off while the actual heating remains on, that gives a specific and reproducible case to investigate. ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [October 4, 2026, 11:57am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/5 "2026-10-04T11:57:51Z")
From my perspective, these are schoolgirl errors. ---
**Author:** ![ashh](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@ashh](https://forum.ewelink.cc/u/ashh)\ **Post date:** [October 7, 2026, 11:40am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/6 "2026-10-07T11:40:52Z")
This is very concerning. I have recently bought several NSPanel primarily as a thermostat interface in each room. They will be controlling both AC and UFH. If this is not rectified soon it’s going to cost a lot of people a lot of money in addition to discomfort. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 7, 2026, 11:53am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/7 "2026-10-07T11:53:23Z")
Perhaps now that the holiday break is over, the SONOFF/eWeLink team could take a look at this and let us know what they think? After having some time to relax and recharge, perhaps a fresh perspective will help. 😉 ---
**Author:** ![Milk](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/milk/32/8679_2.png) [@Milk](https://forum.ewelink.cc/u/Milk)\ **Post date:** [October 8, 2026, 7:09am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/8 "2026-10-08T07:09:42Z")
When the target temperature is reached, the thermostat will turn off the controlled device. The thermostat itself will remain active, because it still needs to monitor the current temperature and decide whether the device should be turned on again. Also, if the target temperature has not yet been reached, the thermostat may automatically turn the device back on even if you manually turn the device off. This is expected behavior. In your current case, has the target temperature already been reached, but the device still does not turn off? Are you using the old thermostat or the central thermostat? If possible, could you also send me screenshots of your current thermostat settings so I can take a closer look? ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [October 8, 2026, 4:40pm UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/9 "2026-10-08T16:40:42Z")
In my opinion, the expected behavior is that when I turn off the thermostat, the heating stops—not that it keeps heating anyway. It keeps heating after reaching the target temperature; the room is supposed to be 18 degrees, not 30+. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 8, 2026, 8:35pm UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/10 "2026-10-08T20:35:22Z")
> [@Milk](#): > > take a closer look I think the key point is to distinguish between the thermostat state, the command it sends, and the actual NSPP output state. If the thermostat shows **OFF** after pressing **Disable** , is the NSPP output also actually **OFF**? It would also be useful to clarify what the two log entries mean: `Zariadenie spustené → ON/OFF` `[user account] spustené → ON/OFF` Do they represent different sources of commands? > [@Jojkoba](#): > > it keeps heating anyway If we know who sent each ON/OFF command and what the NSPP output state was at that moment, the cause should be much easier to identify. ---
**Author:** ![Milk](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/milk/32/8679_2.png) [@Milk](https://forum.ewelink.cc/u/Milk)\ **Post date:** [October 9, 2026, 6:02am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/11 "2026-10-09T06:02:23Z")
If you’re using the old thermostat, I think we may have found the cause. There is a setting that determines what the controlled device should do after the thermostat is disabled or turned off. By default, this option is set to **Keep**. That would explain why the heating device continues to run even after you disable the thermostat. You can first check this setting. If it is currently set to **Keep Current State** , you can change it to **OFF** according to your needs. ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/2/2bd306626011ec75c7bfd69e90a6000936096d31.png) ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 9, 2026, 7:34am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/12 "2026-10-09T07:34:03Z")
> [@Milk](#): > > That would explain why I agree with @Milk. This setting seems to explain the behaviour quite well and is definitely worth checking before concluding that the thermostat is faulty. ---
**Author:** ![debreczeni1996](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@debreczeni1996](https://forum.ewelink.cc/u/debreczeni1996)\ **Post date:** [October 9, 2026, 6:18pm UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/13 "2026-10-09T18:18:01Z")
I don’t have an NSPanel Pro, but I can confirm they seem incapable of releasing a working thermostat. My experience with the regular NSPanel thermostat feature was terrible, and now that I just got the TP-WGZBA, the experience so far is equally terrible. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 10, 2026, 3:29am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/14 "2026-10-10T03:29:36Z")
> [@debreczeni1996](#): > > I don’t have an NSPanel Pro, but I can confirm “ I don’t have an NSPanel Pro, but I can confirm…” is a bit like saying, “I’ve never seen a unicorn, but I can confirm they exist.” 😄 The NSPanel and NSPanel Pro are quite different animals, despite their similar names and appearance. Experience with the thermostat feature on one doesn’t automatically establish that the other has the same problems. Perhaps we should distinguish between the products before declaring that something is f\*cked up. ---
**Author:** ![debreczeni1996](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@debreczeni1996](https://forum.ewelink.cc/u/debreczeni1996)\ **Post date:** [October 10, 2026, 6:41am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/15 "2026-10-10T06:41:05Z")
I’m aware of the differences between the devices, but that doesn’t change the fact that they haven’t been able to make a simple thermostat feature work as it should—especially considering they’ve had it available across multiple devices for years now. I’m happy for your unicorn. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [October 10, 2026, 7:34am UTC](https://forum.ewelink.cc/t/the-thermostat-is-a-disaster/209323/16 "2026-10-10T07:34:27Z")
> [@debreczeni1996](#): > > especially considering The unicorn was just an illustration of the difference between firsthand experience and confirmation. 😁 You may well be right about the thermostat implementation across their product range. But that’s a broader claim than confirming that a device you don’t own has the same flaws. Those are two different things.