Closed S0ulf3re closed 1 year ago
Ok, So I made sure to turn off mDNS repeating like the documentation says to within the Avahi package. But I am still not getting any different results
I was never able to fix this, so I just ended up switching to the raspberry pi. I apologize to anyone who might have found this via search engine :(
I've been discussing this in the HA Discord. But I'm just gonna write it here so it can get a bit more attention by others. I've been trying to commission a TP-Link Tapo P125M Wi-Fi Smart Plug to my Home Assistant Container instance running the docker image for the Python Matter Server exposed to my LAN over a macvlan network alongside a few other things on it. However, whenever I view all exisitng mDNS entries on my network, the Matter Server doesn't show up as a _matter._tcp. entry. And any attempts to commission the device fail with the Python Matter Server complaining about timing out with mDNS resolution.
A few other things in these debug logs that concern me:
enp2s0
The smart plug is currently commissioned to Apple Home and Google Home without any issues. And both the Home Assistant Container instance and Python Matter Server are running on the same device, and are connected to the same LAN that the P125M is on.
My network is currently managed by a Pfsense firewall running version 2.6.0 that has the WAN set to DHCP/DHCP6 and the LAN set to a static ipv6/track interface of WAN for ipv6. Avahi is currently installed and enabled, and set to repeat packets across subnets for a few extra IoT devices on another network.
And here is my docker compose for the Matter server and macvlan: