Choosing the right interval: and window: values

[Nickduino]

Yes, I read the doc but I'm afraid I'm left with more questions than answers

If 211 ms are suggested, then why does the code snippet show 320 ms?
If 120 ms are suggested, then why does the code snippet show 300 ms?

But more broadly, how do you choose which interval: and window: values to test, given you have to recompile every time? How do you know a setting is better than another (I mean, what are you looking for in the Bermuda integration? What entity tells you )?

More specifically, I'm trying to run Bermuda with the Bluetooth proxy of an Everything Presence Light (for people who don't know it: it's an ESP-WROOM-32 with an LD2450 mmWave sensor and Lux sensor) sensor...which is doing a lot more work than looking for iBeacons, so I can't go for a 60% or 94% duty cycle. Have you guys experimented with it already? If not, what process would you suggest? Test random value and keep an eye on the heap?

[agittins]

Howdy!

Good point - the "suggested" comment there was a note I'd made when first experimenting, I don't recall who suggested it! I've removed those commented values in the doc so it just has the defaults in the comment and my suggested values of 320 and 300.

so I can't go for a 60% or 94% duty cycle.

That's not really what's going on, there are two cpu's on the wroom-32, and there are async elements to the scanning so it isn't a system-wide duty cycle allocation. I'd just use my recommended values (yes, for the great Everything Presence devices too), as those settings seem to be quite reliable, and only consider changing them (by reducing the 300 value) if you experience stability issues.

Plenty of folks are using the EP devices, and I don't recall anyone having trouble with the scan/window timings on them - for that matter, this setting only seems to have caused any issues on older ESPHome versions, and the versions over the past 6 months or more seem to be pretty solid regardless of the timing, I think because of improvements to the BT/WiFi co-existence features.

But more broadly, how do you choose which interval: and window: values to test, given you have to recompile every time? How do you know a setting is better than another (I mean, what are you looking for in the Bermuda integration? What entity tells you )?

Symptoms are the proxy stops sending scan results, drops off the wifi or locks up. I choose 320ms for the interval because it is statistically a good bet for catching at least one advert for most devices on most iterations. I chose 300ms for the window because it seems to work for everything (esp-c3 on older esphome excluded) and is a good balance of conservative while also ensuring a good chance of hearing most adverts.

[Nickduino]

Thanks for the clarification on the suggested values. I'll try them tomorrow.

Plenty of folks are using the EP devices, and I don't recall anyone having trouble with the scan/window timings on them - for that matter,

But are they using your suggested settings (which requires adopting the device, cloning the repo, changing the BLE yaml, (in my case) changing the way the !includes are done, etc.) or the default ones (so 30/320)?