ok, yes not possible if they are on different networks (coordinators)
Eh… no, that’s not how it works.
Adding routers doesn’t magically improve the quality of all links. What it does is potentially provide devices with more options, some of which are likely “better” than others (stronger signal, lower latency, less hops, etc).
It also can cause more traffic if you use Zigbee groups.
1 Like
More options are not per definition better, but too few too far apart isn’t going to help. I’ve seen plenty people with 30+ battery operated sensors and barely any routers. Thaking routers out of such a mesh will definitely be a problem.
Sorry , have no idea what you mean, why not say directly what’s your concern ?
It Don’t have anything with OP’s question, the 50 devices you can devide however your want, into to different Coordinators, as i said i have 2 on same OpenFloorplan
ok, i only have (currently paired) 14 battery operated sensors, spread out on 3 floorplans, 100sqm each, (and 1 in the fridge ) 
, Coordinator, on mid-plan ( 7 meters from the other Coordinator ) … AND no router, on this net, so it’s not a mesh, actually i have no mesh, as long as it works it works, why add a router ?,
That is true, but most people I know won’t have such luck due to a lot of concrete walls riddled with metal bars. But indeed, if it works, it works. But in your case adding an extra coördinator in an adjacent building to put in some more sensors or lights wouldn’t be a problem either, which was kind of what I was trying to say.
Right, im actually planning on an additional zigbee coordinator in basement, for heating system, and the " garage" have it own Ethernet-switch for 2 outside cams etc. wired to House-Router, 1 zigbee temp ( of the 14 ) , after +6 month battery still above 80%, and only 1 reports Poor signal (for some reason), in regards to battery-life, it seems like the overall location temperature, is a bigger factor than signal-strength, or in fact most important factor, fridge/outdoor/garage/
And yes, im living in a wooden-house, no disturbing neighbor-signal … hardly no phone-signals either 
EDIT: Poor = 60
EDIT2: And above Poor, is in far-end corner of basement, and from Coordinator, so beside the floorplan + 1 wall, it’s actually Pan-room, so bricked walls / fireproofed roof, but it reports temperature, and wifi-cam + 2 wifi plugs
hmmm, Makes me think, maybe i should try to move it, as i just dropped it on the shelf, between the cam and the 2 pluggs
And yes i do understand, or it seems like i have luck in this matter, … maybe
I have a similar et up to you.
How does flashing a Sonoff bridge with Tasmota allow you to increase the mesh via ethernet?
Have you considered running some outside zigbee lights - you can ever get them in 12/24V
I think some are repeaters ??
Thanks
read the thread → it doesn’t.
1 Like
In theory, it should be possible to create some kind of hardware zigbee receiver imitating a zigbee router and connect it to a home zigbee network. And in the garage start the second device functioning as a transmitter. Bidirectionally connected to each other via the IP protocol. Someone smart would surely be able to do it 
A lot of Zigbee vendors, and no one ever thought of that.
1 Like
After reading this thread, I realized Ethernet cannot be used in the way that a Zigbee router can to extend the reach of the network and the way I use BLE gateways to transport BLE advertisements to Home Assistant over Ethernet.
I thought of a different application and was wondering if it was realistic. If I were to use something like a PoE TubeZB as a Zigbee coordinator, could I implement a highly available Zigbee network by running two instances of Home Assistant in an active/standby setup so only one talks to the coordinator at a time? Or would that need to be supported by the coordinator firmware?
1 Like
It’s not clear how you use BLE gateways to transport BLE advertisements to Home Assistant over Ethernet, but the Smlight SLZB-06s functions over ethernet and will extend the reach of a network.
You’d need both to have the same IEEE address, and for the one not in use to be powered down.
Those are coordinators though, not ethernet connected routers.
I use two methods for BLE. One is devices flashed with Tasmota running a script called Blerry over Berry that converts certain BLE advertisements from supported devices to MQTT messages. The other is devices flashed with ESPhome Bluetooth Proxy where they send all advertisements to HA which aggregates them (proxies and USB dongles), removes duplicates etc and sends them to BLE device integrations.
Backhaul can be done over WiFi or, preferably, wired Ethernet.
I will look at the SLZB-06
Makes sense. So not hot standby but a cold standby with manual switchover. Could be a relatively fast operation if using VMs for the HA instances.
I wonder how long it takes for Ethernet switches to realize the MAC address is now in a different location in the Layer 2 network topology
I will buy one of these coordinators and try this. In the interim, I will move my HA instance to a Proxmox VM and clone it and try an experiment with my USB coordinator.
Thanks.
It’s the Zigbee IEEE address that needs to be the same, not the Ethernet MAC
Received my SLZB-06M and trying it first as a coordinator over Ethernet with the ZHA integration alongside with my Z2M and its USB based coordinator.
Of course it’s possible, just needs someone to design it and build, likely not enough of a demand to make it worth while unless someone wanted to take it up as a project. Would require two master/slaves though.