Matter Integration does not include the interface when attempting to ping IPv6 Local Link addresses

[lavish dune]

Hey all, first time poster here.

I'm having issues using the ping functionality of the the Matter interface. Note, I have a good grasp on IPv4, but 6 still eludes me. If I attempt to ping my Aqara M3 hub via the Home Assistant UI, it fails on the IPv6 Local link address. However, if I exec into the matter docker container and ping that address with the interface specified the device responds to pings

root@core-matter-server:~# ping6 fe80::56ef:44ff:fe6e:8090%enp0s10
PING fe80::56ef:44ff:fe6e:8090%enp0s10(fe80::56ef:44ff:fe6e:8090%enp0s10) 56 data bytes
64 bytes from fe80::56ef:44ff:fe6e:8090%enp0s10: icmp_seq=1 ttl=64 time=1.55 ms
64 bytes from fe80::56ef:44ff:fe6e:8090%enp0s10: icmp_seq=2 ttl=64 time=1.61 ms
64 bytes from fe80::56ef:44ff:fe6e:8090%enp0s10: icmp_seq=3 ttl=64 time=2.94 ms

Am I doing something wrong, or is this a bug?

I've checked the python-matter-server log files and it appears that the SDK is connecting via that local link address

2025-04-13 00:02:14.983 (MainThread) DEBUG [matter_server.server.device_controller] <Node:10> Pinging address 10.10.10.121
[Detaching after vfork from child process 266]
2025-04-13 00:02:14.989 (MainThread) DEBUG [matter_server.server.device_controller] <Node:10> Pinging address fe80::56ef:44ff:fe6e:8090
[Detaching after vfork from child process 267]
2025-04-13 00:02:14.992 (MainThread) DEBUG [matter_server.server.device_controller] <Node:10> Pinging address fdfb:ab02:b9f9:0:56ef:44ff:fe6e:8090
[Detaching after vfork from child process 268]
2025-04-13 00:02:25.001 (MainThread) INFO [matter_server.server.device_controller] <Node:10> The SDK is communicating with the device using fe80::56ef:44ff:fe6e:8090