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

docs: bluetooth: mesh: Add note about storing runtime configuration #58907

Conversation

PavelVPV
Copy link
Collaborator

@PavelVPV PavelVPV commented Jun 6, 2023

All public API declared in cfg.h won't schedule storing of the change persistently if BT_MESH_VALID flag is not set. The flag is set after the node is provisioned.

Thalley
Thalley previously approved these changes Jun 6, 2023
Andrewpini
Andrewpini previously approved these changes Jun 8, 2023
Comment on lines 18 to 19
Any changes done to the runtime configuration before the node is provisioned
will not be stored in the :ref:`persistent storage <bluetooth_mesh_persistent_storage>`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Any changes done to the runtime configuration before the node is provisioned
will not be stored in the :ref:`persistent storage <bluetooth_mesh_persistent_storage>`.
Runtime configuration changes before the node is provisioned will not be stored
in the :ref:`persistent storage <bluetooth_mesh_persistent_storage>`.

All public API declared in cfg.h won't schedule storing of the change
persistently if BT_MESH_VALID flag is not set. The flag is set after the
node is provisioned.

Signed-off-by: Pavel Vasilyev <[email protected]>
@carlescufi carlescufi merged commit 5572a27 into zephyrproject-rtos:main Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants