Closed demono10000 closed 11 months ago
Do you have to remove/replug the SkyConnect? Or is just the restart of the Multiprotocol add-on enough?
Do you use the Thread functionality (e.g. do you have Thread devices paired?)
Restart of the add-on is enough. I have thread enabled and 3 border routers (home nest 2, homepod mini, skyconnect) and 2 smart sockets connected to them.
@demono10000 can you maybe disable the Thread part for a while and see if that changes things?
Unfortunately, there is not much we can do about this directly, as this is all code from Silicon Labs.
@demono10000 can you maybe disable the Thread part for a while and see if that changes things?
Unfortunately, there is not much we can do about this directly, as this is all code from Silicon Labs.
Should I follow this guide or is there simpler way to disable it? https://skyconnect.home-assistant.io/procedures/disable-multiprotocol/
Should I follow this guide or is there simpler way to disable it? https://skyconnect.home-assistant.io/procedures/disable-multiprotocol/
You can disable just the OpenThread Border Router part in the Siliconlabs Multiprotocol add-on configuration.
You'll have to restart the add-on after that.
Should I follow this guide or is there simpler way to disable it? https://skyconnect.home-assistant.io/procedures/disable-multiprotocol/
You can disable just the OpenThread Border Router part in the Siliconlabs Multiprotocol add-on configuration.
You'll have to restart the add-on after that.
Thanks, I will check if it helps.
Should I follow this guide or is there simpler way to disable it? https://skyconnect.home-assistant.io/procedures/disable-multiprotocol/
You can disable just the OpenThread Border Router part in the Siliconlabs Multiprotocol add-on configuration.
You'll have to restart the add-on after that.
It didn't help. I had to restart the add-on four times since disabling Thread.
Hm, I guess it is some lower level issue, e.g. your USB bus hangs or maybe a power supply issue. Do you see something in the Host logs?
What hardware are you using? Can you try changing things around USB, to see if that helps (replace USB hub if used, use a different USB plug)?
Hm, I guess it is some lower level issue, e.g. your USB bus hangs or maybe a power supply issue. Do you see something in the Host logs?
What hardware are you using? Can you try changing things around USB, to see if that helps (replace USB hub if used, use a different USB plug)?
I use Raspberry Pi 4 and I tried switching between USB 2 and USB 3 ports and it didn't help. I will try to replace the USB extension cable.
Hm, I guess it is some lower level issue, e.g. your USB bus hangs or maybe a power supply issue. Do you see something in the Host logs? What hardware are you using? Can you try changing things around USB, to see if that helps (replace USB hub if used, use a different USB plug)?
I use Raspberry Pi 4 and I tried switching between USB 2 and USB 3 ports and it didn't help. I will try to replace the USB extension cable.
Switching the USB extension cable didn't help. I may later try to switch the power supply.
I'm running roughly the same hardware (RP4, SkyConnect, 3.5A PS). It looks like the crash-loop goes in a couple of phases starting with a TX timeout and 10 minutes of internal Property-get::PROP_ENDPOINT_STATE
failures before fully crashing. Then something is internally restarting zigbeed and spamming the logs instead of letting the outer container crash.
Would it be possible to change s6 stuff to crash harder as mitigation? Restarting just zigbeed
automatically is fast, but letting the failure bubble up would restart the container.
Sep 04 06:15:54 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:50:57.188 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:134, chksum:6391, ecn:no, sec:yes, error:Drop, prio:low
Sep 04 06:15:54 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:50:57.188 [N] MeshForwarder-: src:[fd49:44c9:7890:1:9c1d:fd39:3963:368e]:40369
Sep 04 06:15:54 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:50:57.188 [N] MeshForwarder-: dst:[fd49:44c9:7890:1:965c:c45f:9ba1:a184]:5683
Sep 04 06:16:17 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:51:20.876 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:134, chksum:6391, ecn:no, sec:yes, error:Drop, prio:low
Sep 04 06:16:17 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:51:20.877 [N] MeshForwarder-: src:[fd49:44c9:7890:1:9c1d:fd39:3963:368e]:40369
Sep 04 06:16:17 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:51:20.877 [N] MeshForwarder-: dst:[fd49:44c9:7890:1:965c:c45f:9ba1:a184]:5683
Sep 04 06:16:58 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:01.213 [W] Platform------: radio tx timeout
Sep 04 06:16:58 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:01.214 [W] Platform------: RCP failure detected
Sep 04 06:16:58 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:01.214 [W] Platform------: Trying to recover (1/100)
Sep 04 06:17:02 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:05.231 [W] Platform------: Wait for response timeout
Sep 04 06:17:02 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:05.231 [W] Platform------: RCP failure detected
Sep 04 06:17:02 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:05.231 [W] Platform------: Trying to recover (2/100)
Sep 04 06:17:06 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:09.263 [W] Platform------: Wait for response timeout
Sep 04 06:17:06 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:09.263 [W] Platform------: RCP failure detected
Sep 04 06:17:06 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:09.263 [W] Platform------: Trying to recover (3/100)
Sep 04 06:17:10 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:13.295 [W] Platform------: Wait for response timeout
Sep 04 06:17:10 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:13.295 [W] Platform------: RCP failure detected
Sep 04 06:17:10 homeassistant addon_core_silabs_multiprotocol[579]: otbr-agent[306]: 3d.03:52:13.295 [W] Platform------: Trying to recover (4/100)
Sep 04 06:17:13 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 're_transmit_timeout' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1801 : Retransmit limit reached on endpoint #12
Sep 04 06:17:13 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'core_set_endpoint_in_error' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1125 : Setting ep#12 in error, new state: SL_CPC_STATE_ERROR_DESTINATION_UNREACHABLE
Sep 04 06:17:14 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:13:151318] WARNING : In function 're_transmit_timeout' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1801 : Retransmit limit reached on endpoint #12
Sep 04 06:17:14 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:13:151476] WARNING : In function 'core_set_endpoint_in_error' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1125 : Setting ep#12 in error, new state: SL_CPC_STATE_ERROR_DESTINATION_UNREACHABLE
Sep 04 06:17:14 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:13:252693] Info : Client disconnected
Sep 04 06:17:14 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:13:253066] Info : New client connection using library v4.3.1.0
Sep 04 06:17:14 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:13:253237] Info : Client disconnected
Sep 04 06:17:14 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:13:253601] Info : New client connection using library v4.3.1.0
Sep 04 06:17:33 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 're_transmit_timeout' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1801 : Retransmit limit reached on endpoint #0
Sep 04 06:17:33 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'core_set_endpoint_in_error' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1122 : System endpoint in error, new state: SL_CPC_STATE_ERROR_DESTINATION_UNREACHABLE. Restarting it.
Sep 04 06:17:33 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'sl_cpc_system_reset_system_endpoint' in file /usr/src/cpc-daemon/server_core/system_endpoint/system.c at line #498 : Dropping system command id #3 seq#12
Sep 04 06:17:33 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'core_set_endpoint_in_error' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1125 : Setting ep#12 in error, new state: SL_CPC_STATE_ERROR_DESTINATION_UNREACHABLE
Sep 04 06:17:33 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'on_disconnect_notification' in file /usr/src/cpc-daemon/server_core/core/core.c at line #225 : Failed to receive disconnection notification for ep#12
Sep 04 06:17:34 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:33:257268] WARNING : In function 're_transmit_timeout' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1801 : Retransmit limit reached on endpoint #0
Sep 04 06:17:34 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:33:257355] WARNING : In function 'core_set_endpoint_in_error' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1122 : System endpoint in error, new state: SL_CPC_STATE_ERROR_DESTINATION_UNREACHABLE. Restarting it.
Sep 04 06:17:34 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:33:257385] WARNING : In function 'sl_cpc_system_reset_system_endpoint' in file /usr/src/cpc-daemon/server_core/system_endpoint/system.c at line #498 : Dropping system command id #3 seq#12
Sep 04 06:17:34 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:33:257413] WARNING : In function 'core_set_endpoint_in_error' in file /usr/src/cpc-daemon/server_core/core/core.c at line #1125 : Setting ep#12 in error, new state: SL_CPC_STATE_ERROR_DESTINATION_UNREACHABLE
Sep 04 06:17:34 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:33:257459] WARNING : In function 'on_disconnect_notification' in file /usr/src/cpc-daemon/server_core/core/core.c at line #225 : Failed to receive disconnection notification for ep#12
Sep 04 06:17:35 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'property_get_single_endpoint_state_and_reply_to_pending_open_callback' in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
Sep 04 06:17:35 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'property_get_single_endpoint_state_and_reply_to_pending_open_callback' in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
Sep 04 06:17:36 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:35:257952] WARNING : In function 'property_get_single_endpoint_state_and_reply_to_pending_open_callback' in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
Sep 04 06:17:36 homeassistant addon_core_silabs_multiprotocol[579]: [23:17:35:258030] WARNING : In function 'property_get_single_endpoint_state_and_reply_to_pending_open_callback' in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
Sep 04 06:17:37 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'property_get_single_endpoint_state_and_reply_to_pending_open_callback' in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #176 : Property-get::PROP_ENDPOINT_STATE aborted
Sep 04 06:17:37 homeassistant addon_core_silabs_multiprotocol[579]: WARNING in function 'property_get_single_endpoint_state_and_reply_to_pending_open_callback' in file /usr/src/cpc-daemon/server_core/system_endpoint/system_callbacks.c at line #210 : Could not read endpoint state on the secondary
Note: unlike @demono10000, I sometimes find that service restart isn't enough. During start-up, the SiLabs flasher fails to auto-negotiate with the SkyConnect, falls back to probing by baudrate, and exits. Mitigation this time required USB in/out and restarting the add-on.
I agree with @agners that this is likely because of buggy vendor'ed code from SiliconLabs via (their @aautotte bot?) or firmware. Can we get an "upstream" label and keep this bug open? It would help to maintain a Google result for other sufferers to monitor. Looks like there are already other duplicates like #3192 that has some client-side details.
Plus the community share it to Silicon Labs and start spelunking for a software bug and patch/PR.
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[14:41:12] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[14:41:12] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2023-09-05 14:41:14 homeassistant universal_silabs_flasher.flash[185] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version=None, ot_rcp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2023-09-05 14:41:14 homeassistant universal_silabs_flasher.flasher[185] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2023-09-05 14:41:16 homeassistant universal_silabs_flasher.flasher[185] INFO Probing ApplicationType.CPC at 460800 baud
2023-09-05 14:41:20 homeassistant universal_silabs_flasher.flasher[185] INFO Probing ApplicationType.CPC at 115200 baud
2023-09-05 14:41:24 homeassistant universal_silabs_flasher.flasher[185] INFO Probing ApplicationType.CPC at 230400 baud
2023-09-05 14:41:29 homeassistant universal_silabs_flasher.flasher[185] INFO Probing ApplicationType.EZSP at 115200 baud
2023-09-05 14:41:34 homeassistant `universal_silabs_flasher.flasher[185]` INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service mdns: stopping
s6-rc: info: service banner: stopping Default: mDNSResponder (Engineering Build) (Aug 23 2023 18:31:24) stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[14:41:38] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
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.
I found a solution to my problem. I switched from ZHA to zigbee2mqtt and now my zigbee network works normally. I don't have to restart anything every few hours anymore.
Describe the issue you are experiencing
Every few hours my zigbee devices stop working and I have to restart Silicon Labs Multiprotocol addon to make my devices work again. When I check logs before restarting, I see that zigbee starts every few seconds. I am using skyconnect and it has been working fine for a few months, and now since about 2 weeks, it needs restart every few hours. After restarting the addon everything works fine for next few hours. core_silabs_multiprotocol_2023-08-26T17-16-48.488Z.log
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.3.2
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4994 Installed Version | 1.32.1 Stage | running Available Repositories | 1269 Downloaded Repositories | 3Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 26 sierpnia 2023 02:00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | eu-central-1-6.ui.nabu.casa certificate_status | ready can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 10.5 -- | -- update_channel | stable supervisor_version | supervisor-2023.08.1 agent_version | 1.5.1 docker_version | 23.0.6 disk_total | 109.3 GB disk_used | 33.5 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Mosquitto broker (6.2.1), File editor (5.6.0), TasmoAdmin (0.25.0), Google Assistant SDK (2.5.0), Advanced SSH & Web Terminal (15.0.7), AppDaemon (0.13.4), Grafana (9.0.3), InfluxDB (4.7.0), Home Assistant Google Drive Backup (0.111.1), Studio Code Server (5.10.1), Matter Server (4.9.0), Silicon Labs Multiprotocol (2.3.2)Dashboards
dashboards | 5 -- | -- resources | 0 views | 8 mode | storageRecorder
oldest_recorder_run | 16 sierpnia 2023 19:37 -- | -- current_recorder_run | 26 sierpnia 2023 15:59 estimated_db_size | 1035.96 MiB database_engine | sqlite database_version | 3.41.2Sonoff
version | 3.5.2 (2ad1cd7) -- | -- cloud_online | 0 / 4 local_online | 0 / 0Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
No response