# How to pair thread device with latest firmware? **URL:** \ **Category:** Devices\ **Tags:** homey-pro\ **Created:** [January 11, 2024, 9:18am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766 "2024-01-11T09:18:40Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Udo\_Baumann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/udo_baumann/32/79398_2.png) [@Udo\_Baumann](https://community.homey.app/u/Udo_Baumann)\ **Post date:** [January 11, 2024, 9:18am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/1 "2024-01-11T09:18:40Z")
Hi Community, I do have these nanoleaf bulbs. Thread & Bluetooth. [https://nanoleaf.me/en-EU/products/essentials/bulbs/?category=A60-E27&standard=homekit&size=each](https://nanoleaf.me/en-EU/products/essentials/bulbs/?category=A60-E27&standard=homekit&size=each) I thought that as soon as “Thread” is enabled I am able to pair them with my homey pro 2023. The firmware changelog states: **Thread** Enables Homey Pro’s Thread radio. Additionally when adding a device an selecting homey it still says only: Infrared, Matter, Z-Wave, Zigbee. Where is the “Thread” option? Or did I misunderstood what “Thread” implementation means on homey? Thanks! ---
**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:** [January 11, 2024, 9:24am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/2 "2024-01-11T09:24:11Z")
> **[Thread for Homey Pro (Early 2023)](https://support.homey.app/hc/en-us/articles/12010766903580)** > > Since firmware version 10.3.0, Homey Pro (Early 2023) has enabled its Thread radio. This article will briefly explain what Thread is and how you can connect a Matter over Thread device to Homey Pro... ---
**Author:** ![Udo\_Baumann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/udo_baumann/32/79398_2.png) [@Udo\_Baumann](https://community.homey.app/u/Udo_Baumann)\ **Post date:** [January 11, 2024, 9:27am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/3 "2024-01-11T09:27:33Z")
Thanks for your quick response. Just let me confirm; although thread radio is enabled you will not support devices such as the one mentioned above? ---
**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:** [January 11, 2024, 9:29am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/4 "2024-01-11T09:29:59Z")
Have you tried? ---
**Author:** ![Udo\_Baumann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/udo_baumann/32/79398_2.png) [@Udo\_Baumann](https://community.homey.app/u/Udo_Baumann)\ **Post date:** [January 11, 2024, 9:36am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/5 "2024-01-11T09:36:51Z")
Yes I did. Actually I have 2 different kinds of these devices. One which is matter labeled with a 11 digit pairing code, I already added them to homey months ago. The second one are the once with thread/bluetooth (+ homekit compatibility), they have a 8-digit pairing code that is actually not working because the pairing interface requests 11 digits. However I thought now “Thread” is enabled and I can pair them. Any clue? Since I have 12 of these bulbs and need them. Although I do not have an Apple ecosystem maybe I can somehow enable homekit and pair them? Is there a workaround? ---
**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:** [January 11, 2024, 9:45am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/6 "2024-01-11T09:45:03Z")
> [@Udo\_Baumann](#): > > However I thought now “Thread” is enabled and I can pair them. The document I linked to explains several methods of pairing Thread devices with Homey… ---
**Author:** ![Udo\_Baumann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/udo_baumann/32/79398_2.png) [@Udo\_Baumann](https://community.homey.app/u/Udo_Baumann)\ **Post date:** [January 11, 2024, 10:05am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/7 "2024-01-11T10:05:49Z")
Thanks. Unlike the browser version I do see Thread settings in the Android app - I haven’t noticed before. When I open these settings I see this… ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/e/be02c80b5c24e4a89266567f182afb9870d92641.jpeg) I cannot change anything. How do I make Homey to be the main boarder router? And subsequently connect the Nanoleaf thread bulbs? Or, as soon as I enable Homey Boarder Router (how?) I can add thread devices? Thanks ---
**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\ **Post date:** [January 11, 2024, 10:14am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/8 "2024-01-11T10:14:35Z")
In the link that @robertklep shared, it is clearly stated that “Homey Pro only supports Thread devices that also use Matter.”, does your bulbs support Matter? ---
**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:** [January 11, 2024, 10:47am UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/9 "2024-01-11T10:47:31Z")
Stop focussing on trying to add a Thread device, just look at the document I linked to, it explains how to add Thread devices to Homey. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/9/39bdd914f01b32ac45dab45560fc21f541e5d0d1.png) ---
**Author:** ![Udo\_Baumann](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/udo_baumann/32/79398_2.png) [@Udo\_Baumann](https://community.homey.app/u/Udo_Baumann)\ **Post date:** [January 11, 2024, 12:06pm UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/10 "2024-01-11T12:06:17Z")
Dear Robert, Thanks for your feedback. Now I get that only “Thread over Matter” is supported atm. That is not obvious when looking at the connectivity options. “Thread” is shown as a separate functionality such as Z-Wave. Do you plan to integrate “Thread” that I can use my light balls in the same way I use them right now with Google Home (and its Border Router functionality)? (Edit: Let me add that my light bulbs have a Thread logo but no matter logo) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/7/e77837534a0adc040317f3aeff41fa5996e366a1.png) Thanks! ---
**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:** [January 11, 2024, 12:22pm UTC](https://community.homey.app/t/how-to-pair-thread-device-with-latest-firmware/100766/11 "2024-01-11T12:22:31Z")
> [@Udo\_Baumann](#): > > “Thread” is shown as a separate functionality such as Z-Wave. That’s because it _is_ a separate functionality. Matter support for Homey has existed for some time now, Thread support only since this week. > [@](#): > > Do you plan to integrate “Thread” that I can use my light balls in the same way I use them right now with Google Home (and its Border Router functionality)? From what I can see, the Nanoleaf lights come in two variants: HomeKit over Thread and Matter over Thread. Homey supports the latter, and I doubt it will support the former (it also explains that you have an 8-digit pairing code, because that’s a HomeKit code). FWIW, Homey _is_ a Thread border router with the new firmware.