Open kapet opened 1 year ago
Some more experiments this weekend:
esp32_ble_tracker:
scan_parameters:
interval: 100ms
window: 99ms
active: True
Maybe it's the other BLE devices in the vicinity, maybe it is something about this device, I don't know. But with the default scan_parameters
it is not being found.
The problem
I'm trying to use a BLE device (it's a Radoneye), to no avail. I have tracked this down to be a fundamental BLE issue: My phone (using 'nRF Connect') can see the device just fine when scanning, but the ESP32 next to the device reports on various other BLE devices in the vicinity, except for this one.
So the ESP32 BLE feature works in principle, also the Radoneye does send out advertisements. But for whatever reason the ESP32 does not see or report on it.
(The Radoneye sensor is not enabled right now, this is a problem with the Bluetooth/BLE stack and not the Radoneye sensor.)
Which version of ESPHome has the issue?
2022.12.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2023.1.6
What platform are you using?
ESP32
Board
az-delivery-devkit-v4
Component causing the issue
esp32_ble_tracker
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
according to nRF Connect, the Radoneye device advertises about every 65ms; raw advertising data as seen by my phone: 0x130946523A5232303A534E30323931202020202003190000020106020AF403032315110723D1BCEA5F782315DEEF121223150000
screenshot from parsed advertising data on phone: