NSPanel Pro Roadmap and Co-Created Future

[jam3]

@joeyhaverhals

I don’t think the current PX30 CPU will be enough for most modern-day demanding webpages and apps.

There are tablets available, you know

[MichaelLearnsToCode]

Thank you very much for your suggestion. I fully understand your expectations for NSPanel Pro, and I surely hope that NSPanel Pro could live up to it.

RK3588 is the most powerful SoC that Rockchip is offering, and it is also the most expensive SoC in Rockchip’s SoC series. SBCs (the one you mentioned, and also Rock 5B+) using RK3588 normally costs more than $100 USD. For a smart display (like NSPanel Pro) using RK3588 (RAM, eMMC will also need to be upgraded to support Android 15), the pricing will be higher than $200 USD.

To be honest, I’m not sure that SONOFF could sell products at the price of $200 USD at this stage.

[MichaelLearnsToCode]

@staxza

Any news on V4.3 release?

Sorry for the delay. We should be able to release v4.3.0 on January 13th, 2026. Please bear with us.

[dennis99]

Micheal your replies have a lot of insight. Thank you very much for sharing this amount of detail. It really helps me to invest more into Sonoff, because I love if a company is working this open.

Running the Home Assistant companion app on a NSPanel Pro 120 as well as on a NSPanel 86 now and I must say it looks better on a NSPanel 86 since it is a lot of pixels on the NSPanel Pro 120 and text becomes unreadable. What are your best practices for screen zoom? Do you use the Home Assistant native page zoom feature?

[Milk]

Hi, since the NSPanel Pro 120 has a higher screen resolution, it’s recommended to adjust the font size for better readability. After testing with two devices for comparison, setting the font to “Largest” on the NSPanel Pro 120 improves the page display significantly.

Font adjustment path:
Settings → Advanced Settings → Display → Font Size → Largest

[dennis99]

Wanting to try out the new Matter features in 4.3.0:
Issue 1:
On the NSPanel Pro 120 when clicking on Matter Bridge > +, I get a spinner and then “No Internet” (Kein Netzwerk in German locale).

When done via the App: Device Settings > Matter Bridge > +, I get a spinner, then “Failed to turn on pairing mode”. Also the button in Device Settings > Turn on Pairing Mode results in the same error.
Issue 1 was resolved by rebooting the device

Issue 2:
Zigbee is still set to Hub mode (though I would want to switch to Router mode). I now wanted to try switching Zigbee to Router mode, via the eWeLink App > Device Settings > Pilot Features > Zigbee Mode. I received the warning that this would reset to factory settings, I clicked ok and… yeah. It reset to factory settings and got removed from my eWeLink account. After the reset everything works though.

Issue 3:
I set up Home Assistant as a Matter Hub / Matter supported platform via the eWeLink App > Matter Bridge > Add and scanned the QR Code using Home Assistant. Everything is fine, I have 0 synced devices. When going to the NSPanel > Matter it says “Currently added to 1 matter-supported platform(s)”, but the supported platform has chinese writing (Translated with google translate it’s “Other”), maybe just missing localization.

NSPanel MQTT integration feature:
I have set up the MQTT Integration that came with 4.3.0. Maybe of interest to to others: NSPanel publishes to the topics zigbee2cube/# and to homeassistant/# and this cannot be changed. After initial connection also autocreate of entities work in Home Assistant via MQTT and looks like this (currently disconnected hence controls disabled):

[pettorossihernan]

Hi, I can´t find in my HA entyties the NS panel own speaker. Can you help me? I have integrated the panel by sonoff integration and by zigbee2mqtt, and neither them shows it´s own capabilities

[jackyaway]

why is a third device required to bridge home assistant device to matter?

[Milk]

I sincerely apologize for the issue. Regarding the Zigbee mode optimization feature mentioned for NSPanel Pro 4.3.0, it needs to be used in conjunction with the new version of the eWeLink app (5.22.1). With the new version, the device will not reset to factory settings or reboot when switching modes.

[Milk]

Please refer to this thread for checking the configuration steps:

NSPanel Pro v4.2.0 Officially Released: New Features & Enhancements

Hi @DamienCH Starting from version v4.3.0, NSPanel Pro not only supports exporting its Zigbee devices to Home Assistant（v4.1.0 Supported ）, but can also export its own features (such as the speaker and ambient light sensor). Here are the specific steps: Configure MQTT Broker : Set up via the eWeLink App. Navigation Path :eWeLink App > NSPanel Pro > Device Settings Page > Home Assistant Sync Devices : Follow the instructions in the App to complete the MQTT Broker configuration. Once successful…

