#Hey,

1 messages · Page 1 of 1 (latest)

magic phoenix
#

Do I need bluetooth enabled somewhere? Hopefully I don't 😬

dry sable
#

No, we use the bluetooth connection on your phone for commissioning and when you add a device shared from another ecosystem, we dont need bluetooth at all

#

Did you try adding it to Google Home first and from there share it to HA ?

magic phoenix
#

Yeah tried sharing it from Google Home, but that errored out too.
I got an error similar to:
Can't share device

dry sable
#

OK, this smells like networking issues. So the IPv6 (mdns) traffic cant correctly travel from device to HA

#

Make sure that IPv6 is enabled (just set it to automatic) on HAOS

#

en check any switches between the HA server

magic phoenix
#

sigh. Yes probably. I'm 99% sure it's mdns then.

It's setup for the Home-Assistant container but not the matter-server container.

dry sable
magic phoenix
#

oh nope.

dry sable
#

Oops, that is not supported

#

You may get it working but you may run into mdns issues (as you already figured out)

magic phoenix
#

Yeah nothing outside HAOS is really supported.
But as long as I can get awesome pointers like that I'm all good 🙂

Thanks!

dry sable
#

We patched the entire HAOS to make sure the traffic passes

#

I will share some pointers where to look for but you will need a super recent host OS. Maybe you can use bridged networking instead. ?

magic phoenix
dry sable
#

No it wont

magic phoenix
#

oh, what am I misunderstanding?

dry sable
#

You cant route Matter traffic

#

It uses Neighbour discovery

#

So maybe you can just run your container on macvlan ?

magic phoenix
#

is it discovery from matter-server's point of view or home assistant?

(or both)

dry sable
#

matter server

#

ha and matter server communicate only with the websocket via port 5580

#

but the matter server itself needs full (L2) access to the network

#

No support for inter vlan routing etc

magic phoenix