Deploy Now

Stars

15,786

Forks

2,159

Watchers

203

Developer links

Zigbee2MQTT

Zigbee2MQTT bridges a Zigbee smart home network to MQTT so bulbs, switches, sensors, and locks from hundreds of vendors work with your own automation server instead of each manufacturer's cloud bridge. It supports 5,798 devices from 608 vendors, so a Philips Hue bulb, an IKEA TRÅDFRI switch, an Aqara sensor, and a Tuya plug can all join one coordinator and speak one protocol. The built-in frontend on port 8080 shows every paired device with its link quality, battery level, and live state, and lets you rename, reconfigure, bind, or remove devices without editing YAML. A network map view charts which routers carry traffic for which end devices, making weak spots and dead zones visible before automations start failing. Groups collect devices that should act together, scenes capture lighting states for a room, and bindings let a switch talk directly to a bulb even when the server is briefly offline. Firmware stays current through over the air updates you can trigger or schedule per device from MQTT topics or the frontend, including downgrades when a new release misbehaves. Home Assistant picks everything up automatically through MQTT discovery, while openHAB, Domoticz, and Node-RED flows subscribe to the same plain JSON topics. The coordinator plugs into the host by USB or joins over the local network, while the bridge, frontend, and broker traffic run headlessly beside Mosquitto or EMQX. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Zigbee2MQTT
Zigbee2MQTT
Zigbee2MQTT
Zigbee2MQTT
Zigbee2MQTT

Benefits

  • One Coordinator, Every Vendor
  • A single Zigbee coordinator replaces the separate Hue, IKEA, Tuya, and Aqara hubs, because 5,798 supported devices from 608 vendors all pair to the same bridge.
  • Local Control, No Clouds
  • Commands and sensor readings travel between your devices and your own MQTT broker on your network, so lights and sensors keep responding when a vendor cloud has an outage.
  • Frontend Replaces Configuration Files
  • Pairing, renaming, binding, groups, scenes, and firmware updates happen in the web frontend on port 8080, with authentication and optional HTTPS, instead of hand-edited YAML and bridge restarts.
  • Any Automation Platform Connects
  • Home Assistant discovers devices automatically over MQTT, and openHAB, Domoticz, Node-RED, or your own scripts subscribe to the same readable JSON topics, so the bridge outlives any one platform.

Features

  • Web Frontend Dashboard
  • Devices, groups, network map, logs, and settings render in a browser UI on port 8080, with token authentication, optional HTTPS certificates, and a choice of frontend packages.
  • OTA Firmware Updates
  • Check, install, schedule, or roll back device firmware over the air from the frontend or bridge/request/device/ota_update MQTT topics, per device and without removing it from the wall.
  • Groups, Scenes, Bindings
  • Group bulbs across rooms, store lighting scenes, and bind switches directly to lights so basic control keeps working even while the automation server is rebooting.
  • Home Assistant Discovery
  • MQTT discovery publishes devices to Home Assistant automatically with device registry entries, availability tracking, and customizable payloads; legacy discovery and device triggers are also supported.
  • Multi-Coordinator Network Support
  • Coordinators connect over USB serial or TCP network adapters, including Ethernet Zigbee coordinators, so the bridge can run on a server away from the devices it controls.

Apps Similar to Zigbee2MQTT