Chris Xiao

Done! Enabled Bluetooth, restarted HA, and ran `profiler.start` with `seconds: 10` once startup completed. [callgrind.out.1667704104081537.txt](https://github.com/home-assistant/core/files/9945078/callgrind.out.1667704104081537.txt)

[callgrind.out.1667704677477982.txt](https://github.com/home-assistant/core/files/9945086/callgrind.out.1667704677477982.txt) Re-ran with 60 seconds

I'm running HA OS 9.3, on Proxmox 7.2 (latest). Not sure how I could check CPU time, but I'm attaching 2 screenshots of `top` running on HAOS, one with Bluetooth...

Interesting that an RPi4 can do better... I'll look into this a bit more and test on some different systems, but I'm suspecting this might have something to do with...

I installed Debian 11 directly on the same host and tested this again with both [HA Core](https://www.home-assistant.io/installation/linux#install-home-assistant-core) and [HA Container](https://www.home-assistant.io/installation/linux#install-home-assistant-container). I'm seeing very similar CPU usage patterns as the OS...

I have switched to dbus-broker following [the instructions](https://github.com/bus1/dbus-broker/wiki)

> It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the `current` branch. Targeting `rc` branch as...