The Short Answer: Visible Does Not Mean Unlocked
Thread is the low-power wireless network used by many new IKEA sensors. DIRIGERA is the border router—the bridge between that device network and your normal Ethernet or Wi-Fi home network. Thread credentials are the network password and settings that let another device or border router join.
Home Assistant discovers Thread border routers through a small local announcement. That is enough to show a network name under Settings > Devices & services > Thread, but the announcement does not include the private credentials. That is why DIRIGERA can appear under Other networks with no key icon.
If an IKEA Matter device is already joined to that network and you shared the device to Home Assistant, normal control can still work. The Matter controller relationship proves Home Assistant is allowed to control the device, while DIRIGERA routes the encrypted local traffic between Thread and your home network.
What to do now: if IKEA Home smart and Home Assistant both work, do nothing. If only IKEA works, create a temporary Matter sharing code and add the already-used device to Home Assistant. Reset nothing yet.
Why this works: a Thread border router carries local traffic, while a Matter controller relationship—often called a fabric—decides which platforms the device trusts. Home Assistant therefore does not need to own DIRIGERA’s Thread password merely to control a device that DIRIGERA already hosts and IKEA has shared through Matter.
Four Similar-Looking States That Mean Different Things
The easiest way to avoid an unnecessary reset is to separate discovery, Thread membership, and Matter control.
| What Home Assistant knows | What it means | What you can do |
|---|---|---|
| DIRIGERA network is visible | Home Assistant heard the hub’s local border-router announcement. | Recognize that the network exists. This alone does not let Home Assistant add devices to it. |
| A key icon appears | Home Assistant has the Thread operational credentials. | Make that network preferred, commission compatible Thread devices to it, or use the credentials with supported border-router tools. |
| An IKEA Matter device is in Home Assistant | The device has trusted Home Assistant as a Matter controller. | Control and automate the device locally as long as the IPv6 route through its Thread border router is healthy. |
| A Home Assistant border router joined the same mesh | A Yellow or dedicated ZBT radio is routing the same Thread network too. | Add coverage and resilience. This is optional and should be done only with a supported credential-sharing or border-router joining method. |
The third row is the one most households care about. A shared Matter device can work in Home Assistant even while the Thread page continues to show DIRIGERA without a key.
The Three Codes Are Not Interchangeable
IKEA, Matter, and Thread screens can all show QR or numeric codes. Treating them as one universal password is the most common source of confusion.
| Code | What it does | When to use it |
|---|---|---|
| Printed Matter setup code | Commissions a new or factory-reset device for its first Matter controller. | Use during a clean first setup. Do not assume the label can replace a fresh multi-admin code after the device is already in use. |
| Temporary Matter sharing code | Invites another platform, such as Home Assistant, into the device’s Matter fabric list. | Generate it in the app that already controls the device. This is the normal IKEA-first path and it expires. |
| Thread border-router join passcode | Lets another supported Thread 1.4 border router join an existing Thread mesh. | Use only when both products explicitly support that flow. It is not the Matter sharing code and is not needed for ordinary shared-device control. |
Recent Home Assistant Community reports describe DIRIGERA firmware that exposes a separate nine-digit border-router joining passcode. Other households report missing options or unsuccessful joins. IKEA and Home Assistant do not currently publish one universal DIRIGERA-to-Home-Assistant joining procedure, so consider this an advanced, version-dependent path—not a required fix for the missing key icon.
The Best Path for Most DIRIGERA Homes
If a native IKEA Matter-over-Thread device already works in the IKEA Home smart app, keep DIRIGERA as the Thread owner and share only that Matter device. This is the smallest, safest change. Older IKEA Zigbee products exposed through DIRIGERA’s Matter bridge use the hub’s bridge-sharing path instead; they do not have their own Matter setup or sharing code.
- Confirm the IKEA path first. Make sure DIRIGERA is powered, connected to the same trusted home network as Home Assistant, and still controls the device in IKEA Home smart.
- Open the device’s Matter sharing flow in IKEA Home smart. Generate a fresh code for connecting the already-used device to another smart-home platform. Menu wording can change between app versions.
- Start “Add Matter device” in the Home Assistant companion app. Choose the option for a device that is already in use, then scan or enter the temporary IKEA code.
- Test from both apps before building automations. If both work, the missing Thread key is only an ownership detail, not a fault.
- Choose one automation owner. Keep most routines in Home Assistant or in one other platform so the same light is not being turned on and off by duplicate schedules.
If device-level sharing is not offered, check its current IKEA firmware and Matter support before changing anything. A newer native Matter device should have its own Matter path. An older Zigbee device may instead appear as part of the DIRIGERA Matter bridge, so look for the hub’s connect-to-another-platform flow.
When Home Assistant Actually Needs the Credentials
The Thread credentials matter when you want Home Assistant to do more than control a device that DIRIGERA already hosts. You need a supported credential path when you want to:
- commission a new Thread device directly onto DIRIGERA’s existing Thread network from Home Assistant;
- mark DIRIGERA’s network as Home Assistant’s preferred Thread network;
- join a Home Assistant OpenThread border router to the same mesh for extra coverage; or
- move ownership away from DIRIGERA while preserving one carefully planned Thread network.
Home Assistant’s official Thread page currently explains how the companion app can import Thread credentials from Apple on iPhone and Google on Android. It does not promise that every third-party hub—including DIRIGERA—will export credentials into the phone in a form Home Assistant can import. Seeing the network name is not evidence that this import is available.
Do not copy random dataset strings or reset a healthy mesh to force this. Thread credentials grant network membership. Back them up only through documented tools, and join another border router only when you have a reason beyond changing an icon.
Do You Need a ZBT-2, ZBT-1, or Home Assistant Yellow?
No—not for the normal DIRIGERA-first path. If DIRIGERA routes the Thread device and Home Assistant controls it through Matter, another radio adds no required permission. It may add coverage only if it can join the same Thread mesh through a supported method.
A dedicated Home Assistant Thread radio makes sense when you want Home Assistant to own the Thread network, commission devices directly, or keep using Thread without DIRIGERA. Current concrete options include Home Assistant Yellow and a dedicated Home Assistant Connect ZBT-1 or ZBT-2 running OpenThread Border Router firmware. Plan that ownership before resetting accessories; creating a second unrelated Thread network does not strengthen devices that remain on DIRIGERA’s mesh.
Official Support, Local Control, and Cross-Platform Paths
This is the practical boundary for the products and connection choices discussed here.
| Path | Official support and hardware | Local control and cloud | Matter or HomeKit path | Main caveat |
|---|---|---|---|---|
| DIRIGERA-owned Thread | IKEA DIRIGERA hub, including IKEA article number 505.034.14, hosts supported IKEA devices; IKEA says the hub is recommended but not required for its new Matter devices. | Routine Matter traffic is local. Remote access, firmware delivery, and other online app services can still use the internet. | Share each supported Matter device from IKEA Home smart to Home Assistant, Apple Home, Google Home, Alexa, or SmartThings. | Home Assistant may discover the Thread network without receiving its credentials. That does not block an already-shared device. |
| Home Assistant-owned Thread | Home Assistant OS with the official Matter Server and OpenThread Border Router apps; Yellow or a dedicated ZBT-1/ZBT-2 supplies the radio. | Normal Matter control is local. Remote access and vendor-only updates remain separate choices. | Pair the Matter-over-Thread device to Home Assistant first, then use Matter multi-admin to share it outward. | Use a dedicated Thread radio. Do not expect a second independent mesh to extend DIRIGERA’s devices. |
| Apple or Google as another controller | Each platform still follows its own controller and hub rules; examples include HomePod mini or Apple TV 4K, and Nest Hub (2nd gen), Nest Wifi Pro, or Google TV Streamer. | Normal Matter commands can stay local; accounts, remote access, voice services, and some setup still use cloud services. | Use Matter multi-admin for the physical IKEA device. Home Assistant’s HomeKit Bridge is a separate way to expose Home Assistant entities to Apple Home. | Adding another Matter controller does not copy DIRIGERA’s Thread credentials or move the device to a different Thread mesh. |
If the Device Is Offline, Not Just Keyless
A missing key icon is harmless when control works. If the device is actually unavailable, diagnose the working layers in order:
- Test IKEA Home smart. If it also fails, check device power, battery, range, DIRIGERA power, and the IKEA-recommended recovery steps first.
- Update Home Assistant and the official Matter Server app. Matter Server 9.0, released in June 2026, moves Home Assistant to the newer matter.js stack and includes faster reconnects and automatic migration from the previous server.
- Confirm the Matter device still exists in Home Assistant. An empty Thread credential field is not the same as a missing Matter device or removed Home Assistant fabric.
- Keep DIRIGERA and Home Assistant on the same normal home network. Do not isolate one on guest Wi-Fi or a separate network segment. Matter uses local IPv6 addresses and nearby-device discovery, which these network boundaries can block even when both boxes have internet access.
- Restart one layer at a time. Restart DIRIGERA or Home Assistant, wait for the Thread network to settle, then test before changing anything else.
- Re-share before resetting. If IKEA still works but Home Assistant does not, remove and rebuild only Home Assistant’s Matter relationship when the apps allow it. Reset the one affected accessory only after reversible checks fail.
Home Assistant supports its bundled Matter Server on Home Assistant OS. A separately assembled Matter Server container can work for advanced users, but it is not the supported baseline for deciding whether DIRIGERA or Thread is at fault.
What Stays Local and What Still Uses the Cloud?
Once commissioned, Matter commands between Home Assistant and the IKEA device can stay inside the home. DIRIGERA forwards the local IPv6 traffic between Ethernet or Wi-Fi and Thread; it does not need to turn every light command into a cloud round trip.
That does not make every IKEA app feature offline-only. Remote access, software updates, product information, and other online services can still use the internet. Apple, Google, Alexa, and SmartThings likewise combine local Matter control with accounts, remote services, voice processing, and app synchronization. “Matter is local” describes the device-control path, not every service around it.
Tara’s Recommendation
If DIRIGERA appears without credentials but your shared devices work, stop there. Keep DIRIGERA powered, keep Home Assistant and the hub on the same trusted LAN, and run your automations from one chosen platform. Do not buy a radio or rebuild a Thread network merely to make the key icon appear.
Only pursue credential import or border-router joining when you deliberately want one larger Thread mesh or Home Assistant-owned commissioning—and only through a method documented for the software versions you actually have. The safe default is simple: share the Matter device, preserve the working Thread owner, and reset last.
Frequently Asked Questions
Why can Home Assistant see DIRIGERA’s Thread network but show no credentials?
Home Assistant discovered DIRIGERA’s local border-router announcement, but the hub did not give it the private Thread operational dataset. Discovery and possession of the network key are separate, so the missing key icon can be normal.
Does Home Assistant need DIRIGERA’s Thread credentials to control an IKEA Matter device?
Not when the device is already on DIRIGERA’s network and has been shared through Matter. Home Assistant needs its own Matter controller relationship and a working local IPv6 route through DIRIGERA, not necessarily a copy of the Thread key.
Is the temporary IKEA Matter sharing code the Thread password?
No. The temporary Matter code lets another platform become a controller of the device. Thread credentials let a device or border router join the Thread mesh. They solve different problems.
Do I need a Home Assistant Connect ZBT-2 if DIRIGERA already runs Thread?
No, not just to control devices already routed by DIRIGERA and shared to Home Assistant. Add a dedicated Home Assistant Thread radio only if you deliberately want Home Assistant to own or join a Thread network.
Should I reset DIRIGERA or its Matter devices to make the key icon appear?
No. If IKEA Home smart and Home Assistant both work, leave the mesh alone. If control fails, check Matter sharing, Matter Server, local IPv6, and discovery first. Reset only the affected accessory as a last resort, not the whole DIRIGERA network.