NSPanel Pro v4.1.0 Release: New Features & Enhancements

NSPanel Pro
63

My ns panel pro 120 had warned me of the update to 4.x. Once the update was finished, nothing changed and in the about tab it gives me version OS 3.12.0 and app version 3.12.0. And if I check the updates again it says they are on the latest version

1 Like
64

Hi, buyed a NspanelPro and still stuck on 3.12.0 FW. I tryed the screen saver trick and restart more times but without change, my ID is 1002375ebb

65

Hello Sonoff team,

i’m new owner of NSPANEL120PW, adding the FDroid support to use official H-A app, was the jump in for me.

1st, I will say big thank you, to enable the acces to “Advanced setting” to help to manage easily the device.

this one permit me to :

  • modify the “Display size” to small to provide more information on small screen
  • enable the “show status bar” than is more “navigation bar” to enable right “android button” for easily navigate between setting and app in device.
  • Enable the adaptive brightness, don’t know if needed or not

MobaXterm_Personal_25.3_Z6z0DETYQD

One idea for me, is to use the “status (navigation) bar “ as normal usage instead your button floater.

but need to allow to autohide the navigation bar in setting, i think we can by ADB but not tested.

Sure, for Ewelink app, the navigation bar, must be fully hidded

On Home Assistant, the “Fullscreen” option auto hide this one, but the reserved area is not used by app. or maybe due to depreciated API since Android 11 or not compatible with Android 8.

the navigation bar is displayed by gesture on right edge of screen manually

MobaXterm_Personal_25.3_KezUwmLfji

For user, i can recommend to move on alternative keyboard ( Simple Keyboard for me ) where height can be set.

MobaXterm_Personal_25.3_tYrSjwgW0c

About Zigbee :

i have Ihost used as local Docker server for Z2M and MQTT server

NSPANEL is used as “router”, but this setting (switch between coordinator or router ) can be only set in App Ewelink, and must available in device too.

Issue :

the navigation bar can be buggy few times, and only HOME button is available, but not work fine.

Tools used :

for remote acces : DroidVNC ( device ) and MobaXterm (PC )

for DroidVNC, think to disable “start on boot”, when back to Ewelink app, the “pointer” is disable to the fly.

1 Like
66

Follow these steps to join the Beta Test program:

  1. Visit the tool page: NSPanel Pro Beta Testing Program
  2. Log in using your eWeLink account.
  3. Select the NSPanel Pro device you wish to register.
  4. Read and accept the risk notice, then submit your application.
  5. Wait approximately 5 minutes, then go to your device’s Settings -> About -> Software Update to check for the latest firmware and install it.
67

Thank you

68

Thank you very much for using NSPanel Pro and sharing your experience.

One idea for me, is to use the “status (navigation) bar “ as normal usage instead your button floater.

but need to allow to autohide the navigation bar in setting, i think we can by ADB but not tested.

I fully understand your point. Due to the limitations of the underlying Android 8.1 OS which doesn’t provide system-level Fullscreen Gesture support, we have to implement the AssistiveTouch feature (the translucent circular button, which will shrink to a semi-circular arc attached to the edge of the screen) which enables users to go back to NSPanelPro App.

We plan to improve AssistiveTouch in v4.2.0 by:

  1. Support Double Press action: works as the same as the Overview button of the system Navigation Bar, so it can be used to switch between running apps. We call this feature App Switcher.
  2. Support Long Press action: hide and display Navigation Bar as needed. I think this is a step closer to what you want.

NSPANEL is used as “router”, but this setting (switch between coordinator or router ) can be only set in App Ewelink, and must available in device too.

Got it. We’ll put it in the requirements list of NSPanel Pro.

The navigation bar can be buggy few times, and only HOME button is available, but not work fine.

Yeah, we just added Advanced Settings (an entry point to Andriod system settings) in v4.1.1. We know there are bugs related to the use of Navigation Bar. But we think it’s better to have our beta test users to use it as soon as possible.

The known bugs and newly reported bugs will be fixed in v4.2.0.

69

Maybe it’s been already reported, I have several SNZB-02D zigbee thermal sensor joined to my NSPANEL PRO, when I try to make them available through integrated matter bridge I can successfully synchronize only one of them, all the others are marked as not yet supported.

All the sensors have latest release onboard (2.3.0) and are correctly working, I can access details for all of them directly on nspanel itself, ewelink app and even inside home assistant through sonoff lan integration

Nspanel release is 4.1.2

70

Hi,

I have an issue regarding if I don’t use the ns panel for a while I can not wake it up. It is do not respond if I touch the tured off screen.

It happened two times in the last two days.

But I can reboot is from the ewelink app.

