-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Connect to multiple MQTT brokers/base topics #845
Comments
Just out of curiosity, what's the reason for having multiple Zigbee2MQTT instances? Would you be able to solve this with child bridges? |
There is a big problem with the Tuya ZY-M100-S accessories, those device spams the Zigbee Network with 10 status updates messages (with any changes) per second. This behaviour causes poor performance, response times, in the zigbee network affecting other devices. You can found here The 2nd reason is, for some big networks (more than 150 devices) is recommended to split in 2 separate Zigbee Networks. |
So, did the Child Bridge approach work for you? |
@itavero |
Same for me - I also have 3 instances of Z2M, also one for each separate floor. Thank you for your good advice, I also managed to create a separate child bridge for every instance/mqtt topic. However, I didn't manage to do so via the WebUI (is there any way at all?), so I did it through editing the JSON config. |
Problem description
I have 2 zigbee2mqtt instances running, each use a different base topic
Suggested solution
Will be great the ability of declare more than one "mqtt" sentence in the platform
Alternative solutions
Have another Homebridge instance running the z2m plugin with the 2nd zigbee2mqtt base topic
Additional context / information
No response
The text was updated successfully, but these errors were encountered: