I am currently running Homeassistant on a RPi4 with a ConbeeII-stick. To integrate my Zigbeedevices I have IKEA-lights connected directly to IKEA-gateway. For some few Hue-lights I have integrated the Philips Hue gateway. And the rest (e.g. Xiaomi motion sensors) are connected via ConbeeII and Deconz.
BUT, maybe better to integrate all devices to ConbeeII and Deconz instead? Is that a more stable integration? And of course less risk of channel interference. But no firmware updates?
So that would be a better choice than ConbeeII and Deconz?
IMO, YES! But do your own research.
1 Like
OK, I will check⦠In any case I believe going for ONE Zigbee coordinator would simplify things, I hope. As long as the integrations are equally stable as the native corrdinators from Ikea and Philips.
Thanks for your tip!
1 Like
This is the coordinator that Iβm currently using with Zigbee2MQTT. I have 83 devices and everything is rock solid.
OK. Will have a look. Thanks!
I recommend (based on my own experience) using a dedicated Zigbee2MQTT installation aside Home Assistant and pick the MQTT integration in Home Assistant.
As for the coordinator device, I use a CC2652RB based USB-Dongle in one location and a Raspbee II on the other. The range and reliability of the CC2652RB is better than the Raspbee II, though the Raspbee II has the benefit of more compactness. You could combine benefits by using a CC2652P2 Raspberry Hat (like ZigBee CC2652P2 Raspberry Pi Module).
Location 1: Raspbee II, 11.000m2 outdoor, ~80 devices, light bulbs (IKEA, Innr, Hue), motion sensors (Hue), smart sockets (Innr)
Location 2: CC2652RB, 120mΒ² indoor, ~15 devices, light bulbs (Hue), LED strips (Hue, Innr), motion sensors (Hue) smart sockets (Blitzwolf) flush mount actors (Sonoff, iCasa)
1 Like
Just curious.
In my mind Z-Wave & Zigbee are competing mesh network standards with similar functionality & goals. My understanding with Z-Wave here is that it was determined that using MQTT to interface Z-Wave devices was too limiting, That is why rhe zwavejs integration uses websockets.
Doesnβt zigbee2mqtt have the same limitations compared to other contenders such as `zha ?
With the newer firmwareβs, 2 coordinator setups IMO is going to be obsolete
I am regularly confronted with the limitations of my growing zigbee setup (Conbee 2 plus dozens of aqara sensors, Osram plugs, Hue lights and Tradfri devices) and am very interested in the notion of double coordinators. Do you have a write up of how you made this work a relative noob like myself could profit from?
In my mind Z-Wave & Zigbee are competing mesh network standards with similar functionality & goals.
Correct. And they use different frequencies which penetrate solid material (like concrete or stone) differently.
My understanding with Z-Wave here is that it was determined that using MQTT to interface Z-Wave devices was too limiting, That is why rhe
zwavejsintegration uses websockets.
MQTT is just a message bus that transports events and data from publishers to subscribers. It is not related to either Z-WAVE or Zigbee but a widely used industry standard. Instead of connecting directly to Home Assistant, you get reliable, fault tolerant messaging with MQTT for free.
Zigbee2MQTT is Home Assistant agnostic, but supports message format and contents understood by Home Assistantβs MQTT integration. You add a device to your Zigbee2MQTT controlled network and it appears immediatly in Home Assistant.
2 Likes
The recommended way of using that it to use the builtin websockets server & the zwavejs Integration. zwavejs2mqtt basically becomes a control panel interface for zwavejs. In fact, that is what i am running, with MQTT disabled.
I believe @frenck tried something similar with OZW and then, I think, zwavejs2mqtt before the websockets server was chosen at the preferred solution. It would be great if he can weigh in on why MQTT is not recommended for Z-Wave with HA.
I donβt expect him to say that, he might say that using WebSockets was easier / quicker to integrate ZWave to Home Assistant.