# Issue with Matter on self hosted Homey

**URL:** <https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203>\
**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:** 86

<div class="post-metadata">

**Author:** ![Mantlet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mantlet/32/121247_2.png) [@Mantlet](https://community.homey.app/u/Mantlet)\
**Post date:** [June 4, 2026, 8:53am UTC](https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203/86 "2026-06-04T08:53:11Z")

</div>

This guide also helped me to setup matter over thread. Since I don’t have a Mac either, I’ve looked up the WIndows Powershell equivalent of the netstat command. I have found the IPv6 routing to my Google TV 4K, that acts as my Thread Border Router with this command:

```auto
Get-NetRoute -AddressFamily IPv6 | Where-Object { $_.DestinationPrefix -like "fd*" }

```

The result contains something like this:

```auto
DestinationPrefix : fd__:::1::/64
NextHop : fe:::::
ifIndex : 12

```

You can then paste this information in the script that @majorzoltanpepe proposed as boot-script:

```auto
/sbin/sysctl -w net.ipv6.conf.all.accept_ra=2
/sbin/sysctl -w net.ipv6.conf.default.accept_ra=2
/sbin/sysctl -w net.ipv6.conf.eth0.accept_ra=2

/sbin/ip -6 route add fd29:.../64 via fe80:... dev eth0 metric 50 2>/dev/null || true

```

So, if the rest of your network and TBR are setup correctly and you skip all trouble-shooting steps this is all you need: Run powershell script, paste results in boot-script and reboot your Synology NAS.

@majorzoltanpepe Thanks very much for the extensive guide!

---

_[View the full topic](https://community.homey.app/t/issue-with-matter-on-self-hosted-homey/147203)._