After the latest firmware update for the nspanel pro 120 (4.0.12), I can no longer add it as a repeater to the ZbBrige-P (2.7.0).
The nspanel finds the gateway, but the app continues to search for the device without ever pairing it.
Check the roadmap for details on the changes. In version 4.x.x, NSPanel Pro operates solely as a Zigbee coordinator. Currently the router functionality is unavailable. It will likely be restored.
Since NSPanel Pro has significantly greater capabilities as a Zigbee controller anyway (e.g., it supports many third-party devices), consider using it as a controller instead of ZbBrige-P.
Thanks for the quick response.
Since I have two nspanels because I have a three floor house, even if I use one nspanel as a coordinator, the other will never be able to act as a repeater. Correct?
Kr
Francesco
Correct, indeed. Long live the coordinator - there can be only one! 
Keep in mind that when using two NSPanel Pros, a new issue arises: each one creates its own Zigbee network, regardless of whether it has child devices or not. NSPanel Pro doesn’t offer an option to disable Zigbee, at least none that I’m aware of.
Is that a problem? Probably not in terms of interference or bandwidth “stealing.” But you do lose the router function, which means your Zigbee network range might shrink. That depends on how many devices you have acting as routers (typically those powered from mains, not batteries) and I don’t know what your setup looks like. Either way, the situation will definitely change. For better or worse? Hard to say, especially from a distance and in theory.
I’m not sure how the eWeLink platform handles multiple Zigbee coordinators. I’ve only tested that scenario once. It was possible, and naturally, it resulted in two separate Zigbee networks — each with its own routing points. In Home Assistant (both ZHA and Z2M), you can only use one coordinator, which makes sense and is technically justified.
In this case, I’d recommend discontinuing the use of the ZBBridge-P gateway, making one of the panels your coordinator, and ensuring good placement of Zigbee devices with router functionality. Alternatively, you could split Zigbee into two networks, each with its own NSPanel Pro as coordinator, but that second option will likely complicate automation scenarios. Honestly, I’m not sure what to recommend. You’ll need to test and decide for yourself.
One way or another, you’re in for some Zigbee elbow grease - time to reconfigure and re-pair everything. On second thought, maybe it’s better to stick with ZBBridge-P as the coordinator, make sure your other router-capable devices are well positioned, and wait until the NSPanel Pro gets the option to switch roles again. It’ll definitely mean less work, and there’s a good chance your Zigbee network will handle things just fine.