Skip to content

Please support multiple coordinators #577

New issue
New issue
Open
Feature
Open
Please support multiple coordinators#577
Feature

Description

@PaulKlumpp
PaulKlumpp
opened on Nov 14, 2025

I do use Home Assistant at my place with a USB dongle.
I can manage (and actually do) another Zigbee network at another house with a Smlight SLZB-06..
Because ZHA can't also add the SLZB-06 coordinator, I needed to use the Zigbee2MQTT HA Add-On which connects to the SLZB-06 over a socket.

I wish I would not need Zigbee2MQTT. 😌 I wish ZHA was able to add another Coordinator using a socket.

Edit: To clarify my use case:

The house (house 2) of my mother is 50 km away. Our IP-networks are connected with a VPN. My mother is old and I want to check on her, that she is walking by a motion sensors once a day.

But, I do not want to install a Home Assistant machine in her house. I only want to have a Zigbee Coordinator in her house.

My current solution: The SLZB-06 is a Zigbee Coordinator (as a machine) that is TCP/IP addressable using a socket (Zigbee2MQTT can do that, see: https://smlight.tech/manual/slzb-06/guide/installation/#zigbee2mqtt-setup). So I run Zigbee2MQTT alongside my Home Assistant (house 1) which can address the SLZB-06 (house 2).

What I rather want:

I want to use only one Home Assistant with the ZHA integration. As far as I know, ZHA uses this zha library.

I do not want to work around the ZHA limitation (which is only supporting one coordinator) by adding Zigbee2MQTT as Add-On.

Activity

  1. Hedda commented on Nov 24, 2025

    @Hedda
    Hedda
    on Nov 24, 2025

    Can you maybe explain how and why you want the the zha library (i.e. the platform-indepenent backend framework) and/or Home Assistant's ZHA integration (i.e. the frontend Zigbee gateway implementation) to implement support for multiple Zigbee Coordinator radio adapters?

    That is, what is the goal that you actually want to achieve? Please understand that in theory it would be technically possible to multiple Zigbee Coordinator radio adapters in many different ways depending on what you actually want to achieve from an end-users perspective.

    Note! Be aware that at least in the Zigbee 3.0 specification the hardcoded limitations are that there can only be one Zigbee Coordinator per Zigbee network, (the current protocol standard only allows for a single Zigbee Coordinator per Zigbee network).

    Here below are for example a couple of possible solutions that could probably be achieved (but question is if they should be?):

    • Option 1: Add support to Home Assistant to run more than one instance of the ZHA integration via a single integration.
      • What is needed to make that happen?: See the experimental work dmulcahey done around ZHA WebSocket Server ("ZHAWS"). Read:
      • Pros: From an end-users perspective this would allow you to setup several instances of the ZHA integration](https://www.home-assistant.io/integrations/zha), each of which will need to use its own Zigbee Coordinator radio adapter, meaning that it would enable you could have a Zigbee network in different areas/locations that are reachable with standard Zigbee signals (such as for example if you have a detatched building/construction somewhere farther away on you property).
      • Cons: This would create its own totally separated Zigbee network on Zigbee Coordianor radio adapter. Meaning that you do not get the benefit of using the same devices in a single Zigbee network mesh for extended range/coverage, and you can not use Zigbee groups or Zigbee bindings which means that all automations needs to go via the automation engine in Home Assistant.
      • Notes: The option of allowing multiple instances is one of the main benefits of Zigbee2MQTT when compared to the ZHA integration.
    • Option 2: Add support to for the zha library (i.e. the platform-indepenent backend framework) use multiple Zigbee Coordinator adapters and run a seperate Zigbee network on each Zigbee Coordinator.
      • Pros: This might be the best approach needed to implement native support in the zha library for the new ”Suzi” (Sub-GHz Zigbee feature) if a Suzi network now require it to be is own Zigbee PAN (Private Area Network) for the Sub-GHz fequency band?
      • Cons: Increases the compexity of the zha library if it needs to be able to support multiple cuncurrent Zigbee networks.
    • Option 3: Simply duplicate the zha component in Home Assistant's core and that way allow Home Assistant to run more than one instance of the ZHA integration via a multiple integrations (meaning you would see zha1, zha2, etc. in the frontend).
      • Pros: Quick workaround to get around the limitation,
      • Cons: Dirty solution since probably require duplication of components in Home Assistant's core?

    The house (house 2) of my mother is 50 km away. Our IP-networks are connected with a VPN. My mother is old and I want to check on her, that she is walking by a motion sensors once a day. But, I do not want to install a Home Assistant machine in her house. I only want to have a Zigbee Coordinator in her house.

    For such a long distance I would however say that connecting to a remote Zigbee Coordinator that far away will never ever be officially supported. Becuase of the latency you should in a such case cut your loses and just install another totally seperate instance Home Assistant and ZHA (or Zigbee2MQTT / Z2M) in that remote location. Too long distances would make a stable split installtion out-of-scope.

  2. zigpy-review-bot
    added the
    Feature
    issue type on Oct 10, 2026

  3. Hedda commented on Nov 10, 2026

    @Hedda
    Hedda
    on Nov 10, 2026

    For reference, similar thing was now raised as a WTH here which comment I think has some stong and good arguments for this:

    I also actually believe this concept will soon become more relevant when "Suzi" (Sub-GHz Zigbee 4.0) devices become available on the market as you will then need another seperate Sub-GHz radio adapter to communicate with those devices, regardless if they are on the same Zigbee network or not, meaning that you will probably need one Zigbee Coordinator for 2.4GHz devices and a second Zigbee Coordinator for any Zigbee 4.0 that are usiing the new "Suzi" Sub-GHz standard (which I understand is more or just standard Zigbee that only uses a different freqency range, so in theory such could only co-excist on the same Zigbee network if the Zigbee Coordinator supported both frequency ranges at the same time.)

    And for the record, a lot more people (including myself) ahve asked or requested same thing for ZHA in the past:

    Again, a directly related HA feature request is instead the ability to run more than one instance of the ZHA integration:

    PS: This might get part-way resolved if the ZHA component was out of Home Assistant's Core and into its own app, see:

  4. MattWestb commented on Nov 10, 2026

    @MattWestb
    MattWestb
    on Nov 10, 2026

    For information is our Puddly and one more digger testing TREL-like (Thread) pipes with UDP datagrams for low latency with multiple encryption Ethernet links for one Zigbee network with multiple radios.

    zigpy/ziggurat#91

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Feature

    Fields

    Priority

    None yet

    Size

    None yet

    Area

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions