450ms/450ms still doesn't work.

Might need to be 450ms interval, 160ms window?

It may make more sense to enable the coexistence configurations instead of this.

Ideally we land on a config that works for Wi-Fi and can still operate Erik's lock as that's going to be a great test case for this.

Will come back to this after beta and release. I want to get home-assistant/core#88603 in first as well

Looks like the defaults work well for wifi devices but much more and things get a bit unstable.

home-assistant/core#87158 (comment)

Still need to collect more feedback and look into if the built in coexistence settings will improve the situation.

Some more interesting reads https://esp32.com/viewtopic.php?t=2291

https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/coexist.html#setting-coexistence-compile-time-options

@bdraco by coexistence you mean a new configurable option, or just fine-tuned numbers for existing params?

Now have reports that the defaults fix the Wi-Fi stability and active connections.

I still want to do some testing with the coexistence flags but it might be the best interim solution to make the Wi-Fi ones the defaults and use the enhanced values for Ethernet

esphome/issues#2941 (comment)

https://www.reddit.com/r/Esphome/comments/119jy9o/esp32_ble_tracker_prevents_wifi_from_connecting/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

Additional related posts

it might be the best interim solution to make the Wi-Fi ones the defaults and use the enhanced values for Ethernet

Sounds good

@bdraco by coexistence you mean a new configurable option, or just fine-tuned numbers for existing params?

It would likely have to first be a change in the esphome code to add support for the underlying compile flags, and than a change here to enable them.

That would be awesome.