I think I have Matter and Thread Set up properly. I have HA in a container, I have a python-matter server also set up in a container and IPv6 enabled on my network. I am able to pair a tplink taro via matter. I also have homepod mini and level lock matter pairs to the apple home network.
I have added the matter integration and entered URL for container running the matter-python and it connects as I can see it in the log. I also used the mobile app to send the apple home matter credentials to HA as well as made the apple home thread network as the preferred, The HomePod mini is 5 feet from the lock.
I can’t seem to add Level Lock as a Matter device in Home Assistant. I go into Apple Home and enable pairing on the level lock. I get a pairing code which I then go into HA and add a matter device and enter the pairing code but it fails.
I see this in the matter server. Node ID is 9 as I’ve tried multiple times with no success
2025-10-28 17:00:59.207 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 9.
2025-10-28 17:00:59.213 (ThreadPoolExecutor-0_0) DEBUG [matter_server.server.storage] Saved data to persistent storage
I’ve tried to enable debug on thread but I don’t see any thread debug message when I look at the log
Ok… I’m narrowing this down to the Matter Server container… If I run HAOS and run the internal matter server, I can pair to a level lock matter using HomePod mini thread border router.
However, if I configure HAOS to use the matter server container, I get the same issue. I’ve started my mstter server container with the following
Finally got it working, although it’s a roundabout method. Info I left out was that I’m running this on a QNAP. Tried everything to get it working as a straight container on QNAP, but seems like I could not figure out the networking settings to make ipv6 work the way the matter server needed, There was one setting that I could not find any information on how to set net.ipv6.conf.all.accept_ra_rt_info_max_plen = 64.
Anyway, the work around was to install a bare alpine linux in a VM, enable ipv6 and docker on the alpine linux. the docker matter image runs fine under alpine with the ipv6 settings.
If anyone has any ideas on how to configure ipv6 on a QNAP, would be great to hear. I’m running QuTS hero h5.2.7.3256 which is the latest stable version of the firmware. It utilizes aaah to set up virtual switch and unfortunately the qnap kernel does not have a setting for net.ipv6.conf.all.accept_ra_rt_info_max_plen , I was able to temporarily set the other ipv6 settings using the qnap sysctl
