So I’m trying to add the new Bilresa and Timmerflotte matter stuff from Ikea, but I’m absolutely stuck. My setup is an old Conbee II reflashed for thread. Then home assistant OS as VM in Proxmox and the main router as OPNsense virtualized on the same Proxmox box.
I get this far into adding one of them and the companion app shows this while the OTBR addon logs display this:
I can add devices that are matter over wifi. So at least the matter part should work. Also I’ve tried to do the commisioning on the same wifi, too as to not have inter-vlan routing during it. I can ping home assistant’s ipv6 address using my android too. Also the zeroconf tab shows the correct ipv6 address for both _meshcop._udp.local. and _matter._tcp.local. Also I’ve synced the thread keys multiple times.
Only thing i have left the problem could be is Proxmox fucking up the ipv6 packets somehow, the old Conbee II is just ass for some reason or I’ve set up something in home assistant wrong.
Same problem here but no solution. Also an old flashed Conbee-2 stick, same IKEA devices. No proxmox but RPI4 runnning core and Conbee on USB port. Same error message about cannot connect to thread network. I think ipv6 network is ok. I suspect the flashed Conbee stick. On my android phone i only see the thread network of my Google nest hub and it doesn’s show any other thread networks. I orderd a ZBT2 to troubleshoot this problem … see if its the Conbee.
It probably is. Been planning on deleting the whole matter/thread stack from HA and reflash the conbee II again just to be sure i didn’t make a configuration error. Also IPv6 works here as well, can see the multicast and ping the address so probably no problem there.
I have exactly the same setup, but use a ZBT-1 for Thread. It works flawlessly. Recently I added several Timmerflotte and Myggbett sensors via HA app. Also this worked flawlessly, even the firmware updates of Timmerflotte. Since then the sensors are rock solid without any issues. So, my guess would be the Conbee-2 causing your problem.
Replaced the Conbee with a ZBT-2, still no luck. I must be missing something, as you say you got it working. Good to know the new IKEA sensors should work with HA. Just curious, if you go to your android device and browse thread networks (Settings-> Google->All services->Thread networks), do you see the ha-thread network ?
Unfortunately, I don’t have an Android device. I use an iPhone, but no HomePod or comparable Thread border routers - the iPhone itself comes with Thread capabilities. But yes, my iPhone can “see” the ha-thread network and can also add its devices to Apple Home - including the Ikea devices previously added via HA app to the ha-thread network.
Glad to hear that and yeah it probably is. Thinking about getting something like an SMLIGHT SLZB-07 then putting it in thread mode, since i have one already as zigbee adapter and it works well.
Went an ordered the SMLIGHT SLZB-07 since it has the same radio chipset as the ZBT-01. Noticed the conbee II bugging when trying to flash it again, so the usb serial chip is probably busted or near it.
Can confirm after getting the SLZB-07 with the EFR32MG21 radio, thread now works perfectly and pairs. I just updated the stick using the SMLIGHT web flasher to openthread and now everything works 100% can pair both of the devices too without a hitch.
A word of advice if anyone comes across this: Don’t try to waste time with reflashing an old conbee II just get a new adapter, it’s going to save you so much time and sanity.
I also have no luck with the ZBT-2 and the Timmerflotte devices from IKEA. I have added the Kajplats light bulb and Myggspray motion sensor without issues so Matter/Thread are working and I can also connect IKEA hardware. So if anyone has any other solutions (other than changing the ZBT-2) please let me know.
OK. Yes very odd that you can’t add the Timmerflotte (as the other post above shows its possible). The only thing I can think of is check the Matter Logs to see if there is a hint of what maybe wrong.
I’m also trying to pair the Bilresa button with no luck. In my case I have Truenas Scale with HAOS as a VM. I can commision wifi matter devices and this is the first time I’m trying to pair a Thread device.
I have a SMLIGHT SLZB-MR4 as a Thread Border Router and I get this errors on Matter (HAOS Addon) Server logs:
2025-12-26 20:29:27.344 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 3.
2025-12-26 20:29:55.443 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3751i with Node: <0000000000000000, 0> S:0 M:111899254] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-12-26 20:29:57.363 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-12-26 20:30:32.290 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 35
2025-12-26 20:32:05.724 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3752i with Node: <0000000000000000, 0> S:0 M:111899265] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-12-26 20:32:31.094 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-12-26 20:32:55.676 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2025-12-26 20:33:23.475 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3760i with Node: <FFFFFFFB00000000, 0> S:14461 M:92222815] (S) Msg Retransmission to 0:FFFFFFFB00000000 failure (max retries:4)
2025-12-26 20:34:56.040 (Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'SendAttestationRequest': 'src/app/CommandSender.cpp:354: CHIP Error 0x00000032: Timeout'
2025-12-26 20:36:51.355 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3761i with Node: <FFFFFFFB00000000, 0> S:14461 M:92222827] (S) Msg Retransmission to 0:FFFFFFFB00000000 failure (max retries:4)
2025-12-26 20:37:15.192 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to commission: src/app/CommandSender.cpp:354: CHIP Error 0x00000032: Timeout
2025-12-26 20:37:15.193 (MainThread) ERROR [matter_server.server.client_handler] [140428601143952] Error while handling: commission_with_code: Commission with code failed for node 3.
2025-12-26 20:42:17.041 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 4.
2025-12-26 20:42:46.217 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3762i with Node: <0000000000000000, 0> S:0 M:111899272] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-12-26 20:42:47.049 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-12-26 20:43:22.232 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 64
2025-12-26 20:45:01.103 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3763i with Node: <0000000000000000, 0> S:0 M:111899283] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)
2025-12-26 20:45:21.003 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2025-12-26 20:45:44.990 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2025-12-26 20:46:13.296 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3772i with Node: <FFFFFFFB00000000, 0> S:14464 M:237368515] (S) Msg Retransmission to 0:FFFFFFFB00000000 failure (max retries:4)
2025-12-26 20:47:50.419 (Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'SendOpCertSigningRequest': 'src/app/CommandSender.cpp:354: CHIP Error 0x00000032: Timeout'
2025-12-26 20:49:42.662 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3773i with Node: <FFFFFFFB00000000, 0> S:14464 M:237368527] (S) Msg Retransmission to 0:FFFFFFFB00000000 failure (max retries:4)
2025-12-26 20:50:09.071 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to commission: src/app/CommandSender.cpp:354: CHIP Error 0x00000032: Timeout
2025-12-26 20:50:09.072 (MainThread) ERROR [matter_server.server.client_handler] [140428601143952] Error while handling: commission_with_code: Commission with code failed for node 4.
Plottwist, I took the other Timmerflotte from the packaging and that one paired instantly… Whilst never have been connected to anything I’ve factory reset the Timmerflotte (Press button on inside next to C°/F° for 10 seconds (see countdown on display)) and now it paired without problems.
I have the same problem none of the new Ikea matter devices are connecting to HA.
I have setup with a SLZB-MR1 and one with a ZBT-1 and both HA.
If anyone have some good ideas let me know.
I am also trying to connect the IKEA Bilresa and Timmerflotte to my Home Assistant. With my Android device I get a timeout. With my iPhone I get an error message saying that authorization failed.
At the moment, this is honestly quite frustrating.
@Ulrich72 , @ptrkp
Maybe this will help.
Below is a link to a writeup I did some time back. Although it is about adding a different kind of device, what might be helpful here is the “Prerequisites” section. I used an iOS based HA Companion App.
The issue was caused by IPv6 being disabled.
Since I do not use IPv6 in my local LAN, it was turned off, but Matter over Thread requires IPv6 to function correctly.