[edgardasb]

What I have noticed, that nspanel pro displays sleeps even though i have set to “never”

[dennis99]

That version of eWeLink isn’t available in the iOS app store yet (I am still on 5.22.0). Maybe you could add that dependency to the 4.3.0 release plan, so people don’t run into the same problem as me.

I have edited the above post and added a couple of more issues / cleaned it up.

[Milk]

Hi, could you check the settings in these two locations:

Settings → Display → Autolock
Advanced Settings → Display → Sleep

Are both set to “Never” for screen timeout?If your settings appear to be correct, could you please send me screenshots or a video of the issue you’re experiencing?

[dennis99]

Just for everyone a little screenshot of the new MQTT integration in Home Assistant. Works like charm a, thanks to Sonoff/eWeLink Turning the screen on even when in sleep works and a new wake cycle starts (i.e. if you set sleep to 2min and you turn the screen on via MQTT, the screen stays on for another 2 minutes) - now think about Home Assistant automation with the screen automatically turning on when something happens (door bell etc.) The Ambient light sensor (illuminance in MQTT status) is also active with the display off (nice).
This also means I don’t really need the API anymore since the MQTT integration totally works.

I am missing the proximity sensor, please add it as a sensor then I really don’t need rooting

I like that Permit join is disabled, since I am using router mode, not hub mode. I am wondering about Turbo mode. Via the eWeLink app I can still enable Turbo mode via the Pilot Features. I am not sure whether this is a bug or a feature, since I haven’t used that feature and don’t know whether Turbo mode even is supposed to work in Zigbee router mode.

[gabriel7]

Nice work. I’m really looking forward to be able to control the NsPanel Pros via HomeAssistant. Sadly, I stumbled across two issues in 4.3.0.

Issue 1 - Display turning off
Similarly to @edgardasb, the display turns off after some time even though they were set to ‘never’ turn off. I just set Autolock and Sleep to never. Strangely, as soon as you set one of them, the other looses it’s state. (Meaning: If I set “sleep” to never, then in the “autolock” menu no option is selected anymore)

Issue 2 - Disconnects from MQTT
I have three NsPanel Pro 120 on 4.3.0. Each is connected to the same MQTT Server (eclipse-mosquitto running on Docker). All three display connect successfully on the initial setup and show up in HomeAssistant. After some time, only one stays connected. If I reboot a display, it connects again. However, after some time two get disconnected again. (It seems random which display stays connected)
If I open the eWeLink App and go to the MQTT settings on a disconnected display, it’s always saying “Failed. Please try again”.
The MQTT Logs don’t show any issue, so I’m assuming that it’s something within the software-stack of the NsPanelPro.

2026-01-13T19:48:58.332482804Z: New client connected from [IP]:46636 as mqttjs_02c6861d (p2, c1, k60, u'username').
2026-01-13T20:36:14.482815455Z: Client mqttjs_02c6861d disconnected.
(Note: It never re-connects. Only on reboot)

Any idea how to debug this issue any further? I’m happy to provide additional information.

[dennis99]

Can only confirm issue 2. Connection seemed wonky just as you described, but after the “latest” reboot I have a stable connection now. I didn’t really change anything, but pretty much the same setup as you.

[p.silhan]

Agree here.

I find this verion issues very confusing. I need some version of eWeLink, some version of NSPP, also TVRZB valve gets its own firmware version. Release date to GooglePlay store and Apple Store are different. It is complete mess.

I would really vote for better release coordination or backward compatibility.

And, I forgot ZBBridgePro, which also has its own fw version.

[edgardasb]

Yes, at advanced settings there were no sleep option selected, chosen to never, so far haven’t slept

[dennis99]

Please bear in mind that we are talking Beta release here. We are trying out new software here for testing purposes.

[matt653435]

• Always auto-start on system boot: By default, NSPanelPro App is the Home App，aka Launcher, so it will always run when NSPanel Pro boots. When you launch other app through F-Droid -> Settings -> Installed Applications, NSPanelPro App is still running in the background and provides an AssistiveTouch button for you to click in order to go back to it (bring NSPanelPro App to foreground). But if you set other app such as Home Assistant companion app as Home App, NSPanelPro App won’t start after system reboot, which disables all the goodies NSPanelPro App provides. In this version, NSPanelPro App will always auto-start on system boot no matter it’s Home App or not.

  Is this implemented? I’m on version 4.1.5 (app) - it says version 4.3.0 is available but is red circle next to it (to the left) and wont let me update any further.