App ver. 4.1.2

Device id: 10023a888c

A sent a feedback already. I attached a picture.

Thank you for your help.

Br

Peter

IMG_20251116_195051
IMG_20251116_1950511920×2560 460 KB

71

Hi, We’re very sorry for the issue you’ve encountered.We will fix this problem in version 4.1.3 (scheduled to be released this week). Please wait for the device to receive the firmware update.

72

Hi, first of all I’m really sorry you’ve run into this issue.

I tested it based on your description but wasn’t able to reproduce the problem. Could you please help us by submitting: The NSPanel Pro screen log: pull down on the screen → Settings→ About → Submit. The app log: Profile → Help & Feedback → Feedback → Submit

After that, please send me your device ID in a private message.

Thanks in advance for your help!

73

Would it be possible to eliminate the “leading zero” when the panels are in the 12 hr (AM/PM) mode? It would also be nice if the display would show 12:01 AM instead of 00:01 AM. :wink:

Regards.

74

You’re absolutely right. In the 12‑hour format there is no such thing as 00:01 AM. You simply have 12:01 AM, and that’s it.
The notation 00:01 belongs to the 24‑hour format, where midnight is 00:00 and the first minute is 00:01, and not 24:01. Though there are some who think it looks ‘nicer’ that way :slight_smile:

1 Like
75

Hello :slight_smile:
@MichaelLernsToCode We have an issue with MQTT in NSPanel Pro. Description: Mosquitto logs in HA show frequent disconnect/reconnect cycles from NSPanel. Each reconnect generates a new random ClientID (mqttjs_xxx). Additionally, connections from 172.30.32.2 (Home Assistant container) appear as unknown and close immediately.

Log excerpt:

Client mqttjs_7ea702fc disconnected.
New client connected from 192.168.1.12 as mqttjs_035275da (u'nspanel').
...
New connection from 172.30.32.2:46502 on port 1883.
Client <unknown> closed its connection.

Expected behavior:

  • NSPanel should maintain a stable MQTT session without constant reconnects.
  • HA connections should be properly identified and not close instantly.

Possible causes:

  • NSPanel MQTT client generates random ClientIDs on reconnect.
  • Keepalive misconfiguration (currently k60).
  • HA integration performing test connections or misconfigured.

Please check what is going on, because this problem keeps recurring in every recently released version.

76

Hi @jam3

Thank you for bringing this MQTT issue to our attention and for providing the detailed logs.

The team is on it! We’ve started looking into the connection issues to identify the root cause of the frequent disconnects.

We’ll be sure to update you here as soon as we have news. Thanks for your patience!

Best,
JoJo

1 Like
77

You’re welcome. In the development version this is normal, of course, and I understand that. Let’s catch as many shortcomings as possible :slight_smile:
Since we’re talking about MQTT in the NSPanel Pro, there’s another issue that keeps coming back – invalid values and missing JSON attributes.

Problem:
Template warnings: dict object has no attribute 'set_boost_mode_duration', fault_code, etc.
MQTT number error: Invalid value for ..._manual_mode_temperature: 0 (range 4.0 - 35.0)

Expected behavior:

Missing JSON keys handled gracefully (e.g. default values).
Values outside defined range ignored or configurable.

Steps to reproduce:

Configure MQTT integration with device sending JSON payloads.
Payload missing some keys.
Device sends 0 for manual_mode_temperature.

Logs show warnings and errors for TRVZB. Question: Does this result from errors in MQTT in the NSPanel Pro, or does it come from the TRVZB? Unfortunately, I haven’t been able to determine that. The most likely cause is an overlap of two sources of problems – the NSPanel Pro publishes incomplete or non‑compliant payloads, while the TRVZB sometimes sends values outside the expected range.

Regards.

78

Hi, @tom517 @jam3

Thanks for the great feedback! You’re right, the 12-hour format with leading zeros and “00:01 AM” is incorrect.

We’ve added this to our development plan and will fix it in a future firmware update.

We appreciate you pointing this out!

Best,
JoJo

1 Like
79

Hi, we’ve already fixed this issue in the newly released v4.1.3 version. Please update your device and give it a try. Thanks again for your feedback!

80

Hi

My nspanel pro is enrolled in beta testers but can’t update to 4.1.3.

It reboot in recovery mode and fails the update.

81

Hi,
We sincerely apologize for the inconvenience caused by the update failure.

To help us quickly identify the issue, could you please provide us with a photo of the screen when the problem occurs and submit a problem feedback log to us?

Best regards.

82

I also had problems with update. Few restarts, on-screen messages, …

Finally, I am up and running now, but 4.1.3 was not smooth.