BLE Mesh example, address_handle always invalid?

[Mitch996]

Hello, my

m_device_state

is always NOT

DEVICE_STATE_RUNNING, 

so after a little detective work I decided that it's because

provisioner_config_successful_cb();

not properly called, in which

m_device_state

will be set to running status. In other words, my provisioner config isn't successful.

And the reason function

provisioner_config_successful_cb();

isn't called is because:

if(DSM_HANDLE_INVALID != address_handle)

failed. So I traced it back to function:

access_model_publish_address_get(access_model_handle_t handle, dsm_handle_t * p_address_handle)

in which

*p_address_handle = m_model_pool[handle].model_info.publish_address_handle;

and the value of

publish_address_handle

is always 0xFFFF.

Why is that? How do I get a valid publish_address_handle allocated? What should I do?

[Jørgen Holmefjord]

Which example are you using, and what version of the Mesh SDK are you using?

[Mitch996]

Hello, it's the light control example. The version of the SDK is ble_mesh_v0.9.1.

It's not like there is something wrong with the SDK, but rather I don't know if I'm doing things right. The invalid handle COULD BE due to that I'm looking at a not yet allocated property cache slot for a would-be provisionee.