Repository navigation
zigbee-bridge 0.1.0
The first release of zigbee-bridge: a Zigbee coordinator stack and Zigbee to MQTT bridge in Rust, as one static binary with no runtime, for Silicon Labs EmberZNet coordinators.
Status: early. Everything is tested in CI against a coordinator simulator, but this release has not been tested on real hardware yet. Keep a backup of your network, and please report how it goes on your coordinator.
What you can do with it
- Run a Zigbee network on a Silicon Labs coordinator with EmberZNet 7.4 to 8.x NCP firmware (Home Assistant Connect ZBT-1, Sonoff ZBDongle-E after a firmware update, SMLIGHT SLZB-06M/07, and other EFR32MG21/MG24 sticks), over USB serial or TCP.
- Pair devices with Zigbee 3.0 security: unique link keys, install codes, and a policy to require install codes or turn away pre-3.0 devices.
- See readings from any device that uses the standard clusters (temperature, humidity, pressure, illuminance, CO2, PM2.5, occupancy, contact, leak, smoke, power, energy, battery and more) on MQTT, and in Home Assistant through MQTT discovery.
- Switch lights and plugs, and set brightness and color temperature.
- Keep a backup of the network in the open coordinator backup format, and move it to a new coordinator without pairing devices again.
- Inspect the mesh: topology, neighbor tables, an energy scan.
- Ask a port what coordinator and firmware it has, read-only:
zigbee-bridge probe /dev/ttyUSB0.
Install
Static binaries for x86_64, aarch64 (Raspberry Pi 3 and newer, 64-bit OS) and mipsel (MT7621/MT7628 routers) are attached below, with SHA256SUMS. The quick start goes from download to a device in Home Assistant; the documentation covers installation as a service, configuration, every MQTT topic, and hardware.
Known limitations
- Silicon Labs EmberZNet only in this release. Texas Instruments Z-Stack and ConBee/RaspBee coordinators are done on
mainfor the next release; EmberZNet 7.3 and older is refused with a request to update the firmware. - Standard clusters only: devices that report through manufacturer-specific clusters (common with Tuya and Aqara) do not get state fields yet, though every report is published raw on
<device>/report. - No groups, scenes, binding requests or device firmware updates yet (firmware updates are on
main). - No TLS to the MQTT broker yet.
For developers
The stack is a set of library crates: zigbee-host (the coordinator), zigbee-zcl, zigbee-zdo, zigbee-ezsp, zigbee-ash, zigbee-types, and zigbee-sim, a coordinator simulator for testing without hardware. Depend on them by this tag; see the library guide.
Full list of changes: CHANGELOG.md.