Hello everyone,
I’m currently attempting to set up Matter with Thread, and I find myself encountering some challenges.
I seem to be at an impasse as the Nuki ( PRO 4 ) device fails to join the network. At this point, I’m unsure whether the issue lies with the Nuki device itself or with my setup. It’s worth noting that I only have one Nuki device to test.
My Thread router is a Sonoff Dongle E, as shown in the image below:
I’m exclusively utilizing Thread with this device, as I have another device dedicated to the Zigbee network. Initially, I attempted to use OpenThread RCP, but encountered difficulties running it on my Docker container. Specifically, I faced connectivity issues, which I suspect may be attributed to the network interface being labeled as eno1 instead of eth0.
Unfortunately, I couldn’t find any documentation on how to address this within the Docker-compose environment or command line ( to force to use eno1 instead of eth0 )
Below is the snippet of the attempted setup:
# openthread:
# image: openthread/otbr
# tty: true
# stdin_open: true
# container_name: openthread
# privileged: true
# command: --radio-url spinel+hdlc+uart:///dev/ttyACM0
# sysctls:
# - net.ipv6.conf.all.disable_ipv6=0
# - net.ipv4.conf.all.forwarding=1
# - net.ipv6.conf.all.forwarding=1
# ports:
# - "8080:80"
# dns: 127.0.0.1
# volumes:
# - "/dev/ttyACM0:/dev/ttyACM0"
Following this setback, I attempted to change the firmware and employed MultiPan, despite my intention to solely utilize Thread routing.
Below is the Docker configuration for MultiPan:
multipan:
container_name: multipan
image: b2un0/silabs-multipan-docker:latest
restart: unless-stopped
privileged: true # don't change this !
network_mode: host # don't change this !
cap_add:
- SYS_ADMIN
- NET_ADMIN
volumes:
- /home/pc/Documents/projects/multipan/data:/data
environment:
DEVICE: "/dev/ttyACM0" # only change if your have multiple devices
BACKBONE_IF: "eno1" # change this to your network interface
BAUDRATE: "460800"
FLOW_CONTROL: "false" # change to false if you not using SkyConnect
OTBR_REST_LISTEN_PORT: "8081" # use this within the HomeAssistant integration
OTBR_WEB_PORT: "8086"
Although the setup appears functional, I’m uncertain about its adequacy.
I’ve found the following plugins to be promising:
This one also ( I don’t know the diff between Thread and OTBR so I installed both ) :
However, despite these seemingly positive indications, I’m unable to ascertain why my Nuki device refuses to join the network. I enable Matter, proceed to the HomeAssistant app, and attempt to add the Matter device. While the device is detected and an attempt to connect is made, it ultimately fails with an error message stating, “This device cannot join the Thread-HA network. Ensure it’s compatible with this network.”
Any insights into resolving this issue would be greatly appreciated.
