This was explained in the stream, that HA keeps a track of what adaptor has a stronger signal - so it knows which adaptor to use to communicate to the device with.
However the ESP32s right now are passive only, you cannot control a device with a bluetooth_proxy - yet. But that is being worked on.
Great! This implementation seems really amazing, very flexible and poweful⌠Kudos guys!
Looking forward to being able to use ESP32 remotes for active connectionsâŚ
Great update!
Frustrating timing for me - just this week I swapped coordinator and did a full repair đ¤Ś
Thanks but the need for the hardware key is documented in both the Hardware integration and the default_config integration.
In contrast, the schedule key is not documented in the default_config integration. That omission may trip up users who donât use default_config and prefer to cherry-pick its integrations individually.
For those users itâs common practice to review default_config's documentation whenever thereâs a monthly release to see if any new integrations were added (in August it was bluetooth). However, for Septemberâs release, schedule isnât mentioned in default_config's documentation but itâs definitely part of the default_config integration.
Nice work all, especially excited to try out the weekly schedule!
Happy birthday Home Assistant! 
Great release yet again.
The weekly schedule helper has enabled me to delete hundreds of lines of code and countless input_booleans, input_datetimes and template sensors.
Some things that would be nice to have (feature request here):
Maybe help them get the documentation up to date? Anyone can submit a PR on any of the documentation pages, its not that difficult, there are some links at the bottom of every page for thatâŚ
ESP32-C3 support didnât make it for todayâs release. It is in the works.
I know how but I donât have the time for it. However you seem to know how as well so perhaps you can spare the time to do it.
Wonder if using the bluetooth proxy is related to how matter can provision new devices using Bluetooth connections between the individual devices
Once again, all good stuff! Excellent update!
I do wish History would include that elusive âAllâ option, though.
Also, Iâm a little confused by the Processor and memory usage addition to the Hardware page. It seems like a simplified duplication of effort/functionality, especially when we can already do the following quite easily:
Anybody has an issue with shelly.light? I have a dimmer that after the upgrade show the following error:
Unable to prepare setup for platform shelly.light: Platform not found (cannot import name âATTR_WHITE_VALUEâ from âhomeassistant.components.lightâ (/usr/src/homeassistant/homeassistant/components/light/init.py)).
Yes, it seems that it does not work at the moment.
Super excited for this release; especially the new LaMetric integration and Bluetooth proxy!
I did notice that adding new SwitchBot devices doesnât seem to work anymore after I updated to 2022.9. Has anyone else run into this issue?
Wasnât this in the release notes? LightEntity no longer supports white_value | Home Assistant Developer Docs
Also what integration is that? Not the built in one I think. If it is a custom one, ask the authors.
Didnât see that, but the issue is in Shelly for Hass integration, the crude fix described works.
For me itâs the Shelly 4 HASS integration causing this issue. I guess they will push an update soon.
Apart from bringing it to peoples attention (which is good), there is no point asking here for fixes.
Very cool release. My Switchbot Light Strip was discovered right away after the update!
But one question:
Is it possible to use an already in ESPresense installed ESP32 as Bluetooth proxy too?
Means can i install the Bluetooth Proxy in addition?
