You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
Hi team,
when provisioner reset ble mesh node then not all data from persistent store are deleted. At least those data are kept:
bound App key for all models
publication address for all models
I (1660) BLE_MESH(lib): Bluetooth Mesh v1.1 commit: [meshlib:6e23738ff0]
I (1668) BLE_MESH: Friend not supported
I (1732) BLE_MESH: Restored mesh device role: Node
I (1735) BLE_MESH: Restored Model Bound AppKey, index 0000
W (1736) BLE_MESH(lib): Managed flooding policy
I (1737) BLE_MESH: Restored Model Publication, address 0xc000, app_idx 0x000
I (1744) BLE_MESH: Restored Model Bound AppKey, index 0000
I (1749) BLE_MESH: Restored Model Bound AppKey, index 0000
I (1755) BLE_MESH: Restored Model Bound AppKey, index 0000
W (1760) BLE_MESH(lib): Managed flooding policy
I (1764) BLE_MESH: Restored Model Publication, address 0xffff, app_idx 0x000
After re-provisioning those data are restored in new mesh network, but this is most likely undesirable.
Thanks
The text was updated successfully, but these errors were encountered:
Answers checklist.
General issue report
Hi team,
when provisioner reset ble mesh node then not all data from persistent store are deleted. At least those data are kept:
After re-provisioning those data are restored in new mesh network, but this is most likely undesirable.
Thanks
The text was updated successfully, but these errors were encountered: