It’s likely not the issue, I managed to get my matter device, a Tapo Smart plug, added and continue to see this error in the log. Have you added the matter device to either Google/ Alexa / Homekit? I added to Google Home first and shared from there to HA.
I still have this problem too. Could be that I’m using a CM4 with a wireless interface on my Home Assistant Yellow? It clogs up the logs and makes it harder to troubleshoot.
I have been trying to wrestle the IPv6 beast a lot lately and if you are using multiple network interfaces on HA, then you are in for a fight of the big ones and your network understanding from IPv4 will not work at all. IPv6 is so different.
What you need to configure is the network binding of the services and I have no clue where to do that.
In IPv6 every network interface will have several networks, like fe80::/64, ff02::/16 and so on.
If you have 2 network interfaces, then it means you will have 2x fe80::/64, 2x ff02::16 and so on.
When you then want to contact something on a fe80::/64 network then you need to specify which network interface this is going to happen on. With just one network the operating system will always choose the right one, but with multiple it will choice the one that it finds appropriate if nothing is stated.
This might not be the right one, so the standard have a solution to that, which is to state the network interface ID in the address. The interface ID is added to the end with %ID_number_of_interface.
IPv6 will also add multiple addresses that act differently, like some that will not be routed between networks/VLANs, like fe80, others that can be routed between local networks/VLANs, but not on the internet, like fc00::/10.
And these addresses can exist in stateful versions, where it is controlled totally by a server/router, in a stateless versions, that is controlled partly (the prefix part) by a server/router, also called SLAAC, and also in temporary versions that is handled without any server/router.
I discovered after studying DNS-DS and m-DSN that I can compare the list from an ubuntu computer (in my local network) with the command (avahi-browse -all), with the log from Matter in home assistant.
I can use this to trace an error in the services list (DNS-SD) and which device is causing this error.
DNSSD packet parsing failed (for SRV records)
in other words, it is not possible to interpret inaccuracies in the network (parsing) for matters in the home assistant.