Silicon Labs Multiprotocol stops working and needs restart every few hours #3193
Comments
|
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. |
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. |
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)? |
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 Would it be possible to change s6 stuff to crash harder as mitigation? Restarting just |
|
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. |
|
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
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Sonoff
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?
Additional information
No response
The text was updated successfully, but these errors were encountered: