Homey Pro 2023/2026 cannot add new IKEA Matter-over-Thread devices, while Apple Home works fine

Questions & Help
1

Hi everyone,

I’m experiencing an issue with Matter over Thread and have run out of ideas.

Current Setup

  • Homey Pro 2026
  • FRITZ!Box 7530 acting as DSL modem and DHCP server
  • ASUS BT8 as Wi-Fi router
  • Apple TV (latest generation) acting as Home Hub
  • iPhone 15 Pro and MacBook, both running the latest software versions
  • Homey Pro has already been updated to 13.3.0.RC14 for testing purposes

In addition, I have a dedicated 2.4 GHz IoT Wi-Fi network. I have already tested channels 1, 6, and 11.

Devices Already Integrated in Homey

  • 1 × Zigbee door/window sensor
  • 11 × IKEA Matter-over-Thread devices
  • 6 × Matter-over-WiFi devices (Meross)
  • 2 × Matter-over-WiFi devices (Govee)
  • Several Philips Hue lights
  • Ring cameras

Bildschirmfoto 2026-06-12 um 16.06.44
Bildschirmfoto 2026-06-12 um 16.06.441868×1025 166 KB

Problem

I am trying to add two new IKEA Matter-over-Thread devices:

  • 1 × MYGGBETT
  • 1 × BILRESA

Apple Home

Both devices can be added to Apple Home through the Apple TV without any issues and work immediately after pairing.

Homey Pro

When trying to add the devices through the IKEA app or directly through Homey (either via iOS or Homey itself), device discovery is very unreliable. The devices are only found in approximately 1 out of 10 attempts.

If a device is discovered, the setup process starts normally. However, when Homey tries to add the device to the Thread network, the process hangs indefinitely and eventually fails with an error stating that a connection to the Thread network could not be established.

Bildschirmfoto 2026-06-12 um 14.24.01
Bildschirmfoto 2026-06-12 um 14.24.011290×2796 163 KB
Bildschirmfoto 2026-06-12 um 14.24.43
Bildschirmfoto 2026-06-12 um 14.24.431290×2796 197 KB

Additional Possibly Related Issue

Since the device update feature was introduced in Homey, my IKEA Matter devices are shown as having available firmware updates. However, every update attempt fails.

The download and/or installation process never progresses beyond approximately 5% before aborting.

Because of this, I suspect that the issue may be related to Homey’s Thread implementation or its communication with the Thread network rather than the individual devices themselves.

Thread Network

IMG_9002
IMG_90021290×1391 101 KB

As far as I understand, the Apple TV is currently acting as a Thread Border Router, since all IKEA Matter-over-Thread devices can be added to Apple Home without any issues.

Could this be related to how Homey interacts with an existing Thread network, or is there a known issue with Homey joining or managing a Thread network that is already established by Apple Home?

FritzBox IPV6

Bildschirmfoto 2026-06-12 um 14.27.52
Bildschirmfoto 2026-06-12 um 14.27.52838×985 130 KB

ASUS BT 8 2,4 GHz Preferences

Bildschirmfoto 2026-06-12 um 15.13.03
Bildschirmfoto 2026-06-12 um 15.13.03767×719 74.3 KB

Troubleshooting Already Performed

  • Updated Homey to version 13.3.0.RC14
  • Reset both IKEA devices multiple times
  • Tested different 2.4 GHz Wi-Fi channels (1, 6, and 11)
  • Tried pairing through both iOS and directly through Homey

Since the devices can be added to Apple Home without any issues, I suspect the problem is related to Homey itself or its Matter-over-Thread implementation rather than the devices or the network in general.

Has anyone experienced something similar or has any idea what might be causing this issue?

Any help or suggestions would be greatly appreciated.

Cross-post

I have also posted this issue in a German Homey community forum (same content, in German):

-> Link German Issue

If there are any updates or useful findings there, I will summarize them here as well.

4

Same issue for me with Bilresa on a Homey Pro 2026. Stuck on trying to communicate with device during setup.

5

The v13.3.0-update of Homey OS (released today), might address this, given the following fix mentioned in the change log:

IMG_2712
IMG_27121467×304 40.2 KB

6

Can say it does not. I bought some Bilresa with dial yesterday and I can’t pair them to my homey at all. Not through homey, not through iOS.

