May I ask if you are referring to the device being repeatedly turned on and off by scenarios on January 20th? According to the screenshot, it appears to be triggered by the thermostat. It’s possible that your temperature control precision is set to 0.1, and frequent temperature changes are causing the device to repeatedly turn on and off. To better confirm the cause, you can promptly submit the logs from the NSPanel Pro, and I will work on identifying the issue as soon as possible.
Regarding the issue of the thermostat not heating, it could be a known problem we have identified. You can also submit the logs along with the specific time when the abnormality occurred, and I will verify it ASAP.
The central thermostat supports selecting Wi-Fi-enabled devices. May I ask what your trigger source is set to?
Revised Edit: Currently, the device needs to be synchronized to the NSPanelPro split-screen interface in order to be selectable when creating a central heating
OK, I will submit the logs as soon as I found out it happens again.
I will try to add the respective valve switches to the split screens of respective thermostat and test if it works.
To your first question - no, the device was not repeatedly turning on and off. The heating switch was turned on by the thermostat at the set time because the temperature in the room was about 1°C lower than set but immediately switched of by the “Time of Day Scene-condition” trigger which I have no idea where this comes from.
This is related to the thermostat setting—Selected Actuator State. When the thermostat finishes its automatic schedule or is disabled, it triggers the opening/closing of the device. The operation log for the device will display this notification.
OK, so in my case, the schedule ends, new schedule starts and then with some delay after the previous schedule ended, the Selected Actuator State turns off the heating.
In this case, I’ll set all the thermostats to “Keep”.
Hi, I’m asking you because I know you’re the brains behind central heating, so I hope you have a solution. Since the time change, the entire system activates with an hour’s delay. Even though I’ve reiterated the programming time for each valve, setting it to activate at 7:00 AM and deactivate at 10:00 AM, the system still turns on at 8:00 AM and off at 11:00 AM. Could you please give me some suggestions on how to solve the problem? Thanks.
Can I ask if it works and are you satisfied? I can’t really test it because NSPP hasn’t been working correctly for a long time and the connection between iHost and NSPP doesn’t work at all.
I’m very satisfied with this solution! Since I’ve been using it, this is the first problem I’ve encountered. Otherwise, everything’s working very well. I don’t use iHost because I don’t think it’s suitable for my needs at the moment.
I’m glad it works as it should. I had very unstable internet, that’s why I solved it like this. I’m not going to throw away a working device. As for your problem with time, you should contact technical support. Because I can’t say how they solved it.
So I thought I’d check the time zone to see if it’s set correctly.
It’s not so much the response times… it’s as if the valve scheduling is still running on the old time and doesn’t take daylight saving time into account. I reported it on eWeLink, but I’m finding that unlike before, the issues reported on eWeLink aren’t being addressed as quickly as before. It’s as if something has changed in eWeLink’s after-sales service.
I understand the problem but here the problem is clearly in the NSPP not in the central heating system. How about turning off the power and then turning it back.