nimble/mesh: We stop sending beacons after provisioning
Open
- Dominant language
- C
- Stars
- 893
- Forks
- 512
- Avg merge
- 13d 31m
- Merged PRs (30d)
- 7
Description
This issue is not verified and needs further investigation.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the mesh behavior before and after provisioning, then trace the beacon-sending path in the NimBLE mesh implementation. The issue names no files or tests, so identify the relevant entry points and add focused coverage once the failure is understood. Done means beacons continue to be sent after provisioning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100