Hi!
I have 4 buildings that is about 50~60 meters apart from each other. These building are 100% concrete walls.
Inside the same building, I think I can use some power sockets to act as routers to repeat the signal between all rooms…but I don’y have any idea how to link all buildings in only one network in HA. Any idea how to do this?
I was thinking about using one coordinator in each building (LAN coordinator), but zigbee2mqtt only supports one instance, so I kind lost here.
Just for explanation: It’s a university, large rooms and 4 buildings. I’m planing to replace all light switchs by zigbee switchs and also add one IR repeater (broadlink) in each room for A/C control.
A Raspberry Pi in each building, with Zigbee2MQTT installed on each. Home assistant with 4 instances of the integration - each pointing to the IP address of one of the Pi’s.
That’s the easiest way. There is no limit to the number of instances of Zigbee2MQTT that Home Assistant can communicate with, using the websocket not the MQTT part.
I think you’re thinking of zwavejs2mqtt; there’s no zigbee2mqtt integration. OP can either just run separate zigbee2mqtt instances on a pi in each building (with a USB coordinator for each pi) all connecting to their MQTT broker which HA is also connected to, or separate instances on the HA host with LAN coordinators in each building.
Zigbee2mqtt has support for LAN coordinators?
We have a pool of servers for running VM’s (that’s were I’m running HA), so I was thinking about running different instances of Z2M and use LAN coordinatiors instead of running one Pi in each building.
About this setup (using multiple instances and only one MQTT with different topics), I think it’s a really good idea. Tks!
Ok thanks. I installed portainer and a second instance of Z2M but probably need to dwell some more inside the config to create all the files and correct mapping.
version: '3.8'
services:
zigbee2mqtt_b1:
container_name: zigbee2mqtt_b1
image: koenkk/zigbee2mqtt
restart: unless-stopped
volumes:
- ./data-b1:/app/data
- /run/udev:/run/udev:ro
ports:
# Frontend port
- 8081:8091
environment:
- TZ=America/Sao_Paulo
devices:
# Make sure this matched your adapter location
- /dev/null:/dev/ttyACM0
group_add:
- dialout
user: 1001:1001
zigbee2mqtt_b2:
container_name: zigbee2mqtt_b2
image: koenkk/zigbee2mqtt
restart: unless-stopped
volumes:
- ./data-b2:/app/data
- /run/udev:/run/udev:ro
ports:
# Frontend port
- 8082:8092
environment:
- TZ=America/Sao_Paulo
devices:
# Make sure this matched your adapter location
- /dev/null:/dev/ttyACM0
group_add:
- dialout
user: 1001:1001
Everything is located inside data-b1 and data-b2 folders…so I have totallt isolated configs/database.
Since I’m using network-based serial device (ZBridge with Tasmota), serial mapping doesn’t matter in this config.
Sorry for reactivating an old thread here. I’m trying to set up something, as I have an office down my garden. I’ve set up a second zigbee2mqtt connecting to the mqtt broker over the network, and changed the topic. But as far as I can see the HA mqtt through the GUI only supports one topic? Am I missing something, how do I get HA to discover the devices connected to the second zigbee2mqtt?
Trying to get 2 lan zigbee coordinators to work.
My setup:
1 intel nuc running home assistant, zigbee2mqtt and Mqtt.
All works fine connecting to a remote lan coordinator. All devices show up in home assistant.
Now I want to add a 2nd lan device. I use a raspberry pi running home assistant and installed zigbee2mqtt. Configuration wise I changed the base topic and pointed to my original nuc IP-adress to connect zigbee2mqtt to my main homeassistant.
Every time I do this all my zigbee devices which where originally present on my nuc get removed and only the raspberry zigbee devices are visible and working.
Ofcourse I do want to see all my zigbee devices…
Does this have to do with creating an automation which changes the basetopic? <— where can I find more details?
Is there maybe another issue?
Hi, thanks for your answers.
Personnaly my coordinators are on the same lan and (important) in the same room for test.
I follow your solution by writing in /opt/zigbee2mqtt/data/configuration.yaml →
homeassistant: true
permit_join: false
mqtt:
base_topic: zigbee2mqttnumber2
server: mqtt://homeassistant.local
user: xxxxxxxxxxx
password: xxxxxxxxxxxxx
but i have error when launching npm start →
Zigbee2MQTT:info 2022-06-19 12:52:44: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:error 2022-06-19 12:53:50: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-06-19 12:53:50: Failed to start zigbee
Zigbee2MQTT:error 2022-06-19 12:53:50: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2022-06-19 12:53:50: Exiting…
Zigbee2MQTT:error 2022-06-19 12:53:50: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby
The new second coordinator is in conflict with the wireless first zigbee lan. So i had setup another pan_id ext_and panid et channel in /opt/zigbee2mqtt/data/configuration.yaml (see Zigbee network | Zigbee2MQTT) →
advanced:
pan_id: 0x1b62
ext_pan_id: [0xCC, 0xCC, 0xCC, 0xCC, 0xCC, 0xCC, 0xCC, 0xCC]
channel: 15
Note that if you will have to change one of theese parameters in the futur you will get an error message. You have to delete /opt/zigbee2mqtt/data/coordinator_backup.json and restart
