Unprovisioned Beacons not sent when provisioning failed
Open
- Dominant language
- C
- Stars
- 893
- Forks
- 512
- Avg merge
- 13d 31m
- Merged PRs (30d)
- 7
Description
Nimble does not start sending Unprovisioned Beacons after provisioning failure.
https://pastebin.com/pckSAZDi
APP: BleMESH
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the pastebin report and reproducing the failure with the BleMESH app. Trace the provisioning-failure path through Nimble's BLE Mesh behavior and identify what currently happens to Unprovisioned Beacons; done means they resume sending after provisioning fails, with a regression check for that scenario.
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
- 25/100