Hey everyone!
I am getting started with Matter. I have had the Matter integration (BETA) for some time but have never added any devices… until today, today is that day…
When in my desktop browser I click add entry the following appears:
Should I be looking for the “Official Matter Server Supervisor Add-On”?
Here are the add-ons I currently have:
Any wisdom, insight or help would be greatly appreciated!
Thanks,
Paul.
Where you show “ADD ENTRY”, that is trying to add another instance of the Matter Integration, so no don’t use that.
It looks like you have already added Matter devices, as it shows “3 devices”. Not clear what problem you are running into?
Settings>>devices&services>>devices>>add device
Yes that’s correct then it should prompt you with a “Select brand” and then choose “Add Matter device”.
What happens after this?
It asks if device is new or already setup
In the end it will be discovered, you will need to scan QR code or you will need to enter the number from label.
Also, this requires ipv6 which is the exact reason all the devices I currently have do not work. I still need to figure out how i want to implement ipv6 on my network and how I want devices to work in this network. I lack ipv6 understanding and have complex network setup so love to hear how you all do it
EDIT
Pretty sure you must add device using a phone since it uses Bluetooth as part of setup process. You can use your HA server if it has Bluetooth setup and functioning with HA
For starters, it looks like you have HA’s OTBR AddOn. This OTBR is an IPv6 router, and it will send out an IPv6 network prefix over the LAN and any device on the same LAN (including HA) that is enabled for IPv6 auto mode will see this prefix and assign itself a full IPv6 ULA (a private address). When you commission a Matter/Thread device, you’re mobile device “should” be on the same LAN as HA because it will be looking for multicast discovery packets on that LAN.
Hey, quick question, I have a couple matter devices on the same lan as HA and never was able to connect to them over matter if they were on my IOT vlan. So, all my IOT devices are on that other vlan except for those two devices.
I also had an issue where I was unable to cast to a chromecast device that was on a different vlan as well. I finally discovered mDNS repeating and set that up on my router and now I can cast to the Chromecast from any any VLAN… For the chromecast I set up the bonjour service:
_googlecast._tcp.local
so for matter all I need would be to set up this bonjour service? And are there others I would need?
_matter._tcp.local ?
Different routers relay link-local multicast mDNS-SD in different ways, so not sure how you would setup your router. What I have seen from others is that whatever technique a router uses, it can be problematic/hard to get to work so it is not a recommended way. Others instead put their HA on both the IoT VLAN and the main VLAN.
But to answer your question, Matter needs both _matterc._udp (for device discovery), _matter._tcp (for Operational Discovery). Thread uses ._meshcop._udp.
