Sonoff Dongle E + Matter over Thread (+ ZHA)

[Towtoll]

Describe the issue you are experiencing

Hi,

I'm new in domotics.

I run HA in an unraid VM
I'm trying to pair an aqara P2 with HA using Matter server with SiliconLab Silicon Labs Multiprotocol as a test before buying more snesors. Obiously if I'm here that's because I failing to do so. I'm using an Android as compagnon app.
I have no zigbee device for now so my focus goes on thread, but later I'll use zigbee too
I started by following this guide : https://darkxst.github.io/silabs-firmware-builder/ and :

• flashed SONOFF dongle-E with multipan 4.3.2
• installed everything (SiliconLab + Matter server + ZHA with canal change to 15)
• configured everything (like in the guide minus the OTBR firewall, i've seem that this could cause problems)

When trying to pair, I got an error type "Thread connectivity probelm".

I diged and found that there was a 4.4.0 firmware for the dongle so I tried this but same problem (after creating a new HA VM from scratch too)
I checked Ipv6 connectivity and seems good on HA

I don't understand what i'm doing wrong. :(

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Almond

What is the version of the add-on?

2.4.3

Steps to reproduce the issue

1. Fresh system install
2. Config SiliconLab Multiprotocol
3. Trying pairing a matter device
   ...

System Health information

System Information

version	core-2024.1.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.6
os_name	Linux
os_version	6.1.71-haos
arch	x86_64
timezone	Europe/Paris
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.33.0
Stage	running
Available Repositories	1383
Downloaded Repositories	1
HACS Data	ok

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.4
update_channel	stable
supervisor_version	supervisor-2023.12.1
agent_version	1.6.0
docker_version	24.0.7
disk_total	30.8 GB
disk_used	4.8 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Silicon Labs Flasher (0.2.0), Terminal & SSH (9.8.1), Silicon Labs Multiprotocol (2.4.3), Matter Server (5.0.2), Multipan Flasher (0.2.0)

Dashboards

dashboards	1
resources	0
mode	auto-gen

Recorder

oldest_recorder_run	17 janvier 2024 à 12:21
current_recorder_run	17 janvier 2024 à 15:46
estimated_db_size	0.45 MiB
database_engine	sqlite
database_version	3.41.2

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

otbr-agent[303]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[303]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[303]: [NOTE]-ILS-----: Infra link selected: enp2s0
otbr-agent[303]: 49d.22:30:46.780 [C] Platform------: mCpcBusSpeed = 115200
[2024-01-17T17:53:05.031671Z] Info : [CPCd v4.4.0.0] [Library API v3] [RCP Protocol v5]
[2024-01-17T17:53:05.031684Z] Info : Git commit: 1fcaa81347466165f81e4533ee4471e9c3b6db0a / branch: 
[2024-01-17T17:53:05.031685Z] Info : Sources hash: 1e938c77bacd9c9d6d8fe7b457208a3a8a2435bd6374a1918605ffb864bf1ebe
[2024-01-17T17:53:05.031687Z] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #187 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[2024-01-17T17:53:05.031695Z] Info : Reading cli arguments
[2024-01-17T17:53:05.031699Z] Info : /usr/local/bin/cpcd 
[2024-01-17T17:53:05.032887Z] Info : Reading configuration
[2024-01-17T17:53:05.032889Z] Info :   file_path = /usr/local/etc/cpcd.conf
[2024-01-17T17:53:05.032889Z] Info :   instance_name = cpcd_0
[2024-01-17T17:53:05.032890Z] Info :   socket_folder = /dev/shm
[2024-01-17T17:53:05.032890Z] Info :   operation_mode = MODE_NORMAL
[2024-01-17T17:53:05.032890Z] Info :   use_encryption = false
[2024-01-17T17:53:05.032891Z] Info :   binding_key_file = /etc/binding-key.key
[2024-01-17T17:53:05.032891Z] Info :   stdout_tracing = false
[2024-01-17T17:53:05.032891Z] Info :   file_tracing = false
[2024-01-17T17:53:05.032891Z] Info :   lttng_tracing = false
[2024-01-17T17:53:05.032892Z] Info :   enable_frame_trace = false
[2024-01-17T17:53:05.032892Z] Info :   traces_folder = /dev/shm/cpcd-traces
[2024-01-17T17:53:05.032892Z] Info :   bus = UART
[2024-01-17T17:53:05.032893Z] Info :   uart_baudrate = 460800
[2024-01-17T17:53:05.032893Z] Info :   uart_hardflow = false
[2024-01-17T17:53:05.032893Z] Info :   uart_file = /dev/ttyACM0
[2024-01-17T17:53:05.032894Z] Info :   fu_recovery_pins_enabled = false
[2024-01-17T17:53:05.032894Z] Info :   fu_connect_to_bootloader = false
[2024-01-17T17:53:05.032894Z] Info :   fu_enter_bootloader = false
[2024-01-17T17:53:05.032894Z] Info :   restart_cpcd = false
[2024-01-17T17:53:05.032895Z] Info :   application_version_validation = false
[2024-01-17T17:53:05.032895Z] Info :   print_secondary_versions_and_exit = false
[2024-01-17T17:53:05.032895Z] Info :   use_noop_keep_alive = false
[2024-01-17T17:53:05.032895Z] Info :   reset_sequence = true
[2024-01-17T17:53:05.032896Z] Info :   stats_interval = 0
[2024-01-17T17:53:05.032896Z] Info :   rlimit_nofile = 2000
[2024-01-17T17:53:05.032896Z] Info : ENCRYPTION IS DISABLED 
[2024-01-17T17:53:05.045316Z] Info : Starting daemon in normal mode
[2024-01-17T17:53:05.057157Z] Info : Connecting to Secondary...
[2024-01-17T17:53:05.135784Z] Info : RX capability is 256 bytes
[2024-01-17T17:53:05.135787Z] Info : Connected to Secondary
[2024-01-17T17:53:05.138742Z] Info : Secondary Protocol v5
[2024-01-17T17:53:05.144666Z] Info : Secondary CPC v4.4.0
[2024-01-17T17:53:05.150698Z] Info : Secondary bus bitrate is 460800
[2024-01-17T17:53:05.156737Z] Info : Secondary APP vUNDEFINED
[2024-01-17T17:53:05.156757Z] Info : Daemon startup was successful. Waiting for client connections
[2024-01-17T17:53:05.440232Z] Info : New client connection using library v4.4.0.0
[2024-01-17T17:53:05.444038Z] Info : Opened connection socket for ep#12
[2024-01-17T17:53:05.447039Z] Info : Endpoint socket #12: Client connected. 1 connection(s)
[2024-01-17T17:53:06.371294Z] Info : New client connection using library v4.4.0.0
[2024-01-17T17:53:06.373705Z] Info : Endpoint socket #12: Client connected. 2 connection(s)
otbr-agent[303]: 00:00:00.112 [N] RoutingManager: BR ULA prefix: fd9a:9da9:c24a::/48 (loaded)
otbr-agent[303]: 00:00:00.112 [N] RoutingManager: Local on-link prefix: fd7d:2516:da5:e8a9::/64
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:00.113 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: 00:00:00.124 [N] Mle-----------: Role disabled -> detached
otbr-agent[303]: 00:00:00.134 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[303]: 00:00:00.136 [W] Platform------: [netif] ADD [U] fe80:0:0:0:8caf:9297:16fa:d141 failed (InvalidArgs)
otbr-agent[303]: 00:00:00.136 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[303]: 00:00:00.136 [W] Platform------: [netif] ADD [U] fd61:d1ba:fbb9:a899:c10f:567c:f5da:d48e failed (InvalidArgs)
otbr-agent[303]: 00:00:00.136 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[303]: 00:00:00.136 [W] Platform------: [netif] ADD [U] fd61:d1ba:fbb9:a899:0:ff:fe00:3000 failed (InvalidArgs)
otbr-agent[303]: 00:00:00.136 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[18:53:07] 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
Listening on port 9999 for connection...
Accepting connection.
otbr-agent[303]: 00:00:26.023 [N] Mle-----------: RLOC16 3000 -> fffe
otbr-agent[303]: 00:00:26.026 [W] Platform------: [netif] Failed to process request#5: Operation not supported
otbr-agent[303]: 00:00:26.683 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[303]: 00:00:33.183 [N] RouterTable---: Allocate router id 12
otbr-agent[303]: 00:00:33.183 [N] Mle-----------: RLOC16 fffe -> 3000
otbr-agent[303]: 00:00:33.185 [N] Mle-----------: Role detached -> leader
otbr-agent[303]: 00:00:33.186 [N] Mle-----------: Partition ID 0x62d0937c
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:33.196 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: 00:00:33.196 [W] Platform------: [netif] Failed to process request#6: File exists
otbr-agent[303]: 00:00:33.196 [W] Platform------: [netif] ADD [U] fd61:d1ba:fbb9:a899:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[303]: 00:00:33.196 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:33.843 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[303]: 00:00:33.844 [W] Platform------: [netif] ADD [U] fd61:d1ba:fbb9:a899:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[303]: 00:00:33.844 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[303]: 00:00:33.844 [W] Platform------: [netif] ADD [U] fd61:d1ba:fbb9:a899:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[303]: 00:00:33.844 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:35.652 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: 00:00:35.652 [W] Platform------: [netif] ADD [U] fd9a:9da9:c24a:1:f8ca:8fd0:12bc:c745 failed (InvalidArgs)
otbr-agent[303]: 00:00:35.652 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:36.334 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:45.804 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: 00:00:45.804 [W] Platform------: [netif] ADD [U] fd61:d1ba:fbb9:a899:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[303]: 00:00:45.804 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

Additional information

No response

[Waghead]

I have the same problem. Bought a new Sonoff because I thought it was hardware related..

[jotbed]

I have the same Problem. Is there a possibility to install an old version of the addon?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.