Can someone tell me where I can set up the Sonoff Dongle Max in this? There’s no place to write anywhere?
Which protocol stack should I select?
It depends on how you’re connecting it and which protocol you want to use.
Is this supposed to be Matter or Zigbee? Because if it’s Zigbee, you can’t have two Zigbee controllers at the same time. The CUBE OS documentation describes Zigbee integration as a feature that works with a single connected Zigbee dongle acting as the coordinator. There’s no mention of running two coordinators in parallel, and the entire Zigbee2CUBE architecture assumes one stack, one port, one coordinator - which is exactly how Zigbee is designed. A Zigbee network can only have one coordinator; a second dongle in coordinator mode would create a conflict and form a separate network, and CUBE has no mechanism for handling multiple Zigbee stacks simultaneously.
I would like to put a zigbee dongle over tcp/ip for cubeos. Where will all the zigbee devices be connected.
The dongle over TCP/IP is just a remote serial port. It doesn’t create a second network layer or a separate place to ‘plug in’ devices. The coordinator remains the single entry point for the entire Zigbee mesh.
It’s straightforward - Sonoff Dongle‑M = EFR32MG21 = EZSP stack, regardless of whether you connect it via USB or TCP/IP.
Remember that TCP/IP doesn’t change anything. It’s just a ‘remote serial cable’, not a different Zigbee protocol. It will work reliably as long as you:
- provide the correct IP:PORT
- select EZSP
- don’t run a second Zigbee coordinator in the same system
You’ll find an excellent guide on the official Sonoff pages.
I’m not going to run a second Zigbee coordinator. I’m going to connect a tpc/ip zigbee dongle to CubeOS and I still want to enable the matter bridge so I can connect nspp in the hallways. I’m solving this because I can upload HA to the Raspberry Pi if necessary.
There is no information whether there will be iHost2 and I need to be sure that I can change CubeOS at any time. There were several questions whether there will be iHost2 and all were ignored. So one does not know what to think. The second thing is creating an nvr for CubeOS that will be able to record from ip cameras. It cannot be turned on on iHost even by mistake. I gave them a suggestion that they would put an nvr in iHost only for their cameras, but no answer.
No worries, but connecting your Dongle‑M over TCP/IP to CubeOS doesn’t create a second Zigbee coordinator. It’s still the same coordinator, just with the serial port forwarded over the network. No conflict there.
The Matter Bridge is a separate thing: it only exposes the Zigbee devices that CubeOS controls locally. It doesn’t ‘connect’ NSPanel Pro through your dongle, and NSPanel Pro isn’t part of that layer at all.
If you run Home Assistant on a Raspberry Pi, that’s fine — but it doesn’t change the architecture. HA will see your Zigbee network through the Dongle‑M, and NSPanel Pro will show up as its own independent device. Two different worlds.
1 Like
I know that.
Thanks for the correction. It looks like the issue in CubeOS isn’t that EZSP “‘doesn’t work” technically, but rather that CubeOS doesn’t implement full support for EZSP‑over‑TCP, even though that’s exactly how the Dongle‑M operates. The difference isn’t in the protocol itself, but in the transport layer and in how CubeOS interprets the selected stack.
In reality, this seems - if I’m thinking righttly - to be a compatibility gap between CubeOS and the Dongle‑M’s TCP mode, not a problem with EZSP itself.