NSPanel Pro Roadmap and Co-Created Future

@JoJo Great, thank you. Looking forward to the update!

1 Like

Love the openness. In the initial post you did strike through several paragraphs (especially the very end as well as version 4.4). Could you add some information to the initial post on why that is? I don’t want to comb through all 161 posts here to understand what happened :slight_smile:

Additionally I would love to know your “grand plan” as for feature parity with current release version 3.7. I am currently unsure on how to start my Home Assistant journey with the NSPanel Pro. Should I use a Web Shortcut? Should I use the Companion app installed via F-Droid using the current beta firmware? I just don’t want to time into something if it is not the future.

Thanks for all the work you are doing!

1 Like

Thank you very much for using NSPanel Pro.

In the initial post you did strike through several paragraphs (especially the very end as well as version 4.4). Could you add some information to the initial post on why that is?

Sorry, that was a typo :sweat_smile: Please check it again.

Additionally I would love to know your “grand plan” as for feature parity with current release version 3.7.

v3.x is not maintained anymore. We encourage everyone to update NSPanel Pro to v4.1.x firmware. The latest version which is v4.2.x now is in beta phase, but v4.1.x is stable now.

I am currently unsure on how to start my Home Assistant journey with the NSPanel Pro. Should I use a Web Shortcut? Should I use the Companion app installed via F-Droid using the current beta firmware?

Home Assistant companion app through F-Droid is the future. I am using it now.

2 Likes

:growing_heart: Perfect thanks! Will be looking at the companion app then.

Sorry, I misspoke with version v.3.x and was actually thinking about v4.1.x. When (not the exact date) will you implement features from the old FW that are currently missing, especially the Open API? This is currently not documented in your roadmap.

I am very interested in the Open API to turn the display on/off via HA (e.g. on doorbell ring/camera activity) and also other features such as display dimming during different times of the day.

1 Like

I am very interested in the Open API to turn the display on/off via HA (e.g. on doorbell ring/camera activity) and also other features such as display dimming during different times of the day.

If you are going to use NSPanel Pro with Home Assistant, then you won’t need Open API. The following feature is exactly what you want. We are dedicated to make NSPanel Pro the best display for Home Assistant.

v4.3.0 on January 8th, 2026

Additional features

  • Export NSPanel Pro itself to Home Assistant: NSPanel Pro is able to export its Zigbee devices to Home Assistant in v4.1.0. In this version, NSPanel Pro will be able to export its own capabilities, such as speaker, ambient light sensor, to Home Assistant.
2 Likes

Is there any documentation on OpenAPI specifically for nspanel? If so, where can I find it?

1 Like

@MichaelLearnsToCode awesome and awesome. Market it as exactly that. I have no clue how the speaker sounds and the microphone is, but using that for controlling HA would really be a game changer.
I have a problem with the current Export feature, maybe good feedback for you: Currently you can export the NSPanel via MQTT, but in the configuration screen you need to enter the “Home Assistant IP” - I have an external Mosquitto setup that is my MQTT broker, not Home Assistant (which is using said broker). Maybe it is only the wording on that screen.
Secondly since I have other awesome Sonoff products (dongle plus pzg23) to use as my Zigbee antenna, the NSPanel will never be the Gateway, but always be used as a Router. I never want to export Zigbee devices from the NSPanel > Home Assistant, so priority-wise I definitely want to export the NSPanel.

I really have no clue if you have usage numbers, but I would assume that not many people use the NSPanel as the Zigbee Gateway since there are just better devices with better antennas - just pondering priorities for development.

2 Likes

What can be done via web api? My goal is to connect my compensation device with sonoff products. I need to write a gui where I can control your devices.

2 Likes

I’ll add my two cents here. The NSPanel Pro API is too shallow to be useful for advanced users, while at the same time being too technical to appeal to beginners. As a result, the documentation exists, but its real‑world usefulness remains low.

This is especially visible in the context of Zigbee. The panel doesn’t expose any functions that would allow it to be treated as a full‑fledged hub — no access to clusters, no push notifications, no network map, no raw data. As long as the API remains just a thin layer on top of “device/thing”, it’s hard to expect it to become a tool that meaningfully changes how devices are used.

1 Like

Very interested in both the “New 120 Type with 2 relays” and the new 8-inch Type. I’d probably buy both, for different use-cases.

