That’s great, I just didn’t find out whether NSPP has local settings and operations available to the user to what extent.that’s great that the 4.5.0 update is available. I just didn’t find out if NSPP has to what extent local settings and operations available to the user.
I assume that NSPP 80 will have an update available later?
Does the latest release overcome the problems of the panel and zigbee devices going offline. After many months of reliable builds I despair at V4.4.6. My NSPP and linked Zigbee devices go offline on an almost daily if not more frequent basis
My life is too short to spend it rebooting the NSPanel Pro
I have 51 devices in iHost and I don’t have everything paired yet. I hope they will come to their senses and allow to conveniently migrate all of them from iHost to NSPP and similar combinations. Otherwise, no one will ever force me to buy a newer gateway.
Hi @Jojkoba , not sure if they implemented local scenes yet. On beta firmware 4.5.0 i understand that the sub-devices can be paired directly to NSPanel Pro, without the need of using the eWeLink app.
Let me also explain the local functionality in detail:
In previous versions, when using the NSPanelPro, you had to go through some initial configuration after powering on, then scan a QR code to log into your eWeLink account before you could continue using it. With version 4.5.0, after the initial setup, you can directly add and control sub-devices on the screen itself (you can choose not to log in to your eWeLink account). This is the initial version of the local usage feature. In the upcoming version 4.6.0, we will equip it with a local web page that supports more local settings (such as creating local scenes, syncing Home Assistant devices, etc.). All related features will be gradually iterated in subsequent releases. We also look forward to hearing your suggestions for this feature.
First of all, this is great news, it will definitely be versatile and usable everywhere.
Major fixes for occasional Zigbee network outages.
So let’s move on to the suggestions from my side.
Alarm and notification improvements. We’ve already written about that.
I had the opportunity to test a central heating system, how is it possible that I can’t select more than one device to turn on? In certain cases, I need to open the servo valve and turn on the external pump (it didn’t allow me to do that). If I’m wrong, please tell me how it’s done.
The ability to turn off the delay in a scene before the delay ends itself. To finish in conditions such as the device is turned off or interference do this.
The logic of the central thermostat is to use the corresponding switch in each room to control the main switch of the home’s climate control system.
Each room can select its corresponding temperature source and execution device. It also supports creating multiple cards for the same room, with each card selecting a different execution device to achieve the result of controlling multiple devices.
First, select a main actuator, then choose the temperature source and corresponding switch for each room. The switch in each room affects the main switch. If all valves in every room are closed, the main pump will also be shut off.
Regarding scene cancellation: Are you referring to the delayed scenes in eWeLink? If so, editing or disabling the scene will interrupt its execution early.
This is specifically the situation I have set up irrigation to turn on the first valve and turn on the next valve in 5 minutes. In the meantime it starts to rain. Is that enough to fill the scene and will the timer also end? This is about CubeOS.