Description
Checklist
- Checked the issue tracker for similar issues to ensure this is not a duplicate.
- Described the feature in detail and justified the reason for the request.
- Provided specific use cases and examples.
Feature description
Hello Community!
I'm developing a project using esp-nimble (namely NimBLE-Arduino) and I'm facing difficulties that I've described in an issue in NimBLE-Arduino.
TDLR: I'm running multiple devices with different physical addresses on the same hardware and bonding information from one mode is being overwritten when bonding to the same host in another mode.
My proposal is to make the NVS prefix that is now hardcoded in nimble_store_nvs,c as #define NIMBLE_NVS_NAMESPACE "nimble_bond" customizable by replacing it with static char[NIMBLE_NVS_STR_NAME_MAX_LEN] nvs_namespace = NIMBLE_NVS_NAMESPACE. I think I can write a PR but first I want to ask the maintainers of this project whether this can be accepted here and ask their opinions on the details of implementation.
Use cases
I'm developing a gamepad that has 2 switchable modes of operation. To work properly with client devices they need to have different addresses and have separate bonding storages.
Alternatives
No response
Additional context
No response