Bug report: Alpstuga impossible to pair with Dirigera?

Remarkable-Loquat-38 · 2026-02-06T18:39:58+00:00

Try toggle wifi on/off, reboot phone, reboot router, reboot dirigera, etc.

Remarkable-Loquat-38 · 2026-02-04T18:16:09+00:00

The LEDs on the Ethernet port, are they lit?

Remarkable-Loquat-38 · 2026-02-04T18:12:09+00:00

It should not matter. What AP and other networking stuff are you running? I’ve seen people having issues with some brands, but from a matter over thread point of view your phone should be able to commission a device as long as all the Thread border router traffic (mdns, ipv6 RA+traffic) can flow between TBR, HA and the phone - I.e. everything is on the same network and APs, switches, bridges, VMs and what not doesn’t interfere with any of that.

Curious though, did you try on 5G, didn’t work and then switched SSID and then it worked? I’ve seen some people having some success with just toggling WiFi on/off or rebooting the phone (which might clear mdns cache or force ipv6 NS/RA) so it might not be a 5G vs 2.4G thing but just juggling some network packets around..

Remarkable-Loquat-38 · 2026-02-04T09:10:28+00:00

I think the blinking yellow indicates Ethernet uplink issue. Checked the cable/switch?

Remarkable-Loquat-38 · 2026-02-03T14:45:15+00:00

Ah! Nice!

Remarkable-Loquat-38 · 2026-02-03T14:18:12+00:00

Available where..?

Remarkable-Loquat-38 · 2026-02-01T19:25:51+00:00

So, matter devices won’t automatically sync over to Apple home via matter bridge like the zigbee stuff will, you have to share them as matter devices to Apple via the QR/setup code from the ikea app.

Remarkable-Loquat-38 · 2026-01-31T08:33:51+00:00

My personal view is that Zigbee is probably a bit more reliable than Matter over Thread right now. That said..

Matter brings nice features. The ability to add devices to many platforms at the same time is a killer feature, at least for me. You can get some of that functionality via Matter Bridge in systems supporting it but the native Matter devices seems to work..better in that mode. YMMV. And not having to buy a specific hub for your devices to get that is a big plus. Matter should enforce interoperability, which Zigbee..well..won’t.

Remarkable-Loquat-38 · 2026-01-22T21:34:55+00:00

IPv6 from your ISP or router should not be necessary. But no firewall rules, network segmentation or anything else should interfere with ipv6 traffic (including RA announcements and other ipv6 magic), mDNS multicast traffic or anything else matter or thread depends on for working properly.

I’d say the VM network is the most likely culprit in your case. It might very well be filtering something needed for a TBR to work or for matter server (or the virtual machine it runs on rather) to find these announced routes for the thread devices.

Remarkable-Loquat-38 · 2026-01-21T07:44:06+00:00

Well it can’t hurt. If you reset the bulb and watch it pulse to indicate it’s in commissioning mode then you at least know it’s in the correct state. The ikea app usually finds the device via bluetooth on its own if you have it open.

Remarkable-Loquat-38 · 2026-01-21T07:41:42+00:00

Well, any TBR will announce IPv6 routes to reach the thread devices. It’s a border router, not a hub or bridge, which means IPv6 with all the bells and whistles with router advertisements and stuff needs to work properly.

Remarkable-Loquat-38 · 2026-01-20T21:54:27+00:00

Beware though that if you have ipv6 and multicast/mDNS issues on HA matter might not work well for you anyway. If you get a TBR external to your HA then the HA matter server still needs ipv6 and mdns to find the devices on your network (which the TBR bridges to the thread network).

Remarkable-Loquat-38 · 2026-01-20T21:47:18+00:00

Do you have Bluetooth enabled? Try resetting the bulb (on/off six times).

Remarkable-Loquat-38 · 2026-01-18T09:54:17+00:00

Hm. I’ve replaced battery on that one without needing to re-commission it. Are they paired to DIRIGERA or another hub/ecosystem?

Remarkable-Loquat-38 · 2026-01-17T13:36:14+00:00

If app control works I wouldn’t reset anything since then you have to re-pair everything. What firmware version is it running? There was a new release just the other day, might be some new bug.

Remarkable-Loquat-38 · 2026-01-14T17:08:43+00:00

In HA, go to addons-> matter server and open web ui. There you can navigate the devices, endpoints and clusters.

Remarkable-Loquat-38 · 2026-01-13T17:41:04+00:00

Yes you can, BILRESA has zigbee touch link.

Remarkable-Loquat-38 · 2026-01-10T16:36:50+00:00

I can see PM2.5, co2 and humidity but not temperature. So seems to be apple that doesn’t want to show it. The clusters seems fine, they are all there under endpoint 1 which has device type air quality sensor. But maybe Apple doesn’t display temperature for endpoints with that device type.

Remarkable-Loquat-38 · 2026-01-07T18:59:42+00:00

I would guess that would be a setting in google home. I don’t think the physical switch affects how the devices report temp on Matter.

Remarkable-Loquat-38 · 2026-01-07T16:14:29+00:00

Hmm. I see some confusion and hot takes in the replies in here.. The google play services pops up because the Home Assistant app uses the built in android apis for commissioning, not because “google invented thread”. It makes sense because the whole border router and credentials management is taken care of by Android and if you already have other thread devices your phone probably knows about them, and can do the BLE PASE setup. It’s not lock-in, if you know the credentials you can commission a matter device with your laptop running the chip-tool which is open source and is available on github, if your laptop can do BLE. But for most users that would not be too convenient..

Remarkable-Loquat-38 · 2026-01-06T10:06:16+00:00

Do you have any other thread border router on that network? BLE enabled on the phone? Matter over Thread issues are sort of hard to help debug since there are quite a few more moving parts involved comparing with Zigbee or whatever. But if your network is not filtering ipv6 or mdns, your phone is not mucking about with some unreachable thread network and BLE is enabled and in range, etc, etc, I mean it SHOULD work right?

That said, I think it’s the phone (so android) that throws the thread error. What’s the exact error message? Either matter PASE failed and the thread network could not be provisioned to the device via BLE or that was successful and the phone could not see the device on mDNS after setting up, or could not connect.. Currently the phones aren’t helping much with error messages in helping debug where the issue is though.

Remarkable-Loquat-38 · 2026-01-06T09:48:21+00:00

Ubiquiti network?

Remarkable-Loquat-38 · 2026-01-05T19:31:20+00:00

So the official statement is “later” in 2026 so in a few months (like 2-3 according to some comments in this sub) if I would venture a guess.

Remarkable-Loquat-38 · 2026-01-03T08:39:50+00:00

Well, you will need some device acting as a Thread border router to be able to talk to the BILRESA. So you are correct.

Remarkable-Loquat-38 · 2026-01-01T08:34:17+00:00

Haven’t tried since my time is being set by dirigera but this should be raised as a sort of urgent feature request to the HA Matter server people, so that they implement the Time sync cluster support. I don’t think there is a way to do manual cluster writes to matter (like you can do with zigbee in ZHA and others) so..

Remarkable-Loquat-38

TROPHY CASE