Matter onboarding IKEA MYGGBETT fails with “Er is iets misgegaan. Maak verbinding met je netwerk” while Thread & Matter server are OK

[dennidoubles]

The problem

I am trying to (re)onboard an IKEA MYGGBETT door/window sensor (Matter over Thread) to my Home Assistant installation.
This device has worked before on the same system, but at some point it became “Unavailable” in Home Assistant, and since then I have been unable to commission it again via Matter.

Important context:

The same MYGGBETT sensors work fine on a friend’s Home Assistant setup.

They pair there via Apple/Google and then appear in his HA within seconds.

On my setup, Thread now works (OTBR is leader) and the Matter Server runs without startup errors, but the HA Companion app aborts commissioning with:

“Something went wrong. Connect to your network and try again.”

During this failure, there are no new commissioning‑related log entries in the Matter Server logs, and the OTBR log only shows dropped radio frames (NonLowpanDataFrame) from a node.

This feels like a bug/edge case in Home Assistant’s Matter commissioning flow on my particular platform/fabric, rather than a problem with the MYGGBETT hardware or IKEA’s implementation.

Environment
Hardware: HP Thin Client T631 (generic x86‑64)

Home Assistant OS: 17.1

Home Assistant Core: 2026.2.3

Supervisor: 2026.02.3

OpenThread Border Router add-on: 2.16.5

Thread Border Router radio: Nabu Casa ZBT‑2

Matter Server add-on: 8.2.2

Home Assistant Companion app configuration (Android):

Internal URL set to: http://192.168.0.11:8123

Home network: SSID of my Wi‑Fi added

Cloud connection status: “connected”, but local access is via the internal URL.

Phone and HA are on the same LAN/VLAN, no VPN, no guest Wi‑Fi.

Background / prior issues
Matter and the MYGGBETT sensor have worked on this setup before.

At some point the device became “Unavailable” in HA.

In the Matter Server logs I then saw timeouts and issues while removing Node 1 / the old fabric.

I also had a prior problem with the OTBR add-on:

platformConfigureTunDevice() at netif.cpp:2043: Device or resource busy

otbr-agent exited with code 5, which caused the OTBR container to stop.

After a full host reboot, this is resolved; OTBR now runs stably as Thread leader.

Since then, I am trying to re‑commission the MYGGBETT, but the Matter onboarding in HA keeps failing.

Question
Do you have an idea why Matter onboarding of IKEA MYGGBETT fails on my setup with the app error:

“Something went wrong. Connect to your network and try again”

while:

The Companion app uses the internal URL on the same LAN,

Thread (OTBR + ZBT‑2) and Matter Server are healthy,

And Matter Server logs show no commissioning activity at all during the attempt?

Is this a known bug or edge case related to:

HA OS 17.1 on generic‑x86‑64 (HP Thin Client),

The ZBT‑2 OTBR add-on,

Or a “dirty” Matter fabric state after removing the old node?

I am happy to provide more logs or run a debug build if needed.

Thanks in advance!

What version of Home Assistant Core has the issue?

2026.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

core_matter_server_2026-02-27T14-56-29.352Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Current Thread / OTBR status
OTBR starts correctly and becomes leader of the Thread network. Log snippet:

[14:44:39] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/serial/by-id/usb-Nabu_Casa_ZBT-2_DCB4D90E58B0-if00?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp1s0
[NOTE]-ILS-----: Infra link selected: enp1s0
49d.17:03:43.519 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.036 [N] RoutingManager: BR ULA prefix: fdc5:363:20b8::/48 (loaded)
00:00:00.038 [N] RoutingManager: Local on-link prefix: fd7e:243a:c432:a7a3::/64
00:00:00.088 [N] Mle-----------: Role disabled -> detached
00:00:00.136 [N] P-Netif-------: Changing interface state to up.
...
00:00:33.954 [N] RouterTable---: Allocate router id 58
00:00:33.956 [N] Mle-----------: Role detached -> leader
00:00:33.958 [N] Mle-----------: Partition ID 0x7b7d3b17

Additional information

During the recent attempts to onboard MYGGBETT, I also see:

00:19:08.810 [N] MeshForwarder-: Dropping rx frame, aError:NonLowpanDataFrame, len:35, seqnum:5, type:Data, src:103597000088620c, dst:0xffff, sec:no, ackreq:no, radio:15.4
00:19:10.815 [N] MeshForwarder-: Dropping rx frame, aError:NonLowpanDataFrame, len:35, seqnum:13, type:Data, src:103597000088620c, dst:0xffff, sec:no, ackreq:no, radio:15.4
...
00:36:11.267 [N] MeshForwarder-: Dropping rx frame, aError:NonLowpanDataFrame, len:35, seqnum:45, type:Data, src:103597000088620c, dst:0xffff, sec:no, ackreq:no, radio:15.4

