Ongoing discussion about this feature can be found here: https://github.com/Koenkk/zigbee2mqtt/issues/782
Zigbee has support for binding which makes it possible that devices can directly control each other without the intervention of zigbee2mqtt or any home automation software.
When to use this #
A use case for this is e.g. the TRADFRI wireless dimmer. Binding the dimmer directly to a bulb or group has the following advantages:
- Smoothness; this will greatly improve the dimming feedback as the dimmer directly dims the bulb and thus does not have to make the MQTT/home automation software roundtrip.
- It will work even when home automation software, zigbee2mqtt or the coordinator is down.
Binding can be configured using the following topics:
TARGET_DEVICE_FRIENDLY_NAMEwill bind the source device to the target device or target group. In the above example, the TRADFRI wireless dimmer would be the source device and the bulb the target device. When using a group as target, using the group’s friendly name is mandatory, group ID will not work.
TARGET_DEVICE_FRIENDLY_NAMEwill unbind the devices.
Binding specific endpoint #
This is not applicable for most users
By default, the first endpoint is taken. In case your device has multiple endpoints, e.g.
right. The following can be done to specifcy an endpoint:
- Source: append the endpoint friendly name to the topic, e.g.
- Target: append the endpoint friendly name to the payload, e.g.
Binding a remote to a group #
Binding a remote to a group allows a remote to directly control a group of devices without intervention of Zigbee2mqtt.
When we for example have an IKEA E1743 remote called
my_remote and two bulbs called
bulb_2, we can control the 2 bulbs with the remote by putting them in the same group and binding the remote to it.
To do this execute the following steps:
- Create a new group in
configuration.yamland give it a
friendly_name(see Groups). In this example we will set the
- Add the 2 bulbs to the group by sending the following two MQTT messages.
- Bind the remote to the group by sending the following MQTT message. If this fails it might be because the remote is sleeping. This can be fixed by waking it up right before sending the MQTT message. To wake it up press a button on the remote.
Not all devices support this, it basically comes down to the Zigbee implementation of the device itself. Check the device specific page for more info (can be reached via the supported devices page)
When using this feature you are probably also interested in using the report feature. This allows you to get state changes when e.g. a bulb state changes by a bound dimmer. Read more about it here Report.