-
Notifications
You must be signed in to change notification settings - Fork 508
Pairing Devices
Erik Baauw edited this page Nov 2, 2018
·
13 revisions
Pairing devices to deCONZ typically involves four steps:
- Joining the ZigBee network formed by the RaspBee or ConBee;
- Creating the REST API resources to expose the device;
- Configuring the device;
- Setting up the device in your applications (Phoscon, old web app, plugin for homebridge, Home Assistant, Domotic, ...).
How devices participate a ZigBee network depends on the type of device:
- ZigBee routers (typically mains-powered devices) connect to multiple neighbouring routers, forming the mesh network. The coordinator (RaspBee or ConBee) is a router (with additional functionality). Routers are coloured yellow in the deCONZ GUI (the coordinator is blue). The radio of a router is always on (as long as the device is powered);
- ZigBee end devices (typically battery-powered devices) connect to a single parent router (or the coordinator). End-devices are coloured grey in the deCONZ GUI. Typically, the radio of an end-device is off most of the time. Requests to the device are sent to its parent, who caches the request (for like 7 seconds). When the device wakes, it polls its parent for any pending requests. Some devices (e.g. the Hue motion sensor) poll their parent very often, appearing to be reachable all the time, others (e.g. most Xiaomi end devices) only poll once an hour. Some devices poll shortly after sending a report, some (again, most Xiaomi end devices) only poll at fixed intervals. See End Device Polling for more details.
Home Remember : Not all devices listed here are supported by deconz.