#matter device -- connected to ikea hub then shared to HA, is that correct?

1 messages · Page 1 of 1 (latest)

lean vigil
#

I got a couple of IKEA's new matter devices, and to setup the first one, I didn't see any obvious way of connecting it directly to Home Assistant, so I configured it into the IKEA Dirigera hub, then I used their "Connect" button to bring up a share code, and I added it to Home Assistant via the Matter Server->Commission Node->Commission Existing Device. (i see there is Commission Thread Device and Commission WiFi Device, but neither of those options are selectable)

Is this the correct way to set that up?

The device appeared, and worked for several minutes, and then stopped responding, so I want to make sure that I am connecting it properly ... but also, i do wonder if I need to reboot HA or the Dirigera or both to be able to get comm with the device back up

#

the device is still responding in the IKEA app... restarting the matter server in HA got it to respond again. Interesting.

lean vigil
#

looks like the matter server is completely bugged wrt these devices, it drops connection with them after 10-30 minutes, says it reconnects to them, but doesn't.

lean vigil
#

found how to add directly to HA, i'll test to see if that works any better ...

crimson spire
#

I am having similar issues with the devices dropping offline, and not updating button pushes/motion to Home Assistant. If you figure out a way to get it reliable, please pass it along.

lean vigil
#

ikea device specifically? shared from dirigera?

crimson spire
#

yes. They stay connected, but only update maybe every 10-20 minutes for a push of the Bilsrea button, and the new motion nevery updates to home assistant. I can see it working correctly in the Ikea app, but home assistant never sees the detected motion.

steel crater
#

Hmm, I got a bunch of IKEA's new matter devices recently, not having a dirigera hub or the IKEA App though. I just commissioned these devices directly to the HA matter controller via the built-in matter integration using the HA companion App.
I don't know if that is "proper" by your definition, but it is the way I would expect matter devices to behave. Every IKEA matter device has a matter code (on the device and in the accompanying printed product description) that you can directly use.

crimson spire
#

Boris, I think the question here is why do the devices become unresponsive when attached to home assistant thru the Dirigera hub, using Matter. It appears they work when they are woken from home assistant but restart their connection every 10-20 minutes. Testing using the Ikea app shows the Thread connection working; so something is either off in home assistant or the Dirigera matter portion. GameDev, have you gotten any more progress on finding how to get them to stay responsive?

lean vigil
#

@crimson spire i'm finding from a reddit thread about it that other people are having same issue with the motion detector, some are not. Doesn't matter if it's connected thru Dirigera or not.

#

I've connected the detector to HA, to Dirigera, and to Google Home, and Dirigera and Google Home do not drop out after 30 minutes idle, HA does. If I connect it to HA directly, it does. If I connect it to the others, then share it to HA it does. If I connect it to HA then share it to the others, then it still drops out of HA, and I can still see it working in Ikea or Google.

#

Matter Server logs a disconnect and reconnection attempt at the time it stops responding, and.. then just repeats that every 30 minutes until restarted.

crimson spire
#

Interesting. I could not get the motion to show up in my home assistant Matter connection to the Dirigera hub. I had to add the motion separately to the matter server. Is there a way to get the Dirigera matter connection to share the motion?

crimson spire
#

Or did I do this wrong in some other new way?

lean vigil
#

if you connected it to Dirigera first, in the Ikea app, select the device, then hit the Settings Wrench and then select Connect via QR Code, then you can add it to HA as an existing device

#

every which way I tried it, HA identified it exactly the same way, and even reconnected it to it's previous history, so i think it overall doesn't matter .. and the behavior was broken every way i tried it

steel crater
# lean vigil I've connected the detector to HA, to Dirigera, and to Google Home, and Dirigera...

Some questions:

  • Does your Google Home Matter controller come with a thread border router (e.g. Nest Hub Gen 2) and if so
  • Do your Border Routers (Google Home + Dirigera Hub) form separate or a single Thread Networks(s)?

Then:
What happens if you remove the device from all the Matter fabrics, factory reset it, and then in a first step only commision it to HA? (The crucial part here would be the reset, since it frees the device from the multi-admin fabrics internally)

Should that HA only connection work better/more stable: gradually share the device to IKEA (Dirigera Matter Controller) and then Google Home. Does that change the behavior?

Another approach: When your device becomes unavailable in HA:

  • Can you see the device announcements in the HA zeroconf browser? And if so
  • Can you ping the device at the announced IPv6 address? (like from a) your local computer and b) a terminal session to HA?)
#

In other words: mDNS problems and bad IPv6 RA processing can often be the cause of these kinds of problems. And these can be influenced in case multiple border routers don't share their thread networks, but create separate ones, eating bandwith from your 2.4GHz spectrum.

#

Oh, and what environment are you running your HA setup on: virtualized/containerized or native like on a Pi/Green/Yellow?

sonic nymph
lean vigil
# steel crater Some questions: - Does your Google Home Matter controller come with a thread bor...