I am particularly frustrated because some months ago I borrowed the exact same Bilresa from a friend to try it out and back then it worked perfectly. I have no idea what happened up in the meantime.

7

You might want to reach out to Athom support, so they can look into it:

8

You mean well but I doubt that will do much I’m afraid. This is a problem that many people are facing and there are many similar topics, for example:

or full search results: Search results for 'bilresa order:latest' - Homey Community Forum

9

Even more reason to report it to Athom :wink:. I assume that the more people report similar issues, the more attention it will get from them.

This forum is not monitored actively by them, and their official channel for reporting issues is via their support team.

I do understand your frustration of the non-working devices. In general, reporting issues via the official channel is the best bet to get it fixed.

10

I bet your issue is here.

The FRITZ!Box 7530 router isn’t able to send IPv6 into the Asus mesh and you have a double NAT issue.

About a year ago I had the same issue

I had a BT Home Hub as the top layer and a GLiNet Flint 2 for 2.4GHz separating IOT from my personal devices

When I removed the BT router and entered PPPoe into Flint2 making it my ISP router, every issue I had, cleared up overnight. IPv6 address wouldn’t drop off.

11

Is there really that big difference between ASUS BT and ASUS ZenWifi AX routers?

I’m running ASUS ZenWifi AX with mesh-network since few years, always IPv6 disabled and have no troubles running IKEA Matter over Thread.
Just curious…

12

Thread can’t run without IPv6 so it’s clearly enabled somewhere in your stack

13

Correct me if I’m wrong but Matter is not using Your WiFi network’s IPv6.

It’s using its own IP addressing from a Matter router (Homey, Google Home, Apple,…).

“Even if your router has public IPv6 disabled, Matter devices on your Wi-Fi will automatically self-assign link-local IPv6 addresses (starting with fe80::) to talk directly to each other.”

Matter does not require your main router to assign IPv6 addresses . Matter devices and controllers use autoconfigured link-local addresses (starting with fe80::) for local communication. For Matter over Thread, the Thread Border Router assigns the required IPv6 addresses and subnets for the mesh network.

I have never had IPv6 enabled anywhere on my network, turned of on my Mesh-routers from day 1.

So You don’t need IPv6 enabled on Your LAN.

14

Doubtful, because IPv6 is still required for Matter controllers to communicate with each other. The text you’re quoting also doesn’t say that Matter doesn’t need IPv6, it says that you don’t need to enable public IPv6, nor IPv6 address assignment.

15

Doubtful or not: Just checked: IPv6 is disabled on both of my ASUS routers.
If it’s managed by Homey or some of my Google Home devices isn’t clear though…

16

In routers, IPv6 support typically means “public IPv6 support” (so things like subnet delegation).

17

Strange… None of devices on my LAN is using IPv6.
And just to clarify, My PiHole’s (used for DNS & DHCP) setting for IPv6 is also disabled.

As far as I can see my routers WiFi is not involved in IPv6 handling. I might be wrong but IF they were used, shouldn’t either router or PiHole show that in the logs or reservations?

As Gemini explains it:

The Thread Border Router generates its own independent local IPv6 network for the Thread devices.
It then bridges that traffic over to your main Wi-Fi router’s IPv6 network so your phone can control them

So the IPv6 should be managed by Homey then? Or have I misinterpreted it totally?

18

All the devices in your network that handle Matter will be using IPv6. But IPv6 is very different when compared to IPv4, especially when it comes down to things like IP address delegation (DHCP, or rather DHCPv6, is typically not used in an IPv6 network). DNS will be done over IPv4, hence nothing to show in PiHole logs.

Your Homey will be using IPv6 to talk to your TBR’s and other Matter controllers (if you have any), even though the developer tools don’t show that it’s using IPv6. It, and/or other TBR’s, will also create a separate IPv6 network that will be used by the Thread devices it manages.

19

I see what You men.
But correct me if I’m wrong:

You do not have to have IPv6 enabled on Your WiFi router, Homey (or other Matter Router) handles that for Your Matter devices.

20

Yes, but that doesn’t mean that IPv6 isn’t being used. Like I said, enabling IPv6 on your router means something different than “only now can your local devices use IPv6”.

21

IPv6 is needed for thread. Check IP in the matter menu in dev tool in homey