Cannot add Matter devices

ThierryIT · December 26, 2024, 8:03am

Hello,

I have two HA at home, the first main one running under the HA green box when the second is running on a proxmox VM … Both will be connected to each other through the “remote-HA” integaration … Both are connected to the same ethernet network number.
I am using the Skyconnect USB key.

Core 2024.12.5
Supervisor 2024.12.0
Operating System 14.1
Frontend 20241127.8

Matter server: 6.6.1
Silabs-Multi-Protocol: 2.4.5
OTBR: 2.12.2

Logs:

Matter server:

[1735195916.449904][116:116] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)

[1735195916.449961][116:116] CHIP:DL: NVS set: chip-counters/reboot-count = 12 (0xC)

[1735195916.450844][116:116] CHIP:DL: Got Ethernet interface: enp0s18

[1735195916.451170][116:116] CHIP:DL: Found the primary Ethernet interface:enp0s18

[1735195916.455281][116:116] CHIP:DL: Failed to get WiFi interface

[1735195916.455325][116:116] CHIP:DL: Failed to reset WiFi statistic counts

2024-12-26 08:51:56.459 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json

2024-12-26 08:51:56.459 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...

2024-12-26 08:51:56.648 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...

2024-12-26 08:51:56.648 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1

2024-12-26 08:51:56.650 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...

2024-12-26 08:51:56.651 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B

2024-12-26 08:51:56.651 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.

2024-12-26 08:51:56.652 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...

2024-12-26 08:51:56.659 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).

2024-12-26 08:51:56.659 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []

2024-12-26 08:51:56.773 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 112 ms, for event type 2

2024-12-26 08:51:56.836 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.

2024-12-26 08:51:56.851 (MainThread) INFO [matter_server.server.vendor_info] Loaded 271 vendors from storage.

2024-12-26 08:51:56.852 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.

2024-12-26 08:51:57.681 (MainThread) INFO [matter_server.server.vendor_info] Fetched 270 vendors from DCL.

2024-12-26 08:51:57.681 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.

2024-12-26 08:51:57.707 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration

2024-12-26 08:51:57.732 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.

OTRB:

System: Home Assistant OS 14.1  (amd64 / qemux86-64)
 Home Assistant Core: 2024.12.5
 Home Assistant Supervisor: 2024.12.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[08:11:27] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[08:11:27] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-12-26 08:11:32.330 remoteHA universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0), cpc_version=None, fw_type=<FirmwareImageType.OPENTHREAD_RCP: 'openthread_rcp'>, fw_variant=None, baudrate=460800)
2024-12-26 08:11:32.331 remoteHA universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-26 08:11:34.365 remoteHA universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-12-26 08:11:38.702 remoteHA universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-12-26 08:11:38.732 remoteHA universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) at 460800 baudrate (bootloader baudrate None)
2024-12-26 08:11:38.732 remoteHA universal_silabs_flasher.flash INFO Cross-flashing from FirmwareImageType.MULTIPAN to FirmwareImageType.OPENTHREAD_RCP
2024-12-26 08:11:39.264 remoteHA universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-26 08:11:39.295 remoteHA universal_silabs_flasher.flasher INFO Detected bootloader version '2.1.1'
2024-12-26 08:11:39.295 remoteHA universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200)
skyconnect_openthread_rcp_2.4.4.0_GitHub-7074a43e4_gsdk_4.4.4.gbl

Silabs-Multiprotocol

otbr-agent[342]: 00:00:00.307 [N] Mle-----------: Role disabled -> detached
otbr-agent[342]: 00:00:00.388 [N] Platform------: [netif] Changing interface state to up.
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
Listening on port 9999 for connection...
Accepting connection.
[08:14:38] 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
WARNING in function 'server_push_data_to_endpoint' in file /usr/src/cpc-daemon/server_core/server/server.c at line #1667 : Unresponsive data socket on ep#12, closing
otbr-agent[342]: 00:00:15.327 [W] Platform------: Unexpected Spinel transaction message: 8
otbr-agent[342]: 00:00:15.327 [W] Platform------: Error processing response: Drop
[08:14:52:127909] WARNING : In function 'server_push_data_to_endpoint' in file /usr/src/cpc-daemon/server_core/server/server.c at line #1667 : Unresponsive data socket on ep#12, closing
[08:14:52:128213] Info : Endpoint socket #12: Client disconnected. 1 connections
otbr-agent[342]: 00:00:26.606 [N] Mle-----------: RLOC16 0800 -> fffe
otbr-agent[342]: 00:00:26.623 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[342]: 00:00:26.879 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[342]: 00:00:33.382 [N] RouterTable---: Allocate router id 2
otbr-agent[342]: 00:00:33.383 [N] Mle-----------: RLOC16 fffe -> 0800
otbr-agent[342]: 00:00:33.392 [N] Mle-----------: Role detached -> leader
otbr-agent[342]: 00:00:33.394 [N] Mle-----------: Partition ID 0x3a7feb16
otbr-agent[342]: 00:00:33.536 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[342]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!

Thread:
Preferred Network

ha-thread-1d31
1 border router
Home Assistant Silicon Labs Multiprotocol #88EA remoteHA.local.

OTRB
Services

Home Assistant SkyConnect (OpenThread Border Router)
No devices or entities

I do not see anything wrong at this point.

When trying to install the Aqara Sensor P2 from my Android tablet, It detect the device, start the process but instead of connected to the local preferred Thread network (1d31) it is trying to connect to the Thread network of my “main HA” … And stop processing.
I have configured my IPv6 IPs on mu Unifi networks using SLAAC or DHCPv6 …
I am fighting on this problem for few days, I am running out of ideas.

After a try, after a change in my IPv6 config, I have this:

