this post was submitted on 11 Sep 2026
26 points (100.0% liked)

homeassistant

20610 readers
3 users here now

Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk

founded 3 years ago
MODERATORS
 

I'm trying to start using Thread devices in Home Assistant for the first time. I've gotten a Sonoff Dongle Plus MG24, flashed it with OpenThread firmware, added it as an OpenThread Border Router in Home Assistant, and added the Matter integration.

However, when I try to commission a Matter/Thread device using the Home Assistant companion app on my GrapheneOS phone, I scan the QR code, get to the screen that says "power on your device and make sure it's in setup mode," and "connect your phone to your main 2.4GHz network" and tap the "I'm ready" button, but then it gives me an error that I have "no Wi-Fi connection" even though it is definitely connected to the correct (2.4Ghz, not 5GHz) network.

I've also checked that the Home Assistant app has all the necessary permissions (network, nearby sensors, etc.)

Help?


Edit: I just found these bug report threads that look like they're relevant, but I'm still reading through them:

you are viewing a single comment's thread
view the rest of the comments
[–] tiramichu@sh.itjust.works 7 points 1 week ago* (last edited 1 week ago) (2 children)

Commissioning Matter devices using Graphene may not work due to the commissioning flow requiring Google Play Services.

I had that problem. If your Home Assistant instance itself has Bluetooth, you can use the manual flow to work around it:

In HA:

Settings -> Connectivity -> Matter -> Options -> Add Manually

There you can type the 11 digit code from your matter device (exactly as it appears, including hyphens) and it will add it without needing a phone.

As mentioned though, your HA instance needs Bluetooth for this. My HA is in a virtual machine so plugging a dongle was less than ideal. I solved it instead using a esp32 Bluetooth proxy over Ethernet.

https://esphome.io/components/bluetooth_proxy/

You may(?) also need to set up Matter to use that bluetooth device. There's some reading on it here which could be useful

https://smarthomescene.com/guides/add-matter-devices-home-assistant-without-phone/

Good luck! :)

I'm glad I set it up, because being 'forced' to use a google/apple phone for setting up matter on my local network feels like a really stinky pattern. I'm glad I don't need to :)

[–] immobile7801@piefed.social 3 points 1 week ago* (last edited 1 week ago) (1 children)

Interesting that you can use BT for this. I have a spare googled phone for stuff that doesn't work on graphene that I don't feel like troubleshooting for more than a few hours that I used to add an aqara deadbolt.

Honestly, after all the troubleshooting with matter (I didn't have ipv6 prior and didn't really see a need internally for it) I wish I had gone with a different deadbolt as it was the first matter device and currently still only one.

[–] tiramichu@sh.itjust.works 3 points 1 week ago

The normal consumer smartphone pairing flow uses Bluetooth on the phone to do the initial device pairing after you scan the QR code.

You just aren't made aware of that as the user.

The on-server flow also needs Bluetooth therefore, and all that's different is you manually type the numbers from the QR instead of using the camera to scan :)

[–] needanke@feddit.org 2 points 1 week ago* (last edited 1 week ago) (1 children)

To set up matter for using bluetooth one just needs to go into the matter-server apps settings and turn on "Enable BLE proxy".

Besides what the name suggests, that also works for local bluetooth dongles.

[–] tiramichu@sh.itjust.works 3 points 1 week ago

When I did it, this also involved switching to the beta version because the functionality to use a Bluetooth proxy was kinda new. But I guess we're past that now, hooray~