addons: Multiprotocol Add-On Crashing
Describe the issue you are experiencing
About 1-2 hours after restarting Home Assistant, the Multiprotocol add-on crashes. This issue began after updating to Multiprotocol version 2.4.3. No manual configuration changes were made on my end. The current workaround was to enable the watchdog to restart the Multiprotocol addon when it crashes.
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.4.3
Steps to reproduce the issue
- Updated to version 2.4.3.
- The addon crashes with no intervention
System Health information
## System Information
version | core-2024.1.2
-- | --
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 | America/New_York
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 5000
Installed Version | 1.33.0
Stage | running
Available Repositories | 1370
Downloaded Repositories | 13
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 11.4
-- | --
update_channel | stable
supervisor_version | supervisor-2023.12.0
agent_version | 1.6.0
docker_version | 24.0.7
disk_total | 30.8 GB
disk_used | 6.7 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Duck DNS (1.15.0), Studio Code Server (5.15.0), Mosquitto broker (6.4.0), Matter Server (5.0.2), Terminal & SSH (9.8.1), Silicon Labs Multiprotocol (2.4.3), File editor (5.7.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 7
-- | --
resources | 6
views | 24
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | January 2, 2024 at 10:40 PM
-- | --
current_recorder_run | January 11, 2024 at 9:41 PM
estimated_db_size | 170.61 MiB
database_engine | sqlite
database_version | 3.41.2
</details>
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[300]: 00:00:00.196 [N] Mle-----------: Role disabled -> detached
otbr-agent[300]: 00:00:00.198 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[300]: 00:00:00.215 [W] Platform------: [netif] ADD [U] fe80:0:0:0:a085:be66:9e98:ea89 failed (InvalidArgs)
otbr-agent[300]: 00:00:00.215 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[300]: 00:00:00.216 [W] Platform------: [netif] ADD [U] fd7c:f176:af3f:19d2:39ea:badc:584e:2315 failed (InvalidArgs)
otbr-agent[300]: 00:00:00.216 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[300]: 00:00:00.216 [W] Platform------: [netif] ADD [U] fd7c:f176:af3f:19d2:0:ff:fe00:5000 failed (InvalidArgs)
otbr-agent[300]: 00:00:00.216 [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
[08:43:09] 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[300]: 00:00:12.144 [N] Mle-----------: RLOC16 5000 -> fffe
otbr-agent[300]: 00:00:12.148 [W] Platform------: [netif] Failed to process request#5: Operation not supported
otbr-agent[300]: 00:00:12.513 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[300]: 00:00:13.606 [N] Mle-----------: RLOC16 fffe -> c807
otbr-agent[300]: 00:00:13.611 [N] Mle-----------: Role detached -> child
otbr-agent[300]: 00:00:13.637 [W] Platform------: [netif] ADD [U] fd7c:f176:af3f:19d2:0:ff:fe00:c807 failed (InvalidArgs)
otbr-agent[300]: 00:00:13.637 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[300]: 00:00:15.850 [W] Platform------: [netif] ADD [U] fd7c:551:6bda:1:8cc0:6701:96e1:9cec failed (InvalidArgs)
otbr-agent[300]: 00:00:15.850 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
Accepted connection 8.
otbr-agent[300]: 00:00:35.815 [W] Platform------: [netif] ADD [U] fd7c:f176:af3f:19d2:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[300]: 00:00:35.815 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[300]: 00:00:51.161 [N] Mle-----------: RLOC16 c807 -> 5000
otbr-agent[300]: 00:00:51.165 [N] Mle-----------: Role child -> router
otbr-agent[300]: 00:00:51.165 [N] Mle-----------: Partition ID 0x7dbd5b8b
otbr-agent[300]: 00:00:51.167 [W] Platform------: [netif] Failed to process request#9: Operation not supported
otbr-agent[300]: 00:00:51.167 [W] Platform------: [netif] Successfully added an external route ::/0 in kernel
otbr-agent[300]: 00:00:51.193 [W] Platform------: [netif] Failed to process request#10: File exists
otbr-agent[300]: 00:00:51.193 [W] Platform------: [netif] Failed to process request#11: Operation not supported
otbr-agent[300]: 00:00:51.427 [W] Platform------: [netif] Successfully deleted an external route ::/0 in kernel
otbr-agent[300]: 00:00:51.447 [W] Platform------: [netif] Failed to process request#13: Operation not supported
otbr-agent[300]: 00:00:54.382 [N] Ip6-----------: Failed to find valid route for: fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec
otbr-agent[300]: 00:00:56.146 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:154, chksum:28d3, ecn:no, sec:yes, error:ReassemblyTimeout, prio:net, rss:-75.0, radio:15.4
otbr-agent[300]: 00:00:56.146 [N] MeshForwarder-: src:[fe80:0:0:0:24de:32ef:b878:b9e3]:19788
otbr-agent[300]: 00:00:56.146 [N] MeshForwarder-: dst:[ff02:0:0:0:0:0:0:1]:19788
otbr-agent[300]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[300]: 00:00:56.343 [W] Platform------: [netif] ADD [U] fd7c:f176:af3f:19d2:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[300]: 00:00:56.344 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[300]: 00:00:56.346 [W] Platform------: [netif] Failed to process request#16: File exists
otbr-agent[300]: 00:00:56.346 [W] Platform------: [netif] ADD [U] fd7c:f176:af3f:19d2:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[300]: 00:00:56.346 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[300]: 00:00:56.347 [W] Platform------: [netif] Failed to process request#18: File exists
otbr-agent[300]: 00:01:00.130 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:65f2, ecn:no, sec:yes, error:AddressQuery, prio:low, radio:all
otbr-agent[300]: 00:01:00.130 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:60695
otbr-agent[300]: 00:01:00.130 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:01:49.183 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[300]: 00:01:49.183 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:182, chksum:a13c, ecn:no, to:0xc800, sec:yes, error:ChannelAccessFailure, prio:low, radio:15.4
otbr-agent[300]: 00:01:49.183 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:56775
otbr-agent[300]: 00:01:49.183 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:aa0a:aba2:d333:30fb]:5683
otbr-agent[300]: 00:01:49.440 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[300]: 00:01:49.684 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[300]: 00:01:51.651 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[300]: 00:01:51.652 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:182, chksum:a13c, ecn:no, to:0xc800, sec:yes, error:ChannelAccessFailure, prio:low, radio:15.4
otbr-agent[300]: 00:01:51.652 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:56775
otbr-agent[300]: 00:01:51.652 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:aa0a:aba2:d333:30fb]:5683
otbr-agent[300]: 00:02:25.156 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:b979, ecn:no, sec:yes, error:AddressQuery, prio:low, radio:all
otbr-agent[300]: 00:02:25.156 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:56822
otbr-agent[300]: 00:02:25.156 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:02:25.156 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:b979, ecn:no, sec:yes, error:AddressQuery, prio:low, radio:all
otbr-agent[300]: 00:02:25.156 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:56822
otbr-agent[300]: 00:02:25.156 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:02:29.596 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:b979, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:02:29.597 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:56822
otbr-agent[300]: 00:02:29.597 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:03:53.146 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:8b8c, ecn:no, sec:yes, error:AddressQuery, prio:low, radio:all
otbr-agent[300]: 00:03:53.146 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:41710
otbr-agent[300]: 00:03:53.146 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:03:53.455 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:8b8c, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:03:53.455 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:41710
otbr-agent[300]: 00:03:53.455 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:05:21.093 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:21e7, ecn:no, sec:yes, error:AddressQuery, prio:low, radio:all
otbr-agent[300]: 00:05:21.093 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:55329
otbr-agent[300]: 00:05:21.093 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:05:21.160 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:21e7, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:05:21.160 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:55329
otbr-agent[300]: 00:05:21.160 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:05:25.416 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:21e7, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:05:25.416 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:55329
otbr-agent[300]: 00:05:25.416 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:06:47.434 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:c80d, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:06:47.434 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:40093
otbr-agent[300]: 00:06:47.434 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:06:50.149 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:c80d, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:06:50.149 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:40093
otbr-agent[300]: 00:06:50.149 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:08:18.094 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:07bb, ecn:no, sec:yes, error:AddressQuery, prio:low, radio:all
otbr-agent[300]: 00:08:18.094 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:34717
otbr-agent[300]: 00:08:18.094 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:08:18.180 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:07bb, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:08:18.180 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:34717
otbr-agent[300]: 00:08:18.180 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
otbr-agent[300]: 00:08:23.240 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:94, chksum:07bb, ecn:no, sec:yes, error:Drop, prio:low, radio:all
otbr-agent[300]: 00:08:23.240 [N] MeshForwarder-: src:[fd7c:551:6bda:1:8cc0:6701:96e1:9cec]:34717
otbr-agent[300]: 00:08:23.240 [N] MeshForwarder-: dst:[fd7c:551:6bda:1:6fdd:ef0d:d916:e0ec]:5683
### Additional information
When the multiprotocol addon crashes, this causes the ZHA integration to stop working until multiprotocol is restarted.About this issue
- Original URL
- State: closed
- Created 6 months ago
- Reactions: 2
- Comments: 30 (4 by maintainers)
Hey @agners, thank you for the honest and explanatory words! I really can understand your side, but for the buyer of the sticks, who has normally paid twice as much as for the Sonoff dongle, there is a certain expectation. The stick’s website also points out that it is still under development, but it says “Zigbee and Thread at the same time”. Perhaps more information during installation and on the website would prevent people from using it in the production environment!? I will, as I “fortunately” don’t use a Thread device yet, revert to Zigbee only and hope it works then. It’s always hard to explain to the wife why the light suddenly doesn’t come on when she’s standing in the kitchen in the dark in the morning 😄
Greetings! Henry
Unfortunately, previous versions also did not work for all users error free 😢 . Especially folks which were using the Thread network as well. So we do have to continue development, and update to newer version.
We’ve recently updated to Silicon Labs latest version based on Gecko SDK 4.4.0. Unfortunately, as many of you observe, this seems to have negative effect on some system.
@Guardempire (and others) Home Assistant creates a add-on specific backup by default. If previous versions do work fine for you, you can simply downgrade to that previous version and skip/ignore this update.
The multiprotocol solution has also some technical downsides. If you have two sticks anyways, I’d consider using them to form separate networks (as linked above, see this article).
We’ll continue to work with Silicon Labs to get to the bottom of (all) the issues. 🤞
I have the same problem, ZHA is in initialization status and nothing works anymore… unti a complete reboot. I have the Skyconnect stick and it runs in multiprotocol mode, although I don’t have any Thread devices yet. But exactly this mode was the reason to buy it and switch from Sonoff… Because it was supposed to support everything and now the solution is to let it run on Zigbee only and use something else for Thread? It worked completely error-free and without failures until a certain update.
I’m facing the same issue. WIth sky connect stick
Maybe a disclaimer for the product: Only for development purposes and don’t use it in production environment.
Hi @agners ,
This is the kind of communication I like. Understanding, informative, helpful and hopeful. Thank you!
I also have this issue. Crashed 2 times in the middle of the night. ZHA in combination with Skyconnect. I now have the watchdog running and hope it will restart at the next crash so my Zigbee network will not be broken for hours…
Same here. ~80 zigbee devices in the network. RPi 4, SkyConnect stick. Stable until 2.4.3 update today. Running ZHA.
The ever first version I installed was 2.4.3 (today), so I do not have any older versions in a backup. Is there any way to install an older version directly?
Looks like the exact same problem as above, thanks.
Make sure you keep the watchdog enabled for the addon so that it auto-restarts.