addons: Battery devices are unresponsive - ZHA unstable since migration to Silicon Labs Multiprotocol

Describe the issue you are experiencing

Since my switch from Sonoff Dongle-E to Silicon Labs Multiprotocol on my HA Yellow ZHA especially battery devices are really unstable.

After update to HA 2023.6.3 they are no longer available.

Hope the error log helps to solve the issue soon!

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?

Silicon Labs Multiprotocol

What is the version of the add-on?

2.2.0

Steps to reproduce the issue

1. Restarted HA but battery devices can not used. They do not respond
2. Rebooted Host but battery devices can not used. They do not respond
3. Restarted Silicon Labs Multiprotocol Add-On, but error message stays …

System Health information

nothing in the logs

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?

[14:56:51:051786] Info : [CPCd v4.3.0.0] [Library API v3] [RCP Protocol v4]
[14:56:51:051993] Info : Git commit: 5264ecaef094c48b94f501b71edff4caaadb4545 / branch: 
[14:56:51:052012] Info : Sources hash: d0b1e4d46195ed78ab5fccd6b1dd93f77d56dafcd09d1613ec1806014d40d496
[14:56:51:052035] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[14:56:51:052129] Info : Reading cli arguments
[14:56:51:052144] Info : /usr/local/bin/cpcd 
[14:56:51:060663] Info : Reading configuration
[14:56:51:060688] Info :   file_path = /usr/local/etc/cpcd.conf
[14:56:51:060690] Info :   instance_name = cpcd_0
[14:56:51:060693] Info :   socket_folder = /dev/shm
[14:56:51:060695] Info :   operation_mode = MODE_NORMAL
[14:56:51:060698] Info :   use_encryption = false
[14:56:51:060700] Info :   binding_key_file = /etc/binding-key.key
[14:56:51:060703] Info :   stdout_tracing = false
[14:56:51:060705] Info :   file_tracing = false
[14:56:51:060707] Info :   lttng_tracing = false
[14:56:51:060709] Info :   enable_frame_trace = false
[14:56:51:060711] Info :   traces_folder = /dev/shm/cpcd-traces
[14:56:51:060713] Info :   bus = UART
[14:56:51:060715] Info :   uart_baudrate = 460800
[14:56:51:060761] Info :   uart_hardflow = true
[14:56:51:060764] Info :   uart_file = /dev/ttyAMA1
[14:56:51:060767] Info :   fu_recovery_pins_enabled = false
[14:56:51:060769] Info :   fu_connect_to_bootloader = false
[14:56:51:060771] Info :   fu_enter_bootloader = false
[14:56:51:060773] Info :   restart_cpcd = false
[14:56:51:060775] Info :   application_version_validation = false
[14:56:51:060777] Info :   print_secondary_versions_and_exit = false
[14:56:51:060779] Info :   use_noop_keep_alive = false
[14:56:51:060781] Info :   reset_sequence = true
[14:56:51:060783] Info :   stats_interval = 0
[14:56:51:060785] Info :   rlimit_nofile = 2000
[14:56:51:060788] Info : ENCRYPTION IS DISABLED 
[14:56:51:060790] Info : Starting daemon in normal mode
[14:56:51:082935] Info : Connecting to Secondary...
[14:56:51:156911] Info : RX capability is 256 bytes
[14:56:51:156946] Info : Connected to Secondary
[14:56:51:158185] Info : Secondary Protocol v4
[14:56:51:160983] Info : Secondary CPC v4.3.0
[14:56:51:162388] Info : Secondary bus bitrate is 460800
[14:56:51:165349] Info : Secondary APP vUNDEFINED
[14:56:51:165616] Info : Daemon startup was successful. Waiting for client connections
[14:56:52] INFO: Starting zigbeed...
[14:56:53] INFO: Setup OTBR firewall...
[14:56:54] INFO: Starting otbr-agent...
[14:56:53:502274] Info : New client connection using library v4.3.0.0
[14:56:53:505402] Info : Opened connection socket for ep#12
[14:56:53:505897] Info : Endpoint socket #12: Client connected. 1 connections
otbr-agent[311]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[311]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[311]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[311]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2
otbr-agent[311]: [NOTE]-ILS-----: Infra link selected: eth0
otbr-agent[311]: 49d.17:04:11.165 [C] Platform------: mCpcBusSpeed = 115200
[14:56:54:108182] Info : New client connection using library v4.3.0.0
[14:56:54:112127] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[311]: 00:00:00.103 [N] BorderRouter--: BR ULA prefix: fd67:bb3c:b8c7::/48 (loaded)
otbr-agent[311]: 00:00:00.103 [N] BorderRouter--: Local on-link prefix: fda1:39b2:4fdf:2a88::/64
otbr-agent[311]: 00:00:00.184 [N] Mle-----------: Role disabled -> detached
otbr-agent[311]: 00:00:00.190 [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.
[14:56:58] 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
otbr-agent[311]: 00:00:25.795 [N] Mle-----------: RLOC16 6000 -> fffe
otbr-agent[311]: 00:00:25.800 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[311]: 00:00:26.316 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[311]: 00:00:32.819 [N] RouterTable---: Allocate router id 24
otbr-agent[311]: 00:00:32.819 [N] Mle-----------: RLOC16 fffe -> 6000
otbr-agent[311]: 00:00:32.821 [N] Mle-----------: Role detached -> leader
otbr-agent[311]: 00:00:32.822 [N] Mle-----------: Partition ID 0x73209f9a
otbr-agent[311]: 00:00:32.877 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[311]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Accepted connection 7.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9cda:d1ff:fe8b:863d/veth4cf0ac3/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9cda:d1ff:fe8b:863d/veth4cf0ac3/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9cda:d1ff:fe8b:863d/veth4cf0ac3/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::9cda:d1ff:fe8b:863d/veth4cf0ac3/27
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b8cf:17ff:fe8f:6a09/veth8bae502/29
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4a8:36ff:fe10:9cfd/vethf705318/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4a8:36ff:fe10:9cfd/vethf705318/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4a8:36ff:fe10:9cfd/vethf705318/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d43c:fdff:fea1:da67/veth016c6f3/33

Additional information

No response