openthread border router add-on consuming 100% CPU. #3490
Comments
|
Hm, so this is the last line of the startup log? Sounds like the universal-silabs-flasher is hanging then 🤔 Is this reproducible, as in when you restart the add-on it hangs on the same line and CPU goes to 100% on one CPU? @puddly do you happen to have an idea? |
|
Hi, Yeah, that was the last line. I had already rebooted my HA VM, but no to no avail, it spun up to 100% (1 of 4 cores assigned to it) right away after HA had finished starting. I disabled the addon for now, but let me check again. |
|
Check, I just spun up the addon again, and it immediately goes to 100% |
|
The flasher has explicit timeouts for every CPC command so it should never stall. The only thing I can imagine is if it's being overwhelmed by a continuous stream of data, which I think I've seen happen once. Do we have a way to enable verbose logging for the flasher within the addon? |
|
@kluner from the system console (I assume you have access to it on your VM), can you use |
yep, confirmed:
|
|
Can you try run it manually with verbose option? |
|
and unfortunately no strace in haos, or I could have a peak at what is happening at the syscall level. |
yeah, but give me a bit to see if I can get a real ssh into haos going, so I can copy/paste. |
👍 , fwiw, there is a guide how to do this in our developer docs: https://developers.home-assistant.io/docs/operating-system/debugging#ssh-access-to-the-host |
|
oooh, great suggestion. ok, so I half anticipate that kill on python would kill the whole container and cause it to restart, but it seems something did happen: |
|
followed by which seems to run stable currently, at no excessive cpu consumption. |
|
possible (likely) side-effect: zigbee integration is stuck initialising. let's see if I can shake it loose. |
|
Uh, do you use the same device in the ZHA integration maybe? 🤔 The ZHA integration should not point to the that serial port. This would create havoc. We currently discover the device still as ZHA device, but that will change in the future. Currently you have to explicitly ignore the discovered ZHA entry (see https://skyconnect.home-assistant.io/procedures/enable-thread/). |
You know, that would make sense in it causing absolute chaos. But no, I use the socket in ZHA.
|
|
btw, it came back. It’s doing 100% again. |
|
Do you have the Silicon Labs Multiprotocol add-on enabled at the same time? If that accesses the serial port at the same time it would explain the problem as well... |
|
Actually,I do. Funny thing: I have had this configuration since I got the skyconnect in. It never caused problems. So what is the recommended configuration here? Only multi, and matter server and ZHA to handle the protocol stacks? I do not have matter things at the moment, but I do expect that to change shortly. |
|
Unfortunately, the Silicon Labs Multiprotocol add-on showed problems for a lot of folks especially when they started to add devices to the Thread side 😢 So currently we only recommend dedicated setups: Use a radio for Zigbee and one radio for Thread. Maybe you already have a second radio available? 🤔 Alternatively, if you have Google or Apple BR, our Matter stack can make use of those as well (the devices still will be directly associated with Home Assistant on the application/Matter level). |
|
Well, I can easily turn off all the thread and matter stuff currently, it's not really getting used. It's just an obstacle for the future. What do you mean with using the Apple BR? The HomeKit bridge? Can the matter addon use that? That would kinda fix the whole problem anyway. |
No, HomePod and such, see https://www.home-assistant.io/integrations/thread#list-of-thread-border-router-devices. |
|
ah, right check. Well I was looking for an excuse to buy a matter capable one anyway. ;-) I reset the firmware on skyconnect to zigbee, and hooked ZHA to it again. Seems to work fine again now. |
Describe the issue you are experiencing
Since the last update of HAOS and Homeassistant to below versions, the open thread border router add on has started using 100% CPU. Turning overal VM cpu usage from 3% to 27%. (enough to trigger the fans).
logs show no remarkable information:
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?
CEC Scanner
What is the version of the add-on?
2.4.7
Steps to reproduce the issue
...
System Health information
System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
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: