If the NS Panel Pro works as a speaker it will open so.many possibilities when used with Home Assistant.
For example it will be possible to announce alarm.activations and deactivation alert about security threats when linked to the cameras, alert on voltage fluctuations, and many other uses.
What is needed is just to expose its speakers to Home Assistant.
May I ask what device your HA is installed on? Does the device have Bluetooth function? If so, can NSPanel Pro be connected as a Bluetooth audio peripheral?
I run two different systems, one is on HA Green with no Bluetooth, and the other one is on an Ihost.
Previous attempts to.connect NS Panel.Pro through Bluetooth with the Ihost-basef system did not materialise. I also.prefer not to use Bluetooth since I am.already using Wifi and Zigbee all on 2.4 G, adding Bluetooth will further crowd that frequency.
Thank you for your response. I do appreciate the declared commitment to openness and the willingness to collaborate with integration developers. However, referring back to my original post, I feel that the core issues remain unresolved.
This isnāt about differing definitions of āopen sourceā or āopenā, itās about actual access. The community, and especially the developer behind SonoffLAN, has spent months trying to work around limitations that simply shouldnāt exist in a device marketed as open. This is not a matter of interpretation, but of practical reality.
Regarding Bluetooth: NSPanel Pro detects nearby devices, but offers no interaction. The response asks what kind of Bluetooth functionality I expect. Fair enough, but it shouldnāt be the userās job to explain why a module exists. If the device displays a list of nearby devices, the natural question is: what can be done with them? As it stands, it feels like a feature without a function.
Moreover, the reply doesnāt address the core of my original point: the underutilized hardware potential. Weāre talking about a PX30, Mali-G31, 2 GB of RAM, and yet the interface is sluggish, the touchscreen responds slowly, and configuration menus can freeze for several seconds. These arenāt subjective impressions, but repeatable observations across units.
If NSPanel Pro is to be taken seriously, it needs more than a declared direction ā it needs concrete action: documentation, API access, system stability, and full utilization of the hardware thatās already there. That said, NSPanel Pro is certainly easy on the eyes and looking very good indeed
Thank you for sharing your feedback. I believe I understand your request now. At the moment, the NSPanel Pro unfortunately cannot be used as a speaker to play audio from other sources. The feature I mentioned earlier only allows NSPanel Pro to act as an audio source and stream sound to an external Bluetooth speaker. Iāll make sure to pass your request to the relevant team. Thank you very much.
I think I understand your point. Regarding openness and open-sourcing, due to certain policies and business considerations, itās not something we can achieve immediately. Please give us some time to improve step by step.
As for the Bluetooth part, the current scanning feature only supports NSPanel Pro acting as an audio source and connecting to a Bluetooth speaker. Iāll share your ideas with the relevant team so we can explore better ways to leverage different hardware in the future.
On the performance issue you mentioned, we will soon release our native version, which should bring significant improvements to the interaction smoothness. Weād love for you to try it once itās available and share your feedback with us.
Thank you again for taking the time to share your thoughts.
This feature will be very useful, especially for open platforms. For example at the moment Home Assistant can provide voice notifications or alerts about for example, weather alerts, or security infiltrations etc. It sis unfortunate NS Panel Pro has teh hardware to support such functions, but it cannot because of its software limitations.
Here are things we are planning to do with NSPanel Pro, though they will take us some time:
Native NSPanel Pro App as @TimiXu has pointed out. The current version of NSPanel Pro App is developed using React Native technology which is more suitable on high-end hardwares such as mobile phones. We have been developing the new version using Kotlin and Jetpack Compose for 4 months now, and we are going to do grayscale release this month.
Build-in F-Droid App store. Users could download all kinds of Open Source Apps from F-Droid, including Home Assistant App.
Universal Matter Bridge. The ability to bridge all kinds of devices to 3rd-party Matter Fabric, such as Zigbee devices directly connects to NSPanel Pro, eWeLink devices under userās eWeLink account, Home Assistant devices in the same LAN as NSPanel Pro.
Deeply integrated with Home Assistant through Home Assistant MQTT protocol. HA users could manage NSPanel Pro and its Zigbee devices right in HA Dashboard, MQTT integration, Automation, etc..
VUI for AI agents. Turn the microphone and speaker of NSPanel Pro as VUI for Home Assistant Assist and other AI agents.
Open source the underlying customized Android OS, so the whole user experience could be fully customized for other usage scenarios.
I think we all agree that NSPanel Pro has great potential. Letās explore it together.
Letās be honest, most of this shouldāve been baked into NSPanel Pro from the start. But hey, better late than never. The roadmap finally aligns with what the community actually wants: openness, performance, and real integration. So hats off to the devs for listening and building. And to everyone who stuck with NSPanel Pro through its awkward teenage years. Our patience is about to pay off.
Letās explore what this panel can really do if you let us to. Cheers!
Your six point note is music to my ears. This is really great news snd will lead some of us to discard additional IoT devices that were meant to cover for NS Panel deficiencies.
For example, I Have installed additional alarm control hardware in a predominsntly Sonoff ecosystem while the NS Panel.Pro is right there sitting idle.
Great stuff and keep.it up! Canāt wait for the updates!
Why early enrolling only through Facebook message? What if someoneās a certified weirdo who steers clear of Metaās gadgets. You know, not exactly vibing with Mark Zās empire of algorithms?
Please just send me your NSPanel Pro deviceid. I will handle the OTA issue.
By the way, the V4.0.0 is a rewrite of the whole NSPanel Pro App. So it is not feature-complete compared to V3.12.0, and it will have bugs.
The most important feature that is missing in V4.0.0 is the Open API support. We will add Open API support in V4.1.0 which is scheduled to release on November 10th.
I manage mine remotely. I have both Pro and Pro 120.
Brother way I have noticed that it is not possible to initiate an update remotely. Hope this new OTA update will allow remote update. If it will I will.also send my device IDs
By the way, how many Zigbee devices are connected to your NSPanel Pro? And have you using the Open API of NSPanel Pro?
Because v4.0.0 doesnāt support Open API yet. The next version (v4.1.0) which is scheduled to release on November 10th will have Open API support (mainly for backward compatibility).
If you do not use Open API , please give us you DeviceID for NSPanel Pro 120.