fix: change publish period steps and resolution parsing #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an issue with the way the Publish Period step resolution and number of steps were being parsed.
Basically, there was a mistake in the bit numbering, which was causing the publishing period setting to be incorrect.
According to the Bluetooth Mesh specification v1.0.1, the 2 most significant bits represent the step resolution, while the 6 least significant bits represent the number of steps.
I've made the necessary updates to the tests to reflect this change.
How publish period is calculated in nrf sdk for Mesh - Nordic Q&A - Nordic DevZone - Nordic DevZone