We have already discussed the most important points in the other thread, ‘NSPanel PRO v4.3.0…’, and we have come to the conclusion that it is better to first establish a robust and strong foundation for the MQTT system and then see what add-ons can be added.
In any case, I will try to explain it better, because I am not very knowledgeable about home automation and I may need to rethink it in another way. My idea is not to replace my entire HA installation; I want to manage everything through HA, but complement it with some advantages that NSPP already has through its modules.
For example, I want to be able to manage the alarm system from my mobile phone with the HA app and from the NSPP with the original screen or the HA Companion app, but linking it to the “Smart Alarm” module so that I can use the audible alerts and alarm notifications already generated by the NSPP. That’s where my idea of linking HA-MQTT to the existing NSPP modules comes from.
However, my goals may be too ambitious, and I may have to wait longer to see which NSPP entities allow sharing with HA via MQTT.
You’re about right
I think your ideas make sense in principle — everyone wants to squeeze as much functionality as possible out of the hardware they already have. And it’s good that you’re thinking about how HA and the NSPP could complement each other rather than replace one another.
That said, every feature has to fit within the technical, development and even marketing boundaries of the device. Even the best concepts sometimes hit limits that aren’t about imagination, but about what the firmware, hardware or the vendor’s roadmap can realistically support. It’s easy to end up reaching for the moon if those constraints aren’t taken into account.
Your approach of waiting to see which NSPP modules eventually expose stable MQTT entities is the right one. Once the foundation is solid, it becomes much clearer which ideas are feasible and which would require the panel to become something it was never designed to be.
So keep exploring the possibilities — just with the understanding that some things may land in the “nice idea, but not technically viable” category for now. And if the Smart Alarm module eventually exposes the right hooks, then great, you’ll be able to build on that without fighting the device’s architecture.
Thank you for your detailed feedback. We will do our best to support the MINI-RBS in the next version of NSPanel Pro. Camera support is already planned for the Matter bridge development schedule in March. We appreciate your understanding.
I know Matter can work over Thread, WiFi & Ethernet. Can the NSPP function as a Thread border router? What exactly does the Matter bridge do? Is it only Matter via WiFi? If connecting via Home Assistant, will you be exposing anything on NSPP via Matter, or only MQTT &/or Zigbee? Currently, I have NSPP connected to Home Assistant via Matter & Zigbee, with Zigbee in router mode, but no details show up via Matter in Home Assistant.
Hi,
Regarding the ZBMINIR2 mapping error, I’m currently checking the logs and will update you as soon as I have results.
The device cannot perform OTA updates via the app because after syncing through the Matter Bridge, the device was changed to the Matter type, which does not support OTA by default.
Hello @Milk@JoJo@MichaelLearnsToCode , i am testing out nspanel pro 120, and found that there is no way for a native function to use the proximity sensor to wake up the screen (like every other smart home panel on the market). This should be a #1 priority function to activate. I had explored options and at the moment there are some tweaks can be done to activate this via: https://blakadder.com/android-panel-proximity/ and https://github.com/seaky/nspanel_pro_tools_apk , but the normal way should be NATIVE , integrated in the panel firmware.
Hello, we have received your request. The "use the proximity sensor to wake up the screen " feature has been added to the roadmap. We will confirm the specific release time and get back to you tomorrow.
Los dispositivos los estoy pudiendo actualizar desde el ihost después de desenlazar y volver a enlazar con este. Voy poco a poco porque son unos 15 minutos cada uno. Si falla alguno te comento.
Si hay algún avance de los ZBMINIR2, ya me comentas.
Hello again @momoko@JoJo@MichaelLearnsToCode@milk . I am further testing NSPanel Pro 120 functionalities and if this is the best forum topic for this, i would like to share some other feedback i have. This time is about the Voice Call function. At the moment the voice call works from ewelink app to nspanel pro. But i could not find a way to call from NSPanel pro to ewelink app on phone. In parallel i am testing other smart panels from other brands, and all of them supports the 2 way voice call from panel to mobile app and other way around. Am i missing something or this function is not enabled yet ? Thanks
Yes, thank you for your feedback. The two-way voice intercom feature is not currently supported, but we will include it in our future roadmap to explore how to implement this functionality.
Sorry for the wait! Version 4.4.0 (Beta) has been released. Those interested can now upgrade to try out the new features. If you encounter any issues, feel free to reach out to us anytime.
Thank you, @Milk, I successfully updated to 4.4.0 with no issues and now I’m testing this Adaptive mode feature for TRVZB. I also confirm that the ‘ghost’ device that was showing up as a Thermostat in my setup has been resolved. The Thermostat screen still shows after restart even if it’s been disabled via the app, but as far I understand it’s an issue with the app, not the NSPanel.
Just curious, has this been implemented? I cannot find it anywhere..
I own two NSPanel Pro 120, but both of them are in 4.1.5 version and when I check for the updates in the panel it just returns ‘checked’ as feedback. Considering 4.3.3. is live and 4.4.0 is about to come, is that normal?
Thanks!!! Just updated last night. I was waiting for HA to detect the panel as an speaker output, but I dont see it as an entity to select as an audio output for a TTS message. How do we configure it?
We don’t. The NSPanel Pro can handle voice calls between two panels – but that absolutely does not mean it works as an audio speaker for Home Assistant. Home Assistant doesn’t support ‘speakers’ as standalone devices. HA only works with media players (renderers) that expose a proper audio endpoint, such as Chromecast, Google Home, Echo, or DLNA devices. The NSPanel Pro is not a media player and doesn’t implement any audio‑streaming protocol. It isn’t exposed as any standard service, it has no audio API, and therefore HA has nothing to detect.
Even if you install VLC or another player from F‑Droid, HA still won’t see the panel as an audio renderer. Installing a local player doesn’t change the system‑level capabilities — the device still doesn’t provide a DLNA/UPnP/Chromecast endpoint that HA could use.
Because of that, the NSPanel Pro cannot be used also for TTS playback. TTS (Text‑to‑Speech) means converting written text into spoken audio, and the NSPanel Pro simply doesn’t support that functionality