I’m hoping these might have physical buttons? And that the screen/CPU will be more responsive than the current NSPanel Pro 120?

1 Like

I have a problem with the current Export feature, maybe good feedback for you: Currently you can export the NSPanel via MQTT, but in the configuration screen you need to enter the “Home Assistant IP” - I have an external Mosquitto setup that is my MQTT broker, not Home Assistant (which is using said broker)

By default, we assume the MQTT broker is running on the same hardware (IP) as Home Assistant. In your case, you can just use the IP of your MQTT broker.

Secondly since I have other awesome Sonoff products (dongle plus pzg23) to use as my Zigbee antenna, the NSPanel will never be the Gateway, but always be used as a Router. I never want to export Zigbee devices from the NSPanel > Home Assistant, so priority-wise I definitely want to export the NSPanel.

NSPanel Pro will be exported only if it has no Zigbee subdevices (Zigbee Router mode).

I need to remind you, Dongle-PZG23 is Z-Wave dongle, not Zigbee dongle. Dongle-PMG24 is our newly launched Zigbee dongle.

1 Like

In your case, you can just use the IP of your MQTT broker.

Perfect. Maybe you can adjust the wording on the configuration screen, so people know what to configure (since HomeAssistant is not automatically an MQTT broker - but may be in many cases).

Dongle-PZG23 is Z-Wave dongle, not Zigbee dongle. Dongle-PMG24 is our newly launched Zigbee dongle.

Sorry, that’s what I meant. I copy & pasted the wrong product ID.

1 Like

Thank you for flagging this.Your feedback is spot on. We’ll take this on board and will look into updating the wording on the configuration screen to reflect your suggestion and prevent confusion.
We really appreciate you helping us improve.

1 Like

Hi, in ¨matter bridge chapter 3¨, is it possible to add a feature to filter devices (by label for example) to bridge through matter? thank you

1 Like

Very interested in both the “New 120 Type with 2 relays” and the new 8-inch Type. I’d probably buy both, for different use-cases.

The 120 Type with relays is on schedule, and it won’t have physical buttons. Just like your phone, we think the future is Full-screen.

I am very sorry to say the 8-inch Type is canceled due to its high cost. The price of RAM and eMMC is astonishingly high due to AI instustry’s high demand. Our new 86 Type with relays which is going to be launched in April 2026, will also cost a lot more than existing 86 Type, due to the same reason.

2 Likes

Thank you very much for using NSPanel Pro.

in ¨matter bridge chapter 3¨, is it possible to add a feature to filter devices (by label for example) to bridge through matter?

By default, Matter Bridge will not bridge devices to 3rd-party Matter ecosystem (Matter hub) unless you manually select specific devices. We designed it this way because this gives you full control of what and when your devices are exported to 3rd-party Matter hub. We know this manual operation is a bit more work, but we think adding new devices is not a frequent operation, you only need to do it from time to time.

4 Likes

I don’t think the current PX30 CPU will be enough for most modern-day demanding webpages and apps. Why not put an RK3588(S/S2) in one and call it the Ultra or something? That would be a device that could do it all.

Yes, it would cost more to build and yes this would raise the price for the consumer. But i for one would be more than happy to pay the premium for such a device. The Orange Pi 5 Max uses it for example so it cannot be that expensive. I would instantly replace all my 86 screens if a product such as that would be released and probably buy some more if they come in different sizes with the same 230v concept.

Imagine a SONOFF touch screen with the RK3588, this could open the door to virtually any screen size, run any app and even multiple at the same time, run multiple camera feeds and support the latest Android versions which would mean it can be updated for years. It would give so much headroom that it could be used for so much more.

I mean the old PX30 was released back in 2018 and has an AnTuTu score of 40.000 with 20,8 GFLOPS. The RK3588 is pretty old as well since it was released in 2021, but it already makes a huge jump to an AnTuTu score of 575.000 with 450 GFLOPS. In many aspects it’s over 10-20x faster.

Don’t get me wrong, SONOFF is definitely moving in the right direction. The new software is a huge step forward with their fdroid app store being able to install android apps. If now only they could back it up with a CPU like the RK3588 to give it the performance, it so desperately needs.

2 Likes

There’s still a lot of work ahead of you. I can already see at home that nspp is starting to be usable even in the test version.

1 Like

Any news on V4.3 release?

1 Like

May be delayed for several days.