# Zigbee binding support?

**URL:** <https://community.homey.app/t/zigbee-binding-support/152981>\
**Category:** Off-Topic\
**Created:** [March 26, 2026, 2:04pm UTC](https://community.homey.app/t/zigbee-binding-support/152981 "2026-03-26T14:04:17Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Waldo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/waldo/32/115680_2.png) [@Waldo](https://community.homey.app/u/Waldo)\
**Post date:** [March 26, 2026, 2:04pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/1 "2026-03-26T14:04:17Z")

</div>

While poking around in the Homey developer tools today, I noticed something I don’t remember seeing before: a Bindings option when clicking the 3 dots. It shows source endpoint, cluster, target, and target endpoint, and there are options to add binding, restore bindings, and delete individual ones.

As far as I know, Homey has never officially supported Zigbee bindings (direct device-to-device communication without going through the hub). So either this has quietly been there for a while and I just never noticed, or this is a sign that proper binding support is on its way in a more meaningful form?

Has anyone else seen this? Would love to know if this is new or if I’ve just been blind this whole time. 😅

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/3/c37e04e9f595e42a1ce22f0a9fec71d7443f780e.png)

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [March 26, 2026, 2:10pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/2 "2026-03-26T14:10:54Z")

</div>

Like the [Tx/Rx stats](https://community.homey.app/t/zigbee-tx-and-rx-stats/152920), it was added in v12.13.0 or v13.0.0. Not sure though how to use the bindings-functionality. I also read somewhere this option was added in preparation for the planned Zigbee OTA update functionality.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [March 26, 2026, 10:01pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/3 "2026-03-26T22:01:51Z")

</div>

It might be possible the main reason it’s added is to be able to _ **undo** _ spontaneous bindings between, for example, Aqara and Ikea devices.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 27, 2026, 5:05am UTC](https://community.homey.app/t/zigbee-binding-support/152981/4 "2026-03-27T05:05:38Z")

</div>

I think the main reason for all the recent Zigbee changes is because LG wants better Zigbee support for their Thinq ON device. It’s rather suspicious that Zigbee on Homey hasn’t gotten any love for _many_ years, but now that the [Thinq ON has gotten Zigbee-certified recently](https://csa-iot.org/csa_product/lg-thinq-on/), things are quickly being added (possibly to Homey first, because Everyone Is A Tester™, before it gets rolled out to the ON).

---

<div class="post-metadata">

**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\
**Post date:** [March 27, 2026, 7:36am UTC](https://community.homey.app/t/zigbee-binding-support/152981/5 "2026-03-27T07:36:39Z")

</div>

While the reasoning may be suspicious, in the end it’s a welcome improvement Zigbee support is getting some love.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [March 27, 2026, 7:47pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/6 "2026-03-27T19:47:47Z")

</div>

Very well possible, and it’s about time 🤓  
I also noticed extended generic zigbee driver support:

 ![Screenshot_20260325_235544_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/a/ca2070f9522fb3726245274916b4cec01aeed032.jpeg)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 28, 2026, 5:20am UTC](https://community.homey.app/t/zigbee-binding-support/152981/7 "2026-03-28T05:20:00Z")

</div>

> [@Peter\_Kawa](#):
>
> I also noticed extended generic zigbee driver support:

Let’s just say that Athom, probably “encouraged” by LG, has finally seen the light.

Athom has been adamant since basically forever that generic device support is “bad”, and that  
device support should be implemented in separate apps. But this isn’t really sustainable in an environment where new devices pop up daily, and lots of apps are developed by community developers that, at some point, either stop working on their apps or are using vibe coding that, from what I’m seeing, requires an app to be in permanent test phase because it can break at any time.

Also, other platforms have had generic device support for a long time, and it’s _so_ much easier for the users (case in point: I’m working on a few DIY boards running Zigbee, and Z2M supports them out of the box because they use standard Zigbee clusters; for Homey, this would require making a specific app just for this particular board…).

So yes, good thing they finally saw the light, although much too late for me (also, this doesn’t fix the issues with the Zigbee hardware).

---

<div class="post-metadata">

**Author:** ![makleso6](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/makleso6/32/78907_2.png) [@makleso6](https://community.homey.app/u/makleso6)\
**Post date:** [May 6, 2026, 10:12pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/8 "2026-05-06T22:12:29Z")

</div>

> [@robertklep](#):
>
> So yes, good thing they finally saw the light, although much too late for me (also, this doesn’t fix the issues with the Zigbee hardware).

“When you mention ‘this doesn’t fix the issues with the Zigbee hardware,’ are you referring to the Zigbee radio/chip built into the Homey hub itself, or to hardware issues with third-party Zigbee devices from various manufacturers?”

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [May 7, 2026, 4:23am UTC](https://community.homey.app/t/zigbee-binding-support/152981/9 "2026-05-07T04:23:07Z")

</div>

> [@makleso6](#):
>
> are you referring to the Zigbee radio/chip built into the Homey hub itself

Yes.

---

<div class="post-metadata">

**Author:** ![makleso6](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/makleso6/32/78907_2.png) [@makleso6](https://community.homey.app/u/makleso6)\
**Post date:** [May 7, 2026, 10:43am UTC](https://community.homey.app/t/zigbee-binding-support/152981/10 "2026-05-07T10:43:35Z")

</div>

> [@robertklep](#):
>
> > [@makleso6](#):
> >
> > are you referring to the Zigbee radio/chip built into the Homey hub itself

> [@robertklep](#):
>
> Yes.

What wrong with it?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [May 7, 2026, 11:26am UTC](https://community.homey.app/t/zigbee-binding-support/152981/11 "2026-05-07T11:26:00Z")

</div>

Nobody in the world, apart from Athom, uses MultiPAN firmware anymore because of the issues it can cause.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [May 10, 2026, 1:28pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/12 "2026-05-10T13:28:22Z")

</div>

AFAIK SmartThings and IKEA DIRIGERA also use Multi-PAN?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [May 10, 2026, 2:48pm UTC](https://community.homey.app/t/zigbee-binding-support/152981/13 "2026-05-10T14:48:42Z")

</div>

I don’t know about SmartThings, but the Dirigera has two separate radio chips, one for Thread and one for Zigbee.