This suggests the Border Router does see 802.15.4 frames from a node (103597000088620c), but they are not accepted as valid Thread/6LoWPAN frames for the current network.

Current Matter Server status
Matter Server starts cleanly and runs without obvious errors. Log snippet:

[14:44:37] INFO: Starting Matter Server...
[14:44:38] INFO: Using Python Matter Server
[14:44:40] INFO: Using 'enp1s0' as primary network interface.
[14:44:41] INFO: Successfully send discovery information to Home Assistant.
2026-02-27 14:44:50.015 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2026-02-27 14:44:50.016 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
...
2026-02-27 14:44:54.019 (MainThread) INFO [matter_server.server.device_controller] Loaded 1 nodes from stored configuration
2026-02-27 14:44:54.037 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.

After that, I removed the old Matter device (Node 1, the “original” MYGGBETT) from HA. Matter log:

2026-02-27 14:49:50.555 (MainThread) INFO [matter_server.server.device_controller] Node:1 Node could not be discovered on the network, returning cached IP's
...
2026-02-27 14:51:50.118 (MainThread) INFO [matter_server.server.device_controller] Removing Node ID 1.
2026-02-27 14:51:50.118 (MainThread) INFO [matter_server.server.device_controller] Node ID 1 successfully removed from Matter server.
2026-02-27 14:52:21.130 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-02-27 14:52:35.130 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000001]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-02-27 14:52:35.130 (Dummy-2) CHIP_ERROR [chip.native.CTL] Remove Current Fabric Failed : src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-02-27 14:52:35.131 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to unpair device: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-02-27 14:52:35.133 (MainThread) WARNING [matter_server.server.device_controller] Removing current fabric from device failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout

Since removing Node 1, there are no new log entries in Matter Server at the moment I try to re‑commission MYGGBETT. That’s important: the commissioning attempt seems to fail before it even reaches the Matter Server.

Steps to reproduce (what I do now)
Factory reset MYGGBETT

Press and hold the system button for about 10 seconds until the red LED stops blinking.

After that, a yellow/white LED slowly fades in/out; according to documentation this indicates pairing mode (about 15 minutes).

In the Home Assistant Companion app (now using internal URL, phone on same Wi‑Fi/LAN):

Settings → Devices & Services → + Add device → Matter

Select “Add new device”

Scan the MYGGBETT QR code.

In the app I see:

“Searching for devices…”

Almost immediately: “Connecting to device”

Then: “Generating Matter credentials”

And finally the error message:

“Something went wrong. Connect to your network and try again.”

If I retry immediately, sometimes the “Generating Matter credentials” step is skipped; I just see short “Searching/Connecting” and then the same error again.

During all of this:

Matter Server logs do not show any new commissioning‑related events.

OTBR logs only show the “NonLowpanDataFrame” drops as above.

Things I believe are ruled out
App / network config:

Phone and HA are on the same LAN and SSID; internal URL is configured and working.

The Companion app works fine and is noticeably faster now that it uses the internal URL.

Device/firmware:

The same IKEA MYGGBETT sensor(s) work on a friend’s HA setup and via Apple/Google, so the hardware and firmware appear fine.

Thread / Matter backend:

OTBR is leader, Thread network appears in HA.

Matter Server initializes and runs without startup errors.

[home-assistant]

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign matter Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@dennidoubles Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20matter%22%20
_{^{(message by IssueContext)}}

---

matter documentation
matter source
_{^{(message by IssueLinks)}}

[uli-rpi]

The same issue here with 2 of 4 IKEA MYGGBETT, but maybe there is a general problem with IKEA Matter devices, see here
https://www.theverge.com/tech/873973/ikea-matter-thread-smart-home-connectivity-issues and https://www.iphone-ticker.de/ikea-bestaetigt-probleme-mit-neuen-matter-geraeten-272490/

[ttomas0520]

I'm facing with the same issue since this morning with one of my TIMMERFLOTTE sensor

2026-03-02 19:38:01.010 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:12893i with Node: <0000000000000000, 0> S:0 M:261399402] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4) 2026-03-02 19:38:25.493 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000000F, 1>. Current state was 1

[dennidoubles]

Update / resolution
I was finally able to successfully onboard 2 IKEA MYGGBETT door/window sensors via Matter over Thread and 2 WiZ Matter bulbs via Matter over WiFi.

The root cause on my setup turned out to be user error: I still had the Silicon Labs Multiprotocol add-on/ app running alongside the OpenThread Border Router (ZBT‑2). Both were trying to access the same radio, which caused intermittent Thread/Matter failures.
After completely removing the Silicon Labs Multiprotocol add-on and rebooting the host, OTBR comes up cleanly as leader, and Matter commissioning now works fine over both Wi‑Fi and Thread.
So this is not a Home Assistant bug, but a misconfiguration on my side.

KAJPLATS bulb still problematic, but that seems to be a known IKEA device issue, not HA‑core.

Thank you, and feel free to close this issue.