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

zigbee router mode paired with z2m

Zigbee doesn’t pair through MQTT — these are two completely separate layers.
MQTT is only the transport used by Zigbee2MQTT to publish device states to Home Assistant.
The actual pairing happens exclusively in the Zigbee layer, directly between the coordinator and the device, using the Zigbee network key.

If NSPanel Pro is acting as a Zigbee router, it pairs directly with the Zigbee coordinator, and only after that Z2M publishes its data via MQTT.

It’s worth using the correct terminology here, because mixing MQTT and Zigbee pairing leads to confusion and makes it harder to understand what’s really happening in the system.

1 Like

correct . paired as zigbee router (through routing mode zigbee ) , but i meant to say that its also connected as device through mqtt (integrated) by mqtt address , user and password

The MQTT username, password and topics don’t have anything to do with Zigbee pairing. Every device handled by Zigbee2MQTT appears in the MQTT broker, because MQTT is just the transport layer Z2M uses to publish device data to Home Assistant.

The Zigbee pairing itself happens only in the Zigbee layer — radio‑to‑radio, using the network key. So seeing NSPanel Pro in MQTT is normal and expected, but it’s not related at all to how the device joins the Zigbee network.

When the NSPanel Pro is switched from Hub to Router mode, it effectively splits into two logical devices. The Application Layer (the screen/Android side) still uses MQTT to report its status and receive commands. The Zigbee Chipset, however, is now an independent router that requires a hardware-level handshake (using the network key) to join your existing Zigbee mesh. You are essentially managing two different communication paths for one physical device.

Your explanation about NSPanel Pro having two logical layers is correct in general — the Android side communicates over MQTT, and the Zigbee chipset joins the mesh using the Zigbee network key. But this is a separate topic from what we were discussing earlier. The original point was simply that Zigbee pairing does not happen ‘through MQTT’. MQTT is only the transport used by Z2M after the Zigbee device has already joined the network.

its just misunderstand because i was talking about NSPanel (two logical devices) at same time , yes that abit confuse for any new user

No worries — that is why I wanted to keep the terminology clear so others reading the thread don’t get confused.

No those are diffrent these are mine…

(attachments)


In that case, you can contact the product seller to inquire about the calibration process before use (it seems this device is not from Sonoff).

I checked the logs at this specific time, and it shows that the NSPanelPro’s WiFi connection was disconnected. No other abnormalities were recorded at other times.

May I ask if you encounter this issue frequently? If it only happened this once, it might have been caused by a temporary network fluctuation leading to the disconnection.

If you experience this issue frequently, you can still submit the logs after the problem occurs.

Buth according to my observation, it can disconnect from wifi even when they are in the same room.

Ya I tried thirdrealitys calibration and it dident work idk…

Ok I will submit everytime i see it then cause it seems to happen alot…

Trying to play audio with the NSPP speaker. Dou you have a tutorial on how is this supposed to be working. It seems that the audio shouls be located inside de NSPP and not in HA OS.

Hi,

I have a Sonoff NS Panel pro 120 version 3.70 and I would like to update it with the new firmware version. Unfortunately, I have rooted my device, so I cannot update it from the app. Can you help me with this?

My device ID is 100250dd96.

Many thanks,

Quentin

Hi, you can obtain the latest version through this beta application tool:

May I ask about your specific use case for this? Currently, the NSPanelPro itself does not have a feature for selecting and playing audio files. However, you can provide me with the detailed scenario, and I will explore whether it currently exists or if it might be feasible to implement in the future.

Ok, la idea es usar Alarmo como sistema de alarma dede Homeassistant. Y las notificaciones por audio de alarma activada o desactivada que se emitan al NSPP. Para esto necesito que el NSPP figure como una entidad de salida de audio, asi como ocurre con parlantes externos wifi o como con dispositivos de Alexa.

Lo extraño es que desde Music assistant pude reproducir musica en el Panel selecionandolo como “this device” en las opciones de output de sonido. Por lo que estimo deberia poder configurarse.

Lo que no se entiende el la utilidad que proyectaron al permitir reproducir sonidos desde el panel con las entidades que actualmente aparecen. No encuentro una forma util en que me sirva a lo que quiero armar.

Gracias

Based on your description, I tested it and found that NSPanelPro cannot be selected as an alarm device because it is not a media-type device. However, you can set up an automation like this:

  • Trigger condition: When an alarm is detected
  • Action: Select Device → NSPanelPro → Set NSPanelPro Spkr Audio Address → Enter the audio file address; or select the built-in alarm sound on the NSPanelPro.