NS Panel Pro Thermostat problems

@str858 @Jojkoba @Stophammer @demonizator
Great news! We’re excited to announce the release of version v4.2.3

What’s New:
Central Heating in Settings is now available! This feature adds a dedicated screen on your NSPanel Pro, allowing for centralized control of heating across multiple rooms .

Go ahead and download the update to start exploring. We’d love to hear your feedback!

How to Update:

  1. Go to your NSPanel Pro.
  2. Navigate to Settings → About → Software Update .
  3. Check for and install the latest firmware.
2 Likes

Thank you, Jojo, just updated to this new version. Unfortunatelly, it still doesn’t work for my setup :confused:

As mentioned before, my home is supplied by a centralized district heating system. I have no local boiler, furnace, etc. to control, i.e. no smart switch to assign as Boiler actuator. Each of my rooms simply has a radiator with its own TRVZB.

For testing purposes, I still asigned one of my lights switches as the actuator and at first glance everything seems ok.

I completely understand that you’re targeting more complicated setups with this Thermostat solution, but it’d be great if the rest of us can also benefit from this dedicated screen listing multiple TRVZB in the above fashion - instead of using the (now) very unfunctional widgets. Or, redesign the TRVZB widgets to be as functional as the ones in the Thermostat screen.

I sent the log files with NSPP. I don’t know if it’s intentional or a mistake, but when I tried adding Mattermost with iHost, there were several NSPP restarts.

The restarts started between 16:30 and 16:50.

I would like to try it, but I can’t get to the matter bridge in iHOST, so I’m missing 48 devices in the panel and I can’t try anything with that pad.

First impressions are very positive and you can see a lot of work, I commend you.

For your heating system, I recommend an original thermostat. Centralized heating control is suitable for systems where it is necessary to additionally turn on, for example, the boiler, and then open, for example, a valve.

The thing is that the original Thermostat also behaves the same way - it requires an actuator to be set up.. Cannot set only the valves.. :confused:

I haven’t tried it, but if I understand it, they don’t allow you to open just the valve on the radiator, for example?

Do you have a similar situation but without external thermometers?

1 Like

You need to give comments and they will definitely fix it. My goal was to improve the multi-zone heating where it is necessary to turn on the electric boiler and open, for example, servo valves. I install this system very often and there are several of us who wanted the aforementioned solution.

So it’s good to try and give feedback for all options.

It’s exactly the same setup, several TRVZBs with external thermometers - SNZB-02Ps and SNZB-02Ds.

Currently, on the NSPP I use the TRVZBs device widgets and they do the job, but they lack the polished interface and usability of the dedicated Thermostat screen.

Absolutely! That’s why I mentioned this scenario before - it’s quite common in our region, so I’d expect many users to face similar issues. The team here has been excellent: highly engaged and proactive, already implementing so many suggestions, including some of mine. Big kudos to @MichaelLearnsToCode, @JoJo and everyone else involved.

Hello. After some limited testing, the multi-zone heating itself appears to work well, but I’ve made some observations.

  1. When setting up a room, I can choose either a temperature sensor (in my case already bound to a TRVZB) or a TRVZB as the thermometer. If I choose the temperature sensor, I can’t then choose the TRVZB as the valve actuator (see the pictures below), I thought this may be because the sensor is already bound to the TRVZB. If I choose the TRVZB as the thermometer, would it get the temperature from the TRVZB or its bound sensor?

  2. In my kitchen, I don’t have a sensor bound to the TRVZB, but my THR320D is in there with a temperature probe. I can choose the THR320D as the thermometer, but I still can’t choose the TRVZB as the valve actuator, even though the TRVZB isn’t bound to any sensors (see the pictures).

  3. I presume the new thermostat is getting the schedules for the TRVZBs from their smart schedules. Previously, I had the old thermostat linked to a temperature sensor in my hallway. I’ve added this as a room to the new thermostat (with no TRVZB) where I can set a heating schedule and a heat differential of as low as 0.1c. It would be nice if I could add my existing temperature sensors (currently bound to TRVZBs) as thermometers and choose the corresponding TRVZB as the valve actuator (possibly ignoring the smart schedule of the TRVZB), this way I could set everything up from the NSPanel rather than setting some schedules on the app and others on the panel. Or maybe add a smart schedule function to the temperature sensors in the app.

  4. When this gets to a release version, it might be an idea to add a note to the thermostat section in the app saying that there’s a more advanced version available on the panel itself and how to enable it, or remove the basic thermostat section from the app and have that on the panel as well. Also, I’d like to be able to move the new thermostat screen from the end of the list.

Overall, this is a great improvement, well done.

