More detail and screen shots in this forum thread: https://community.home-assistant.io/t/why-cant-ha-ping-ipv6-sometimes/941304/1
Short version: Added IPv6 to my local LAN (no ISP support), everything gets ULA address as well as its link local. Everything can ping everything else on both local and ULA addresses. Only one VLAN involved (I have others but HA is not involved).
In the integration the matter device works (can control it), and it shows an IPv4 address and IPv6 link local address (only, no ULA).
Everything else on my network that I have tried can ping the link local address of the device, as well as the ipv4 address.
From the matter integration device page, a ping there succeeds in IPv4 but not IPv6 (though the address is right).
From HAOS I can ping the IPv6 link local address from the SSH CLI.
The matter control on the device works, mostly, though start up after power failure can take a LONG time (like 10-15 minutes). I have no idea if that's related, but since that's my only symptom I worry it might be.
The ping from matter did work once -- I do not know why it stopped (after a power cycle on the device though). At that time it ALSO pinged a ULA address (DHCP6 is active).
Any ideas?
Linwood
PS. Screen shots and such at the form address above, didn't want to overload this thread. Note that forum post started with a different SSH addon that also affected pings, but it gets more clear toward the end.
I am just starting to use Matter, and set up ipv6 on my local network only with ULA addresses (and link local) as well as DHCP6. HA and my desktop and my network monitoring system are all on the same VLAN. I have a matter device with link local address fe80::d273:d5ff:fe80:d2d8. I have tried pinging it from my desktop and my NMS and it works...