home-assistant-matter-hub container not announcing _matter._tcp on IPv6

[tam481]

I managed to determine that my matter devices are showing on my RPi's eth0 interface announcing themselves via mdns "_matter._tcp".
I can also see that my RPi is listening on IPv6 on port 5540 which I am pretty certain is my "home-assistant-matter-hub" container.

However, I while I can see my "home-assistant-matter-hub" container is listening on IPv4 and IPv6 port 5540, it does not appear to be announcing itself on mDNS on IPv6

What can I do to fix this? is this a bug? Can I "mannualy announce via mDNS" the HAMH IPv6 address?

[tam481]

Update:
I have been doing a lot of testing and the container is only publishing the IPv4 address on mDNS.

I tested this by stopping the container and running:

avahi-publish-address D83ADDCFE8A20000.local fd81:b82:c83:1:eb07:dc4b:60a1:55b5

avahi-resolve-host-name D83ADDCFE8A20000.local
D83ADDCFE8A20000.local  fd81:b82:c83:1:eb07:dc4b:60a1:55b5

When I start the matterhub container and try to resolve the host name I get

avahi-resolve-host-name D83ADDCFE8A20000.local
D83ADDCFE8A20000.local  192.168.1.20

[Apollon77]

is your docker configured for IPv6? This neds to be enabled!

[tam481]

Docker is configured for IPv6

The router is issuing the host with a valid IPv6 address fd81:b82:c83:1::20

[Apollon77]

also see matter-js/matter.js#2152 (comment)

[Apollon77]

Today I found matter-js/matter.js#2189 which lead to invalifd encoding of specil IPv6 adresses sometimes, might be easiely related that ... would be cool to retry after this got merged