otbr-agent[342]: 02:14:13.772 [N] MeshForwarder-: Dropping (dir queue full) IPv6 UDP msg, len:269, chksum:cb74, ecn:no, sec:yes, prio:low
otbr-agent[342]: 02:14:13.772 [N] MeshForwarder-:     src:[fe80:0:0:0:bc38:88dd:8f5b:88ea]:5353
otbr-agent[342]: 02:14:13.772 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
otbr-agent[342]: 02:14:13.801 [N] MeshForwarder-: Dropping (dir queue full) IPv6 UDP msg, len:269, chksum:ca75, ecn:no, sec:yes, prio:low
otbr-agent[342]: 02:14:13.802 [N] MeshForwarder-:     src:[fe80:0:0:0:bc38:88dd:8f5b:88ea]:5353
otbr-agent[342]: 02:14:13.802 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Default: mDNSCoreReceiveResponse: Received from fe80::cbae:fe18:ebf6:de56:5353   22 6.5.e.d.6.f.b.e.8.1.e.f.e.a.b.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR remoteHA287788.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 6.5.E.D.6.F.B.E.8.1.E.F.E.A.B.C.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR remoteHA.local.

Help will be much appreciated.
Thx

WallyR · December 26, 2024, 2:21pm

Make sure you have the correct thread credentials on the Android.

On the Android Companion App open Settings → Companion App → Troubleshooting (I think that is what it is called in english, but it list logfiles and other tools to diagnostics as description of the item).
In this next window click the Sync Thread Login Credentials (Again it might not be named exactly that, but close to and there should not be that many options and it should be in the bottom)

It should say either something with “Added …” or “Already using the same credentials”.
The trick here is to run it again and make sure that it does not say “Added …” the second time.

If it does then you need to clear the Google Play Services Cache, which might clear a lot of other stuff, like login to services and credit card informations for Google Play and websites and so on, so make sure you know you informations before hand.

The way to clear the cache is Settings → Apps → See All Apps → Google Play Services → Storage and Cache → Manage Storage → Clear All Cache
Now repeat the syncing of the thread credentials above.

ThierryIT · December 26, 2024, 2:51pm

No luck, not working …

NathanCu · December 26, 2024, 3:20pm

Are you married to that multiprotocol stack?

Dev stopped working on it last year due to. Some e fundamental problems on the silabs side…

May not be related at all but troubleshooting is going to be difficult because if you find an issue you can’t say it’s NOT the problem. I’d try to revert that first then see if you can recreate the issue.

wmaker · December 26, 2024, 9:42pm

Sorry… trying to understand your setup a little better.

You have 2 HA instances, “main” and “remoteHA” on the same LAN with the same IPv6 subnet.
You are also running a Matter-Server, one on “main” and another on “remoteHA”?
Each HA instance is running their own OTBR/Thread-network independently. “main” HA has a Thread network named “??” while the “remoteHA” has a Thread network “ha-thread-1d31”.
You are using this custom integration to export the entities and their state created and maintained by the “remoteHA” instance to the “main” HA instance
You are using Android version of HA Companion App. Do you have the Companion App configured for two HA server instances?

I think what you are saying is that you want to run separate independent Thread networks in your home (and not try to run one combined Thread network). And you want separate Matter Fabrics?

Also I agree with Nathan, you should change multiprotocol AddOn to OTBR AddOn.

ThierryIT · December 27, 2024, 8:19am

You have 2 HA instances, “main” and “remoteHA” on the same LAN with the same IPv6 subnet.

→ Yes
You are also running a Matter-Server, one on “main” and another on “remoteHA”?

→ Yes the matter server running on the main server is used for my Ikea stuffs
Each HA instance is running their own OTBR/Thread-network independently. “main” HA has a Thread network named “??” while the “remoteHA” has a Thread network “ha-thread-1d31”.

→ The main HA has a thread network named “ha-thread-9750” as preferred network and the “ha-thread-1d31” from the remoteHA as “other network” .

On the main HA Add-On part:
Matter server
On the remote HA Add-on part:
Matter, OTBR and Silabs Multiprotocol

You are using this custom integration to export the entities and their state created and maintained by the “remoteHA” instance to the “main” HA instance

→ Yes
You are using Android version of HA Companion App. Do you have the Companion App configured for two HA server instances?

→ Yes

ps: the matter/thread server on my main HA is beeing removed.

ThierryIT · December 27, 2024, 8:32am

Thx a lot, from your point of you, what should I use to make my Skyconnect (or my Sonoff E) running on Matter/thread protocol ??
I am ready to reinstall one more time my HA

wmaker · December 27, 2024, 6:19pm

OK, if you are now only using Matter Server and Thread from your “remote” HA instance, then it makes things a little easier.

The HA Companion App uses the underlying Android Matter/Thread framework, and Android is known to store the first set of Thread dataset/credentials that it sees and it will only use that dataset/credentials for commissioning devices. In your case, your mobile device running Android has stored that Thread dataset/credentials stored on your mobile device. If you want to now commission devices on your “remoteHA” Thread instance, then you’ll need to follow the instructions Wally mentioned above for Google Play which should clear out the Thread dataset/credentials of your “main” instance.

Next you should go to your “remoteHA” instance’s Thread integration and click CONFIGURE, and make sure the remote HA instance’s Thread ha-thread-1d31 is not only “Preferred” but also click on its 3dots and select “Used for Android and iOS credentials”. You should then see an icon of a mobile device with a key inside. Then using the HA Android Companion App, follow Wally’s instructions for “Syncing” the Thread credentials. This should put the ha-thread-1d31’s dataset/credentials on the Android framework which in turn should be the one’s used for commissioning a Matter/Thread device from this same mobile device.