# Issue with Matter on self hosted Homey **URL:** \ **Category:** Homey Self-Hosted Server\ **Tags:** matter\ **Created:** [December 18, 2025, 8:09am UTC](https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203 "2025-12-18T08:09:08Z")\ **Posts on this page:** 1\ **Showing post:** 40
**Author:** ![Etone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/etone/32/120942_2.png) [@Etone](https://community.homey.app/u/Etone)\ **Post date:** [January 17, 2026, 8:25am UTC](https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203/40 "2026-01-17T08:25:07Z")
Quickly changed to bridge network mode on my homey-shs compose. The Matter daemon now starts successfully, but the connection does still not work. Instead of immediately getting errror 0x00ac I’m now having a timeout when pairing the device (Shelly Plug) with Homey, quite likely because either the IPv6 routing or mDNS is not working correctly. Unfortunately I don’t have the time to check this today. Might have a look at it tomorrow EDIT: I also found [this Guthub Issue](https://github.com/project-chip/connectedhomeip/issues/27007) which indicates that having to many Network Adapters on a host might cause issues when initializing the Matter Daemon, and since I have a bunch of IP Links due to running more compose stacks, this might be my problem. Would also explain why in bridge mode this works, as in the container I would only have a small number of Network Adapters (One from the host, the loopback device and the one veth interface from the container Network). I might move my homey-shs to another host (vm on proxmox) and check if this works or move it even out of VMs and see if I have success then --- _[View the full topic](https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203)._