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

esp_conn_mgr does not advertise service uuid when include_service_uuid is set (AEGHB-665) #363

Open
3 tasks done
AlejandroHuerta opened this issue May 25, 2024 · 0 comments

Comments

@AlejandroHuerta
Copy link

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

5.2.1

Espressif SoC revision.

esp32-c3 (QFN32) v0.4

Operating System used.

Windows

How did you build your project?

VS Code IDE

If you are using Windows, please specify command line type.

None

Development Kit.

esp32-c3-devkitm-1

Steps to reproduce.

  1. Build spp_server example
  2. Make sure to set include_service_uuid = true in the esp_ble_conn_config_t config. (It looks like it's set to true by default)
  3. Flash device
  4. Use external bluetooth tool to observe advertisement data
  5. Notice that no service uuid is advertised.

Build Logs.

No response

More Information.

Looking at the source of esp_nimble.c it looks like that property is never used. Might be a case of this functionality not being added yet. I'm still trying to figure out a work around for the time being.

@github-actions github-actions bot changed the title esp_conn_mgr does not advertise service uuid when include_service_uuid is set esp_conn_mgr does not advertise service uuid when include_service_uuid is set (AEGHB-665) May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants