-
I am trying to commission Tado radiator thermostats using Matter.js via the Matter-Shell. The device and the Thread Border Router are already commissioned into the same network. When I attempt to commission the device on Ubuntu, it works as expected without any issues. However, when I try the same process on Windows, I encounter an error and the commissioning fails. Please let me know if further details or logs are needed to investigate this issue, and thank you for your time. Logs: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
Please check the IPv6 setup of your host ... if Linux you might need to tweak the network config a bit oin order to be able to communicate with brorder router ipv6 adresses https://github.com/project-chip/matter.js/blob/main/docs/TROUBLESHOOTING.md#ipv6-linux-system-details |
Beta Was this translation helpful? Give feedback.
-
Thank you for the suggestion. I have already looked into this, but IPv6 forwarding is disabled, and the corresponding kernel option does not exist on Windows. Unfortunately, I couldn't find a way to verify whether Route Announcements (RA) and Route Information Options (RIO) are active on Windows. Could it be that using the Thread Border Router on Windows is simply not supported, similar to how BLE functionality is unavailable on this platform? Any clarification or additional guidance would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
-
Ahhh you are on windows. try turning off the firewall and verify if it works then ... if it is this then you need to find out how to tweak the firewall settings. Several others also use on Windows so I assume it is really just a matter of settings. If you find it out I am happy to include it into the troubleshooting |
Beta Was this translation helpful? Give feedback.
-
It seems like it's a routing Problem, manually setting it in the Terminal like that " netsh interface ipv6 add route "IPv6-Prefix" "Interface-Index" "Next-Hop-Adress" " has fixed the problem. |
Beta Was this translation helpful? Give feedback.
It seems like it's a routing Problem, manually setting it in the Terminal like that " netsh interface ipv6 add route "IPv6-Prefix" "Interface-Index" "Next-Hop-Adress" " has fixed the problem.