bt_mesh_cfg_cli_mod_app_bind_vnd fails with status 0x1 or 0x3

[AndyM]

Hello 
I am trying to provision a device over the air

Provisioning succeeds 

But when I try to bind the app key it fails with status 1. I also saw status 3 

Here are the commands I used

mesh init

mesh cdb show
Mesh Network Information
========================
Address Elements Flags UUID DevKey
0x00c8 1 - 670e3c752a7e46c78000000000000000 aafa70e245e8f7718a4ec7a8e6c75dcf
> Total nodes: 1
---
NetIdx NetKey
0x000 2870a43ade4745d5f471ce29e6ffc0f2
> Total subnets: 1
---
NetIdx AppIdx AppKey
0x000 0x000 522975c06bcadcbbf4a402df2f895226
> Total app-keys: 1

mesh models cfg model app-bind 200 0 4098 2570
Model App Bind failed with status 0x01

The code in cfg.c calls bt_mesh_cfg_cli_mod_app_bind_vnd  which fails with status 0

 What does status 0 mean?

What do I need to fix this?

Thank  you

Andy

[Hieu]

Hi Andy,

It's been a while. Yes, I figure there is a typo with the later "status 0" part and have been looking into why it could be status 0x01 or 0x03.

It turns out that I will need some further internal help with your question. I will get back to you within next week with an update, or as soon as I get some help.

Hieu

[AndyM]

Thank you

More info

If the provisioner is not rebooted  after successful provisioning a node, bt_mesh_cfg_cli_mod_app_bind_vnd fails with status 0x3

If it is rebooted it fails with status 0x1

[Hieu]

Hi Andy,

The status codes are defined in Section 4.3.5 of the Mesh Profile Specification v1.0.1. 0x01 is Invalid Address, and 0x03 is Invalid AppKey Index.

AndyM said:

If the provisioner is not rebooted  after successful provisioning a node, bt_mesh_cfg_cli_mod_app_bind_vnd fails with status 0x3

If it is rebooted it fails with status 0x1

Does this happen consistently?

With the status code's meaning known, could you review your steps to see if some addresses are incorrect, or if the key has been bound before being used? Incorrect address, for example, is easy to encounter if a node has multiple elements, with each has its own unicast address.

If you still have difficulties, could you please give me a full log and more details?

[AndyM]

The problem was that I did not have the destination address set 

After this command

mesh target dst <address of node being provisioned>

I was able to provision, bind the models and configure publication parameters over the air

Thank you

Andy

[Hieu]

Thanks for letting us know the root cause. Feel free to close the thread at your convenience then