MI32 legacy: fix compilation with Bluetooth 5 #22506
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Fix compilation when building with Bluetooth 5 turned on.
The overall performance of BLE 5 on the ESP32 (ESP32-C3 in my last tests) is very underwhelming in my tests and did not improve in the last few months in the context of scanning. The only sensors with software support for BLE 5 that I know are the ones supported by the custom firmware from PVVX. I can clearly see, that I receive data on the Coded PHY (the longe range packets), but this does not gain a single meter in comparison to the same Xiaomi sensor without enabled long range. Both sensors (placed side by side) become invisible in the same distance.
I do not expect further improvements here and for me BLE 5 in the ESP32 family is only a pseudo feature, but I would be more than happy to be proven wrong.
Small addition to the packet parser to suppress unnecessary log messages.
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass