NSPanel Pro V4.x.x Beta Test Application Tool Now Open

I apologize that this issue has affected your usage. You can submit the NSPanelPro logs by following these steps: Top drop-down menu → Settings → About → Feedback → Submit. After that, please send me the device ID, and I will review it ASAP.

Feedback sent.

Hi, regarding the offline status displayed on NSPanelPro, this is a display error (the device is actually online). This issue will be fixed in version 4.4.0. For now, you can tap the card to enter the details page and control the device.

If you are unable to control the device or experience delays in control, this may be related to the MINI ZBRBS device. I will check with the SONOFF team to confirm.

Surely it’ll get fixed, but something else will fall apart or stray. With NSPanel Pro it all turns into an imitation game — everyone hits their marks, pretending the whole setup isn’t held together by optimism and tape.

1 Like

Hi, I tested nspp yesterday and it is very delayed. I turned on the lights by clicking on the icon. The icon did not respond for 2 seconds and then it responded.

Is there a delay when the actual state of the light changes?
Is your light a WiFi device or a Zigbee-type device? Are there delays when controlling other devices?
You can submit the logs, and I will help determine whether it’s a network issue or if the NSPanelPro needs optimization in terms of control.

There is a delay when changing state. I am using a Switchman M5 matter device.

Before diagnosing the delay, it’s important to clarify how your SwitchMan M5 is paired.
M5 can actually operate in two modes at the same time — as a standard Wi‑Fi eWeLink device and as a Matter device. Many users don’t realise this and unintentionally end up with a dual setup.

If your M5 is paired in dual mode (eWeLink + Matter), the NSPanel Pro will control it through the eWeLink layer, while the device also synchronises its state via Matter through an external Matter controller (Home Assistant, Google Nest Hub, Apple HomePod, etc.).
This dual‑stack configuration often introduces 1–2 seconds of delay, because NSPanel Pro does not have a native Matter controller and cannot talk to Matter devices directly.

If the M5 is paired only as a Wi‑Fi eWeLink device, control is usually much faster.
So the first step is to check whether your M5 is connected as eWeLink Wi‑Fi, as Matter, or in both modes simultaneously — because this completely changes how NSPanel Pro communicates with it and can easily explain the delay you’re seeing

I don’t know how it’s paired, I put it as a matter in iHost. And mspp, you installed it yourself.

If you added the M5 as a Matter device to iHost, then NSPanel Pro is not controlling it through Matter. NSPanel Pro has no native Matter controller, so it can only communicate with the M5 through the eWeLink (Wi‑Fi) layer. This means your setup is most likely dual‑stack:
• M5 paired as Matter → handled by iHost
• M5 also visible to NSPanel Pro through eWeLink (Wi‑Fi mode)

In such a configuration the device has to synchronise its state between Matter and eWeLink, and NSPanel Pro sends commands through the eWeLink path while the actual state comes from Matter via iHost. This cross‑sync between iHost and NSPanel Pro often causes exactly the 1–2 second delay you described.

To diagnose this properly, we need to know whether your M5 is paired only as Matter, only as eWeLink Wi‑Fi, or in both modes at the same time — because the behaviour is completely different depending on the mode. And if you’re asking for help on the forum, it really helps to provide these basic details up front, because ‘I don’t know’ makes troubleshooting much harder for everyone. Pardon me for being blunt.

Matter in iHost and in nspp across wi-fi.

Just to clarify — NSPanel Pro does not have a Matter controller, so it cannot control any Matter device directly.
If your M5 is added as Matter to iHost, then NSPanel Pro is still controlling it only through the eWeLink Wi‑Fi layer. This means your setup is dual‑stack (Matter in iHost + eWeLink in NSPanel Pro), and this cross‑sync is exactly what causes the delay.

I already know about this.

If you already knew that, then great — although your earlier messages suggested otherwise.
Just keep in mind that NSPanel Pro still can’t control Matter directly, so if your M5 is added as Matter to iHost, NSPanel Pro will always fall back to the eWeLink Wi‑Fi path.
That’s the whole reason behind the delay, regardless of the ‘already know’.

The water heater tends to be on a timer rather than a temperature sensor. I happen to have a temperature sensor on the tank but it isn’t normal. You could get a tap left dripping how water and the boiler continuously on. This is a bit like an open window but less obvious. If the boiler is either heating the house or heating the water it is on. A thermostat or water tank circuit typically opens a valve and when it is open it closes a circuit so the boiler gets a signal, so really all we need is a device to open two valves, one based on temperature and one based on a timer.

I just upgraded to 4.4.0 and I have lost connection with 90% of the Zigbee sensors (all Sonoff, both end devices and routers), only 5 devices out of 71 are connected.

I rebooted the units, power cycled the router devices with no luck. Anyone with the same issue after 4.4.0 upgrade from 4.3.3?

1 Like

This problem has been going on for several updates without success.

Right after the upgrade, some services will restart, causing sub-devices to temporarily disconnect. Within about 5 minutes after the restart, all sub-devices should gradually come back online.

For devices that remain offline, please try manually controlling the device (such as toggling its switch) at the device end and observe if it goes back online.

If your device remains offline for an extended period or its status changes are not synced, you can submit the NSPanelPro logs and send me the device ID separately.

Hi Milk,

I sent the feedback yesterday, device ID 100177c43b. Let me know if you can grab it or you want me to resent again. Devices still disconnected, and the few that are shown as connected in the app, cannot be controled (get “failed” when you try to switch them).

Thanks,

I just got my update I will let yall know how it runs in the morning…