I will add that in the application view, at the moment of the problem, the temperature that is to be reached is visible, e.g. 20 degrees, and the reading from the device, e.g. 23 degrees, and an icon that the heating is on despite the goal being achieved.
I recommend reporting it as a bug. I removed all the devices from NSPP and the heating is now controlled by iHost. What you are writing about happened several times and one day I had 33 degrees.
Iād like to add a use case that I havenāt seen mentioned here yet, because it highlights a gap in how the NSPanel Pro thermostat currently thinks about āa thermostat = one relayā.
In my house I have a multi-zone hydronic system powered by a Daikin heat pump. Each room/zone has two separate circuits:
-
Floor heating circuit (zone valve actuator in that room/zone)
-
Ceiling heating/cooling circuit (zone valve actuator in that room/zone)
But the pumps are not per room. There are only 2 circulators in the entire house:
-
One circulator for all floor heating
-
One circulator for all ceiling heating/cooling
So whenever any room needs floor circulation, the single floor circulator must run; and whenever any room needs ceiling circulation, the single ceiling circulator must run.
The core requirement is that the zone behavior is different in winter vs summer:
Winter / Heating mode
When a room needs heat, both emitters in that room should contribute (floor + ceiling). That means the thermostat logic must:
-
Open the floor valve for that zone
-
Open the ceiling valve for that zone
-
Turn on the floor circulator (global)
-
Turn on the ceiling circulator (global)
Stopping (setpoint reached or thermostat off) must reliably:
-
close that zoneās floor + ceiling valves
-
turn off the global circulators only if no other zones still need them
Summer / Cooling mode
In summer, cooling is done only via the ceiling. So a cooling demand in a zone should:
-
Open the ceiling valve for that zone
-
Turn on the ceiling circulator (global)
-
Ensure the floor valve for that zone stays closed
-
Ensure the floor circulator stays off (unless another zone is heating, but typically the whole system will be in cooling mode)
Stopping must:
-
close that zoneās ceiling valve
-
turn off the ceiling circulator only if no other zones still need ceiling cooling
Why this matters for the app/firmware
Most thermostat implementations assume:
1 sensor + 1 setpoint ā 1 output relay
My setup requires:
-
1 zone thermostat controls multiple outputs (two valves)
-
plus shared/global outputs (two pumps) that must be driven by āany zone calls for itā (OR logic)
In other words:
-
Zone valves are controlled per-room
-
Pumps are controlled centrally based on aggregated demand:
-
floor_pump = ANY(zone_heating_requested)
-
ceiling_pump = ANY(zone_heating_requested OR zone_cooling_requested) depending on season/mode
-
Iām sharing this because if NSPanel Pro supports mode-dependent multi-output zones plus global āany demandā pump control, it would cover a lot of real hydronic installs (and avoid the kinds of āthermostat icon off but relay/pump still onā issues people are seeing).
Hello, I am aware of this issue, I hope, and in this forum I have emphasized several times that it is absolutely necessary to be able to add more devices to run.
This is a big post, I remind you of the fundamental thing I mentioned here. Even from my drawing it is clear that when it is to start heating, it must be able to turn on more devices, such as opening the servo valve and turning on the pump. But please do not limit it to only 2 devices that can be added.
Sorry for the issue. Please submit a log on the NSPanel Pro device through Top drop-down menu -> Settings -> About -> Feedback -> Submit. The best timing is right after you notice the error.
Donāt worry, I understand your use case, and I believe our new design get it covered.
Thank you very much for your detailed description of your use case. I learned a lot from it.
From my perspective, itās better to separate Central Heating and Central Cooling, otherwise the system would be too complicated to understand.
Regarding your need of floor heating and ceiling heating, I think we could treat them as two seperate Centrol Heating system but share the same set of thermal meters (temperature sensors). So the setup could be:
Central Heating One (Floor):
- One relay to control global floor circulator
- Room A
- Temperature sensor A_T linked to relay A_R_Floor which control floor valve actuator
- Room B
- Temperature sensor B_T linked to relay B_R_Floor which control floor valve actuator
- Room C
- Temperature sensor C_T linked to relay C_R_Floor which control floor valve actuator
- etc.
Central Heating Two (Ceiling):
- One relay to control global ceiling circulator
- Room A
- Temperature sensor A_T linked to relay A_R_Ceiling which control ceiling valve actuator
- Room B
- Temperature sensor B_T linked to relay B_R_Ceiling which control ceiling valve actuator
- Room C
- Temperature sensor C_T linked to relay C_R_Ceiling which control ceiling valve actuator
- etc.
The first picture I posted here is the same situation as described here, only the difference is that it has two circuits, one in the floor and one in the ceiling. Otherwise, itās exactly the same.
Same hereā¦
Even after disabling the termostat, it still interferred with scenes I use instead. So I had to change actuator to device I do not use at all through winter. So, be carefull.
I moved the heating control to iHost. It is currently risky to let nspp control the heating because it sometimes heats even when it doesnāt need to.
also @vodkon
We will optimize existing Single Room Heating solution after we release Central Heating solution. The current Single Room Heating solution uses the same underlying technology as Scene which is not optimal.
I also believe that many existing users who need a heating solution will find out Central Heating is better for their use case.
Do you have something like a closed loop for testers? I can try it on my heater before you release it.
Great, thank you, weād love to. Please allow us 2~3 weeks to prepare it.
Do you have time. I just want to help.
428 / 5 000
Before the update it seemed to work correctly (like on the classic nspanel without pro) but on new software versions, even on 3.X, there was an error as if the thermostat task/control stopped working, as if nspanel stopped controlling the temperature even though the status indicated that it was working, it did not change the device status, resetting the device or just turning off and on the automatic thermostat mode fixes the problem temporarily
I would also be happy to help test it.
On a couple of occasions, after Iāve manually turned off the relay (by tapping the card on the NS Panel), mine has also failed to start heating when it should.
This fixed it for me too. It seems that turning off the relay manually may stop the automatic thermostat mode, but the NS Panel still shows the automatic mode as being active.
Iām sorry you encountered this issue. Could you provide more details about the specific circumstances of the problem (screenshots or videos from the app), the exact time it occurred, and promptly submit feedback logs from both the app and the NSPanel Pro after the problem happens?
Please send me your Device ID separately. We will work to locate the issue as soon as possible.
Will this allow us to pair a single SNZB-02P with a single TRVZB as a thermostat? I installed two TRVZB devices yesterday, and aside from the scheduling issue (TRVZB schedules not working), I also noticed that I canāt assign the TRVZB as an Actuator in either the NSPanel Proās Thermostat interface or the Thermo Plugin in eWeLink. I assume this might be by design since the TRVZB widget does the same, but it would be great if even this simple setup could benefit from the improved UI and dedicated full-screen page for Thermostat on the NSPanel Pro.
For context: We live in a large apartment with five heated rooms. The building is supplied by a centralized district heating system, and each room in every apartment simply has a radiator with its own valve. I believe this would fall under Single Room Heating. Where I live, this type of heating setup is very common.
Will this allow us to pair a single SNZB-02P with a single TRVZB as a thermostat
SONOFFās TRVZB itself supports external thermometer, such as SNZB-02P, SNZB-02D, SNZB-02WD, etc., as the temperature source. So you donāt need Thermo Plugin in eWeLink App or Thermostat of NSPanel Pro to pair a single SNZB-02P with a single TRVZB as a thermostat.
