Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advertise my own service uuid in advertising data during Bluetooth Mesh / BLE coexistence (IDFGH-14535) #15297

Open
lebrislo opened this issue Jan 29, 2025 · 0 comments
Assignees
Labels
Status: Opened Issue is new Type: Feature Request Feature request for IDF

Comments

@lebrislo
Copy link

Is your feature request related to a problem?

Hi,

Here's my problem explained : #15217

Describe the solution you'd like.

I would be a benefit to be allowed to add my own ble service uuid along with the current mesh proxy service (0x1828) in the BLE advertising data.

The expected behavior is exactly what's happening when advertising with BLE only with esp_ble_adv_data_t. It would be great to add my services uuid inside esp_ble_mesh_ble_adv_param_t.

Describe alternatives you've considered.

No response

Additional context.

No response

@lebrislo lebrislo added the Type: Feature Request Feature request for IDF label Jan 29, 2025
@lebrislo lebrislo changed the title Advertise my own service uuid during Bluetooth Mesh / BLE coexistence Advertise my own service uuid in advertising data during Bluetooth Mesh / BLE coexistence Jan 29, 2025
@github-actions github-actions bot changed the title Advertise my own service uuid in advertising data during Bluetooth Mesh / BLE coexistence Advertise my own service uuid in advertising data during Bluetooth Mesh / BLE coexistence (IDFGH-14535) Jan 29, 2025
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new Type: Feature Request Feature request for IDF
Projects
None yet
Development

No branches or pull requests

3 participants