i don't even know how i have a google home controller, when i scan the device on my phone, the phone automatically offered to join it to my google home 😄 i guess it's my phone?

I tried it connected only to HA, and the symptoms/problems were identical -- once it hits the 30 minute timer, it would say that it lost connection, reconnected, but ignore any further input from the sensor.

HA zeroconf browser?

There's a "Ping device" button on the device page in HA that shows that it is reachable

steel crater
#

You'll find the zeroconf browser at the /config/zeroconf path of your home assistant web url.

steel crater
#

In order to control matter devices you need a matter controller. These Google devices act as matter controller: Nest Hub (1st/2nd gen), Nest Hub Max, Nest Mini, Nest Audio, original Google Home/Mini speakers, Nest Wifi Pro, and the Google TV (4K) streamer. The Dirigera hub acts as a matter controller, and Home Assistant also acts as a matter controller. When you commission a matter device to a matter controller we say that the device joins a matter fabric. A single matter device can join up to five fabrics. When a device is joined to more than one fabric (multi-admin mode) it has to manage these fabric memberships separately. Many devices on the market have a bad multi-admin implementation and can at most join two fabrics before they behave strangely. When I asked you to factory reset your device and then only join HA, I wanted to make sure the device is in clean state, and make sure it doesn't suffer from a bad multi-admin implementation in that situation.
In addition to all that the IKEA devices use Thread as a transport layer, and hence a Thread border router (TBR) is needed. These Google devices act as TBR: est Hub (2nd gen), Nest Hub Max, Nest Wifi Pro, and the Chromecast with Google TV (4K model) (in addition to being matter controllers). Dirigera Hub acts as TBR, and HA can act as TBR. Usually each eco system (google, apple, samsung, ikea, HA) would create their own Thread networks, and manage them along with their matter controllers. But it doesn't have to be like that, specific combinations of TBRs can form a unified Thread mesh. This is desirable because when un-unified each Thread network will eat bandwidth from your precious 2.4GHz spectrum. The outcome in that case also is that it canbe hard to tell which device in which Matter fabric uses which Thread network.
All this can contribute to error states. So, fiddling with multiple fabrics and maybe even multiple TBR can make error analysis complicated in the first place, so reducing complexity

#

in the set-up can help. That's what I was aiming for with my questions.
Additionally, if your HA setup is virtualized/containerized this can contribute to the IPv6 RA not being processed correctly.

Now, all that said, it is really strange that your matter device is pingable while offline in your HA fabric...

crimson spire
#

So I can only speak to my setup, but this is my configuration: Devices pingable from home assistant, they only seem to come alive every 30ish minutes,

#

Home Assistant run from proxmox, but ipv6 turned on and available

#

The only Thread Border Router I have on network is the Digiera hub. I have no other thread radios to connect them to my HA instance

#

I am unsure if I could commission them into Home Assistant without going thru the Ikea app prior to bringing them into Home Assistant, though HA seems to see the Digirea as the prefered thread network, I still see no devices listed under the thread integration

violet fjord
#

I have the new IKEA Matter 2-Button controller and the ZBT-2 setup as my Thread Border Router. The error I get asks me to set up a TBR and then add the device.

steel crater
# crimson spire I am unsure if I could commission them into Home Assistant without going thru th...

You should be able to commission devices directly via the HA companion app if HA is able to get the network credentials from Dirigera. Afaik Dirigera implements credential sharing, I don't know if HA already does, though. If you see the Dirigera as preferred Network it should also show it as thread border router listed under preferred networks (you should see the network name and the border router as two items). You won't see any further Thread devices in the Thread integration (apart from the border routers), because this is handled in the orchestration layer, i.e. Matter.

crimson spire
#

Did some testing and found that I can push the button on the Bilresa thread device, and once I ping it from home assistant, the button push will register. It seems something is saving up the inputs and only passing them to home assistant once something wakes it. Not sure where the problem is, but I hope Ikea pushes new firmware to fix.

hollow wedge
#

Any news on this? I have around 20 IKEA matter devices that all behave the same way.

#

Here is a little bit of my logs:

#

After enabling debug logging I see this entry right after service restart:
2026-01-21 18:47:41.108 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
...
2026-01-21 18:49:33.837 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <0000000000000011, 1>. Current state was 3
2026-01-21 18:49:36.841 (MainThread) DEBUG [matter_server.server.sdk] Node:17 Establishing CASE session took 74.5 seconds
2026-01-21 18:49:36.841 (MainThread) INFO [matter_server.server.sdk] Node:17 Attempting to establish CASE session... (attempt 2 of 2)
2026-01-21 18:49:36.841 (MainThread) INFO [matter_server.server.sdk] Node:17 Attempting to establish CASE session... (attempt 2 of 2)
2026-01-21 18:51:05.833 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:54508i with Node: <0000000000000000, 0> S:0 M:170773129] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4)

#

Still no resolution though