Closed KitHubek closed 1 year ago
version | core-2023.5.4 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.10.11 |
os_name | Linux |
os_version | 6.1.25 |
arch | x86_64 |
timezone | Europe/Warsaw |
config_dir | /config |
@bdraco
today i made test. I disabled all integrations, all devices. Stays onlu Supervisor, reboot HA and run in terminal py-spy command as below:
and HA freeze and after about 10 minutes rebooted But when HA freeze i connect to HA host via ssh and done top command, because i think that CPUI usage will 100% and host will unresponsive, byt NOT. I can connect cia ssh, and CPU usage is very low. See screen below:
@bdraco
after update HA to 2023.6.0 py-spy working!
here is svg file after command:
./py-spy record --pid 66 --rate 10 --duration 60 --output spy.svg
Great. Can you zip up the file before posting? GitHub compresses them and mutates them.
also if you can capture at a higher rate that would help
ok @bdraco done with sample: 100 150 200 500
The websocket looks a bit busy. If you open the inspector panel in your browser, how fast are the messages coming in?
You mean: open HA in browser (in my case: newest chrome) right click and INSPECT?
If yes, its open about 1 sec or less. I can say: right away
In the network tab, find the websocket. You can look at the messages come over.
You may need to shift
+ reload
to get it to appear
ok, this load right away. i cant see any delay
I think the problem is likely higher up the bluetooth stack in bluez or bleak
I just found https://github.com/hbldh/bleak/pull/1329 but there seems to be more issues
I setup an x86_64 intel nuc system with the exact same adapter (I moved it from an aarch64 ARM system) and I'm having trouble with it as well.
It works perfectly fine on the aarch64 ARM system
It seems like the problem is in the kernel or bluez
ok, thanks for this work. But is main question: What now? What next? Lock working ok with only btproxy but, as You know, this is another device, another power plug, another wifi ora lan client. This is not the same as local bt adapter plugged into HA hardware.
big thanks
https://github.com/hbldh/bleak/pull/1329 will fix the cases where we wait the whole timeout for the device to reappear
https://github.com/home-assistant/core/pull/99520 will fix the case where the device is removed from the bus while connecting and than we take a long time to timeout.
If that doesn't fix it we can reopen this case and hopefully the new logging will give us a hint what is going on.
The problem
@bdraco
Iam using HA with Yours fix esphome folder in dir custom component and all as i wrote in this https://github.com/home-assistant/core/issues/90265 thread worked fine.
BUT
When i see new verison 2023.5.3 HA included this fix i delete esphome dir from custom component dir and update HA. This was 14 may. Today is 16 may, i tested many scenario, and i have to say that something is wrong. Something another than before.
Now problem is, that connection not go via bt-proxy and this make another delay. I not made any change in my config, only one change was: delete esphome folder from custom component and update HA to 2023.5.3. When connection is via bt-proxy all is ok and without delay. But i dont know why, not every connection going via bt-proxy. Before update to 2023.5.3 everyome lock connection go via bt-proxy
what to do?
Below logs when connection go via proxy and NOT (via app: tap unlock and when unlocked tap lock and lock locked)
What version of Home Assistant Core has the issue?
2023.5.3
What was the last working version of Home Assistant Core?
2023.5.2 with custom fix and earlier
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ESPHome
Link to integration documentation on our website
https://www.home-assistant.io/integrations/esphome
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response