Help with the Matter setup

Configuration Matter/Thread
1

Hi,

I bought today in Ikea a Timmerflotte (temp sensor) and a Bilresa (a button) that are thread matter. I use zigbee with zigbee2mqtt, but I have a skyconnect ZBT-1 that I never used, so I thought, instead of relaxing this weekend, I will rather waste some time with this.

Anyway I connect the ZBT-1 and choose use as Thread, so it got flashed with the OpenThread Border Router, then the Thread service was added, then I added the Matter service. I went to settings, plugins, and I see the OpenThread Border Router and matter server have been automatically added.

On the OTBR configuration, the skyconenct is selected as default device, the port is 460800, I disable the Hardware flow control,
then firewall is on and nat64 is off, but I also tried it on. I restarted the server.

On the phone, I connected to the 2,4GHz Wi-Fi, I went to settings, companion app, troubleshooting, and sync thread,

Then I went to add new matter device, scan the QR, and it says connecting to device few seconds, then generating matter credentials, then checking connectivity to thread network ha-thread-3b7 few seconds and then can’t connect to thread network.

What I’m doing wrong?

2

My yaml for OTBR

device: >-
  /dev/serial/by-id/xxx
baudrate: 460800
flow_control: true
otbr_log_level: notice
firewall: true
nat64: true
autoflash_firmware: true

Matter server

log_level: info
log_level_sdk: error
beta: false
enable_test_net_dcl: false

then exactly as you said,
Companion App → Troubleshoot → Sync Thread credentials

and then connect device. That worked for me with Ikea Bilresa. On the Bilresa all three LEDs should be blinking before starting the connection.

3

Not working for me, :frowning: my config of my 2 server are exactly like yours. I had IPV6 disabled under networking, so I enable it and set it default, also enable on the router. My isp does not have native ipv6, but i understand is not essential.
I restarted the router and the server, and the server now has a local ipv6 address as well. Yet nothing. Still failing. This is the log if its any help

Adapter settings file /data/thread/0_124b0021b950e8.data is the most recently used, skipping
[19:20:41] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_12b93fa84243ed11ba2b45ab2a61ed69-if00-port0?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp1s0
[NOTE]-ILS-----: Infra link selected: enp1s0
49d.17:08:08.467 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.048 [N] RoutingManager: BR ULA prefix: fdec:e040:171b::/48 (loaded)
00:00:00.048 [N] RoutingManager: Local on-link prefix: fd21:5510:90ec:ae50::/64
00:00:00.074 [N] Mle-----------: Role disabled -> detached
00:00:00.125 [N] P-Netif-------: Changing interface state to up.
00:00:00.158 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.159 [W] P-Netif-------: Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
[19:20:42] INFO: Enabling NAT64.
Done
00:00:00.374 [W] P-Netif-------: Failed to process request#7: No such process
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[19:20:42] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
00:00:26.164 [N] Mle-----------: RLOC16 6000 -> fffe
00:00:26.254 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:32.759 [N] RouterTable---: Allocate router id 24
00:00:32.759 [N] Mle-----------: RLOC16 fffe -> 6000
00:00:32.762 [N] Mle-----------: Role detached -> leader
00:00:32.762 [N] Mle-----------: Partition ID 0x595e9be8
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:34.959 [W] DuaManager----: Failed to perform next registration: NotFound
4

One thing I don’t understand. So in the settings the network is called ha-thread-543d, but in the companion app when I scan it’s trying to connect to ha-thread-3b7c. I remove the services, I reset the server on companion app i reset the cache, I sync the thread credentials again, every time it’s trying ha-thread-3b7c

image
image1036×2048 68.2 KB

image
image1623×564 18.8 KB

5

There is also an integration (not only add-on) “OTBR”, perhaps you have to remove entries there as well and start all over.

6

The integration and the add-on were installed automatically after I install the skyconnect. There are no entries.

7

If i install manually the integration, then it asks me for the address of the thread server. If it’s installed automatically after the skyconenct is installed, then its just work, but I cant connect anything to home assistant.

8

I think the problem has to do with Google services. I tried another to add it to google home and its trying to the same ha-thread-3b7c, i deleted data for google home, and google , still the same.

9

have a look here

but read the advice concerning deleting all data from Google Play services (I did it myself in the past for other reasons)!

10

In the end, I managed to add them using an iPhone. I will buy another just so that i try reseting the Google play. I spent all day with the Samsung, it took 10 min from the iphone. :grimacing:

I appreciate your help.