CC2531 (BRIDGE/Gateway USB Zigbee)

4 minutes of reading

riprogra

Proconductor: various
Category: BRIDGE/Gateway ZigBee↔︎TCP/IP
Type: USB dongle
Technology: Wi-Fi / ZigBee
Installation difficulties: Media
Ease of use: Media
Availability: Amazon
Review review: 1.0

CC2531

"CC2531" it is a small and extremely cheap USB dongle which allows Raspberry Pi (or any traditional computer) to implement radio transmission / reception via proProtocol ZigBee. As you know, different promanufacturers have opted this procommunication protocol as standard of the profirst home automation solutions: is the case of the note line products Philips HUE, Xiaomi Aqara, Ikea TRÅDFRI and many others.

This component is particularly useful to solve a specific one proproblem: mounted on a computer and used in conjunction with a personale HUB (Home Assistant, Homebridge etc.), this module allows you to check different devices, of different proproducers, who use different declinations of the proProtocol ZigBee.

"CC2531"Makes available il proProtocol ZigBee to the operating environment of the computer that mounts it, thus transforming it (through the adoption of the software zigbee2mqtt) in a BRIDGE/Gateway ZigBee↔︎TCP/IP to all effects. This means that if you have home automation components based on ZigBee (which typically need, in order to be controlled, a "collector", a BRIDGE appunto) it will be possible check them directly - through HUB personal - without the need to implement the BRIDGE/Gateway solitamente proplace in havenamento.

As known, the adoption of components based on the excellent home automation standard ZigBee provides also the adoption of BRIDGE/Gateway Zigbee↔︎TCP/IP of the same line products (eg. Gateway Philips HUE to check the components of the same line), except in cases of interoperability (eg the existing possibility to check components ZigBee LUMI Aqara means Gateway Xiaomi Mijia) - as well as the forced use of app furnishings apposite provided by proproducers of gateway. The adoption of this type of component (together with its software counterpart) allows essentially to avoid the hateful vendor lock-in indirectly given by the adoption a BRIDGE/Gateway different for each line prodotti, among other things not always integrable with our loved ones HUB personal.

The component is sold as seen in the photo: naked, without any cover of protection.

In particular

This form connects via USB on the computer, after which it is managed by its software - calling counterpart zigbee2mqtt - which exposes communication APIs useful to the most common HUB personal to dialogue with it, then with the antenna, then with the components ZigBee connected. CC2531 is a component low consumption procast for coverage up to 200 meters (net of any obstacles), and is compatible with any computer equipped with a standard USB port.

Before you can use it, however, CC2531 It requires a proming one-time fee, which is time when installing a firmware appTeddy which allows the component to dialogue with its software counterpart, or the aforementioned zigbee2mqtt.

This procedura can essentially be carried out in two ways:

The first mode is the one that makes it less sensible the adoption of CC2531 with respect to its direct rival, ConBee II: the latter It costs more of CC2531, but if we add up the total cost of the necessary components to his reproming, then the disbursement is close to that required for the purchase of ConBee II (pronto use and overall easier to use, as well as more powerful in terms of radio signal). Otherwise, venturing to the riproming using directly and only the proprio Raspberry Pi (maybe on which ours is also running HUB home automation staff), then the adoption is certainly recommended, net of the following considerations.

The software zigbee2mqtt basically transforms communications to and from the components ZigBee in messages MQTT then usable by our personal home automation. MQTT is a prolight, fast and fairly elementary tocollo, but certainly requires a minimum of appuser statement to be understood and dominated. Ultimately, the adoption of CC2531 is recommended for users who want to save and have the ability to learn new things, in this case MQTT. To those who prefer something more immediate (but not for this reason not of value - indeed) we recommend the binomial deCONZ + ConBee.

CC2531 - Table

Domotics integrability

Let's see in which modes the majors personal HUBmanage to integrate zigbee2mqtt (and therefore the components ZigBee on it certificates):

HUBModalità di integrazione
Home Assistant
(distribution HASSIO)
Add-on dedicated (server zigbee2mqtt) + native MQTT component Home Assistant HASSIO. Once riproprogrammed the CC2531 antenna with the expected firmware, you need to run the server zigbee2mqtt; subsequently it is necessary to carry out the pairing of the components ZigBee with the CC2531 antenna, so that their communications are transformed from the server into MQTT messages. Finally, the MQTT component Home Assistant (thanks to the autodiscovery) will automatically recognize these new virtual MQTT devices, prothus seeing the definition of the corresponding entity. It is also possible to manually configure each accessory via MQTT.

GUIDE TO INTEGRATION

Home Assistant
(installed as applicativo)
Service (server) zigbee2mqtt + broker MQTT + native MQTT component Home Assistant. One time riproprogrammed the CC2531 antenna with the expected firmware, you need to run the server zigbee2mqtt; subsequently it is necessary to carry out the pairing of the components ZigBee with the CC2531 antenna, so that their communications are transformed from the server into MQTT messages. Finally, the MQTT component Home Assistant (thanks to the autodiscovery) will automatically recognize these new virtual MQTT devices, prothus seeing the definition of the corresponding entity. It is also possible to manually configure each accessory via MQTT.

GUIDE TO INTEGRATION

openHABService (server) zigbee2mqtt + broker MQTT + native MQTT component openHAB. One time riproprogrammed the CC2531 antenna with the expected firmware, you need to run the server zigbee2mqtt; subsequently it is necessary to carry out the pairing of the components ZigBee with the CC2531 antenna, so that their communications are transformed from the server into MQTT messages. Finally, the MQTT component of openHAB (thanks to the autodiscovery) will automatically recognize these new virtual MQTT devices, prothus seeing the definition of the corresponding entities.
DomoticzService (server) zigbee2mqtt Once riproprogrammed the CC2531 antenna with the expected firmware, you need to run the server zigbee2mqtt; subsequently it is necessary to carry out the pairing of the components ZigBee with the CC2531 antenna, so that their communications are transformed from the server into MQTT messages. Finally, the Domoticz MQTT component (thanks to the autodiscovery) will automatically recognize these new virtual MQTT devices, prothus seeing the definition of the corresponding entities.
HomebridgeRegardless of where Home is runningbridge, it is necessary to install the server zigbee2mqtt (the installations vary depending on the type of operating system that will host it) on the same computer or on a computer connected on the same LAN and perform the pairing of accessories ZigBee with the CC2531 antenna appropriately reprogrammated in the firmware. Subsequently it is necessary to use one of the many plugins available for the management of the MQTT (we recommend homebridge-mqttthing) and define the various accessories manually, one by one, starting from the MQTT messages prolearned from zigbee2mqtt.
HomeyThink about using CC2531 with Homey it wouldn't make any sense: Homey it's a personale HUB hardware equipped with antenna ZigBee and of a whole series of apps to integrate a huge variety of components ZigBee.

Compatibility

The complete list (and continuously updatednamento) of the devices ZigBee compatible with CC2531 +zigbee2mqtt is available here.

Availability and cost

CC2531 - BoA


Please comment below