ESP IDF BLE mesh vendor client example persistent memory

[kurtisblow]

Hi,

I tried out the BLE mesh vendor server/client examples and it works fine so far. The problem i encountered is on the client side (provisionier), such that after a restart, the node informations are gone. In the IDF menuconfig, the option "Store BLE Mesh configuration persistently" is activated on both nodes and the vendor server also is in the network after a reboot. Any ideas, why the provisioner does not permanently save all the network informations?

Log:
I (499) BTDM_INIT: BT controller compile version [219866f]
I (499) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (599) phy: phy_version: 4180, cb3948e, Sep 12 2019, 16:39:13, 0, 0
E (959) BLE_MESH: Restored mesh device role: Unknown
I (959) EXAMPLE: ESP_BLE_MESH_PROV_REGISTER_COMP_EVT, err_code 0
I (959) EXAMPLE: ESP_BLE_MESH_PROVISIONER_SET_DEV_UUID_MATCH_COMP_EVT, err_code 0
I (989) EXAMPLE: ESP_BLE_MESH_PROVISIONER_PROV_ENABLE_COMP_EVT, err_code 0
I (999) EXAMPLE: ESP_BLE_MESH_PROVISIONER_ADD_LOCAL_APP_KEY_COMP_EVT, err_code 0
I (999) EXAMPLE: ESP_BLE_MESH_PROVISIONER_BIND_APP_KEY_TO_MODEL_COMP_EVT, err_code 0
I (999) EXAMPLE: ESP BLE Mesh Provisioner initialized
I (4089) BOARD: tap 1 cb (RELEASE)
E (4099) BLE_MESH: ble_mesh_model_send_msg, Invalid destination address 0x0000
E (4099) EXAMPLE: Failed to send vendor message 0xc202e5