EDIT: It has occurred to me that the valve actuator might be intended to turn on additional pumps etc, rather than a TRVZB. If I choose a temperature sensor as a thermometer (and set a heating schedule and heat differential on the panel), how will the bound TRVZB know when to turn on or off, or would it rely on its smart schedules?

TRVZB is still unresolved. But I believe that Sonoff will fix it.

You can add a description so the user knows that it activates the advanced thermostat. The description should briefly explain what type of heating system it is intended for. There will certainly be cases where they activate this option even though it is not intended for their heating system.

Mine seem to be working well, but the new thermostat allows a heat differential down to 0.1c, and I’d like to use a differential lower than ±0.5c. A swing in temperature of 1c is sometimes too much.

Edit: Ignore this. I remembered the TRVZBs already allow a temperature accuracy down to 0.2c.

Is there any reason not to remove the original thermostat from the app, and just use the new thermostat on the panel?

Difference of one degree is too much a cold room and long heating are the consequences of that 1 degree. it should be suggested that they put a minimum value of 0.1 degree in the trvzb.

The new thermostat is not suitable for certain types of heating. That is why two thermostats are available.

The original thermostat is suitable for apartment units that have a common boiler room. For example, for controlling electric heaters, controlling servo valves on radiators.

The new thermostat is suitable for solutions that have their own boiler room. and it is necessary, for example, to start the heat pump and open the servo valve in the distributor. It can independently control multiple zones on different floors.

How does an old thermostat work ( the heating that’s all it allows ):

1, the temperature drops

2, open the valve or turn on the heater

3, it warms up the room it turns off

How do newer thermostats work:

1, the temperature drops

2, the distributor opens the corresponding servo valve

3, it turns on the heat pump, electric boiler, circulation pump, etc…

4, it warms up the room it turns off everything it turned on

A clear example of my house. I need to turn on the heat pump and open the servo valve on the 1st floor for the guest room. And I also need to open the servo valve on the ground floor for heating the hallway. This control is not possible on the original thermostat. Because the original thermostat allows the valve to open when the room temperature drops, but if it does not turn on the heat pump, it will not heat.

My personal opinion is that chose the right approach. If they wanted to merge the two thermostats into one, they would make it very complicated.

at first glance there are not many differences but in your own boiler room where you need to turn on a dry contact the original thermostat will no.t work. a thermostat is a heating control.

Perhaps I’m mistaken, but in the new panel thermostat (select actuator>select room>select thermometer), selecting the room is the only additional step over the app thermostat (select actuator>select thermometer). This seems less complicated than having two thermostats, one in the app and one in the panel.

100250da2d

Merci

Thank you very much for testing Central Heating System.

When setting up a room, I can choose either a temperature sensor (in my case already bound to a TRVZB) or a TRVZB as the thermometer. If I choose the temperature sensor, I can’t then choose the TRVZB as the valve actuator (see the pictures below), I thought this may be because the sensor is already bound to the TRVZB. If I choose the TRVZB as the thermometer, would it get the temperature from the TRVZB or its bound sensor?

The TRV itself is a kind of thermostat. It has built-in temperature sensor and built-in actuator to control the valve. If you link an external temperature sensor to TRV, then the two together form a thermostat.

So for a room already managed by TRV, just choose TRV as the thermometer and it’s enough. The Central Heating System will link TRV’s status to bolier actuator. For example, if TRV goes into Heating state, then bolier actuator will be turned on.

Maybe choose TRV as the thermometer will create a confusion? Should we just list TRV as a separate option for room, alongside with Termometer and Valve actuator? Or we should put TRV in Valve actuator option instead of Termometer optoion?

I presume the new thermostat is getting the schedules for the TRVZBs from their smart schedules.

TRVZBs have their own schedules and they are different from the schedules of the Central Heating System. If you choose TRV for a specific room, then you continue to use TRV to control that room, I mean TRV has its own device page on eWeLink App and device tile on NSPanel Pro. You just need to link a TRV for a room in Central Heating System.

When this gets to a release version, it might be an idea to add a note to the thermostat section in the app saying that there’s a more advanced version available on the panel itself and how to enable it

eWeLink App will provide a management portal for Central Heating System. eWeLink App has its own release schedule, and this Central Heating System couldn’t wait for it. So we just provide the Central Heating System option on NSPanel Pro this time.

remove the basic thermostat section from the app and have that on the panel as well.

We plan to optimize the existing basic thermostat after we do Central Heating System right. We will definitely take your suggestion into consideration.

Also, I’d like to be able to move the new thermostat screen from the end of the list.

Got it. It shall be done.

Yes, and we are working on it. TRVZB will get some optimizations in v4.3.0.

Great, thank you. Can’t wait for the v4.3.0 update now - so many features and fixes that I care about. Thank you!

Hi, your device has been assigned version 4.2.3. Please check and install the new version, and feel free to contact me if you encounter any issues.

1 Like