J. Nick Koston

There is an unrelated `uv.lock` file in this PR

Tagging this since the new feature was already added and we are missing the deprecation of the old entities

``` [05:10:53][I][runtime:100]: Component Runtime Statistics [05:10:53][I][runtime:101]: Period stats (last 60000ms): [05:10:53][I][runtime:122]: bluetooth_proxy: count=16418, avg=0.08ms, max=21ms, total=1283ms [05:10:53][I][runtime:122]: api: count=6511, avg=0.19ms, max=16ms, total=1205ms [05:10:53][I][runtime:122]: esp32_ble: count=6511, avg=0.17ms, max=18ms, total=1133ms [05:10:53][I][runtime:122]: esp32_ble_tracker:...

I think we need to enable the loop using the ISR safe helper since the ethernet callbacks happen in a different task AFAICT

I think, adding disabled by default switches, makes a lot of sense here. I wouldn’t worry too much about them turning off the Bluetooth script as they can also do...

Please follow the instruction at > Tracking down a memory leak of python objects https://community.home-assistant.io/t/2024-5-tracking-down-instability-issues-caused-by-integrations/724441

Sorry there aren't any docs on this. All the encryption code is in the _frame_helper.noise module

> I did some more testing and it seems to work fine if I `asyncio.sleep(0.2)` after sending a message to the motor. > > @bdraco this issue is related to...

Sorry about the conflicts

Down to one perf regression