mirror of
https://github.com/OpenEPaperLink/OpenEPaperLink.git
synced 2026-03-21 00:04:28 +01:00
[GH-ISSUE #470] why the ESP32 can detect BLE devices but fails to ping them. #3607
Assignees
sascha_hemi
Clear assignees
sascha_hemi
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/OpenEPaperLink#3607
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yangmeng6666 on GitHub (May 25, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/470
I'm seeking assistance to understand why the ESP32 can detect BLE devices but fails to ping them. Any insights or suggestions would be greatly appreciated.
BLE Advertised Device found: Name: , Address: 0c:8c:dc:42:d9:b2, manufacturer data: 9f0002041601, serviceUUID: 61353090-8231-49cc-b57a-886370740041, rssi: -60 Payload data: 02010411074100747063887AB5CC4931829030356107FF9F0002041601 Address type: 00 Manu data: 9092CC3F0600 failed ping BLE Advertised Device found: Name: , Address: f3:d9:2f:2d:34:8a, manufacturer data: 570102ffffffffffffffffffffffffffffffff03f3d92f2d348a, rssi: -87 Payload data: 0201061BFF570102FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF03F3D92F2D348A Address type: 00 Manu data: F405CC3F1A0000001A000000C092CC3FEC92CC3FC8B6803D0000 failed BLE Advertised Device found: Name: , Address: 58:b6:23:78:45:36, manufacturer data: 8f030a1093090034457823b65881, rssi: -73 Payload data: 0201060FFF8F030A1093090034457823B65881 Address type: 00 Manu data: 9092CC3F0E0000008F030A109309 BLE Advertised Device found: Name: DL02V1, Address: 44:df:65:b5:7e:b5, manufacturer data: 8f0310558b3916b57eb565df44, rssi: -82, serviceData: U�9�~�e�D Payload data: 0201060E1695FE10558B3916B57EB565DF440709444C303256310EFF8F0310558B3916B57EB565DF44 Address type: 00 Manu data: 9092CC3F0D0000008F0310558B ping failed pingBLE Advertised Device found: Name: , Address: 5b:7a:4d:73:2b:07, manufacturer data: 4c00021550765cb7d9ea4e2199a4fa879613a4928f9beb94ce, rssi: -76 Payload data: 1AFF4C00021550765CB7D9EA4E2199A4FA879613A4928F9BEB94CE Address type: 01 Manu data: 04FECB3F1900000019000000C092CC3FEC92CC3F58B7803D00 failed pingBLE Advertised Device found: Name: U-ACG3018, Address: 54:08:53:97:30:19, rssi: -95, serviceData: U+ Payload data: 0201060A09552D41434733303138101601FF552B0315000511011A5410A305 failed ping failed ping failed pingBLE Advertised Device found: Name: , Address: 58:ea:1f:f0:d0:6a, rssi: -74 Payload data: 172B0100E29CEF78A5B3C4420000000032E9C65FF9F36044 failed ping failed@yangmeng6666 commented on GitHub (May 25, 2025):
BLE Advertised Device found: Name: , Address: 0c:8c:dc:42:d9:b2, manufacturer data: 9f0002041601, serviceUUID: 61353090-8231-49cc-b57a-886370740041, rssi: -60
Payload data: 02010411074100747063887AB5CC4931829030356107FF9F0002041601
Address type: 00 Manu data: 9092CC3F0600
failed
ping
BLE Advertised Device found: Name: , Address: f3:d9:2f:2d:34:8a, manufacturer data: 570102ffffffffffffffffffffffffffffffff03f3d92f2d348a, rssi: -87
Payload data: 0201061BFF570102FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF03F3D92F2D348A
Address type: 00 Manu data: F405CC3F1A0000001A000000C092CC3FEC92CC3FC8B6803D0000
failed
BLE Advertised Device found: Name: , Address: 58:b6:23:78:45:36, manufacturer data: 8f030a1093090034457823b65881, rssi: -73
Payload data: 0201060FFF8F030A1093090034457823B65881
Address type: 00 Manu data: 9092CC3F0E0000008F030A109309
BLE Advertised Device found: Name: DL02V1, Address: 44:df:65:b5:7e:b5, manufacturer data: 8f0310558b3916b57eb565df44, rssi: -82, serviceData: U�9�~�e�D
Payload data: 0201060E1695FE10558B3916B57EB565DF440709444C303256310EFF8F0310558B3916B57EB565DF44
Address type: 00 Manu data: 9092CC3F0D0000008F0310558B
ping failed
pingBLE Advertised Device found: Name: , Address: 5b:7a:4d:73:2b:07, manufacturer data: 4c00021550765cb7d9ea4e2199a4fa879613a4928f9beb94ce, rssi: -76
Payload data: 1AFF4C00021550765CB7D9EA4E2199A4FA879613A4928F9BEB94CE
Address type: 01 Manu data: 04FECB3F1900000019000000C092CC3FEC92CC3F58B7803D00
failed
pingBLE Advertised Device found: Name: U-ACG3018, Address: 54:08:53:97:30:19, rssi: -95, serviceData: U+
Payload data: 0201060A09552D41434733303138101601FF552B0315000511011A5410A305
failed
ping failed
ping failed
pingBLE Advertised Device found: Name: , Address: 58:ea:1f:f0:d0:6a, rssi: -74
Payload data: 172B0100E29CEF78A5B3C4420000000032E9C65FF9F36044
failed
ping failed
@skiphansen commented on GitHub (May 29, 2025):
What kind of AP are you using?
I don't use BLE tags and know little about BLE tag operation in OEPL, but the message "ping failed" means that the ESP32-s3 can't ping the RF coprocessor.
If you are running a BLE only AP w/o a RF coprocessor (most commonly an ESP32-C6) then the message "ping failed" is expected.
Your best bet for support for BLE tags is the "atc_ble_oepl" channel on the ATC1441 discord server.