RE: Provisioning problem with Mesh SDK 2.0

ajay — Fri, 17 Aug 2018 09:26:17 GMT

I am doing the similar project

- 1 board is used for the Client & provisioner:

- 1 board is used for Server side.

Seems the device is provisioned, and the node is already configured.

But afterwards, when i send the simple on off message to the server side, it say Publication not configured for client

 0> <t:         24>, main.c,  932, ----- BLE Mesh Light Switch Mesh Demo -----
 0> <t:        520>, main.c,  861, Initializing and adding models
 0> <t:        526>, main.c,  880, Initializing and adding models finish
 0> <t:        537>, main.c,  911, Setup defaults: Adding keys, addresses, and bindings 
 0> <t:        701>, provisioner_helper.c,  378, netkey_handle: 0
 0> <t:       6030>, main.c, 1426, Device UUID : 0059ABCDEFABCDEFACCDEFABCDEFABCD
 0> <t:       6035>, main.c,  481, Waiting for Server node to be provisioned ...
 0> <t:     995699>, provisioner_helper.c,  303, Static authentication data provided
 0> <t:    1205425>, provisioner_helper.c,  212, Provisioning completed received
 0> <t:    1205430>, provisioner_helper.c,  217, Adding device address, and device keys
 0> <t:    1205436>, provisioner_helper.c,  227, Going to address [0x0100]key_handle [0], dev_key[536886660]
 0> <t:    1205443>, access.c, 1101, #### public address handle 0, set to access_model_pool index 2
 0> <t:    1205448>, config_client.c,  438, >>>>>>>>>>>>>>>>>>>>>>>:0x02 Addr:0x00
 0> <t:    1205454>, provisioner_helper.c,  263, <t:    1209434>, provisioner_helper.c,  175, Local provisioning link closed: prov_state: 2  remaining retries: 2
 0> <t:    1209440>, main.c,  773, Provisioning successful
 0> <t:    1209445>, provisioner_helper.c,  201, Provisioning complete. Node addr: 0x0100 elements: 1
 0> <t:    1209450>, node_setup.c,  699, Configuring Node: 0x0100
 0> <t:    1209455>, config_client.c,  438, >>>>>>>>>>>>>>>>>>>>>>>:0x02 Addr:0x00
 0> <t:    1209461>, node_setup.c,  329, Setup select Step for addr 0x0100
 0> Getting composition data
 0> <t:    1285449>, main.c,  201, Config client event
 0> <t:    1285454>, node_setup.c,  393, Adding appkey
 0> <t:    1285474>, access_reliable.c,  413, access_model_publish statu 0
 0> <t:    1329861>, main.c,  201, Config client event
 0> <t:    1329865>, node_setup.c,  404, App key bind: Health server
 0> <t:    1329877>, access_reliable.c,  413, access_model_publish statu 0
 0> <t:    1332259>, main.c,  201, Config client event
 0> <t:    1332263>, node_setup.c,  419, App key bind: Simple On/Off server
 0> <t:    1332277>, access_reliable.c,  413, access_model_publish statu 0
 0> <t:    1335080>, main.c,  201, Config client event
 0> <t:    1335084>, node_setup.c,  472, Setting publication address for the health server to 0x0001
 0> <t:    1335103>, access_reliable.c,  413, access_model_publish statu 0
 0> <t:    1382356>, main.c,  201, Config client event
 0> <t:    1382361>, node_setup.c,  499, Set: on/off server pub addr: 0x0100
 0> <t:    1382366>, access_reliable.c,  413, access_model_publish statu 4
 0> <t:    1397084>, main.c,  201, Config client event
 0> <t:    1397089>, node_setup.c,  510, Adding subscription
 0> <t:    1397102>, access_reliable.c,  413, access_model_publish statu 0
 0> <t:    1398643>, main.c,  201, Config client event
 0> <t:    1398647>, main.c,  729, Configuration of device 0 successful
 0> <t:    1398652>, main.c,  742, Finish Init the Simple Onff 0 model handle 4
 0> <t:    1398658>, provisioner_helper.c,  331, Scanning For Unprovisioned Devices
 0> <t:    1398716>, main.c,  597, Flash write complete
 0> <t:    1398720>, main.c,  608, Flash write complete exit
 0> <t:    1584330>, main.c,  332, Button 0 pressed
 0> <t:    1584334>, access.c,  351,  I am here 
 0> <t:    1584338>, access.c,  352,  App key Handle 0xFFFF
 0> <t:    1584342>, access.c,  353,  publish_address_handle key Handle 0xFFFF
 0> <t:    1584346>, access.c,  354,  Is valid opcode 1??
 0> <t:    1584350>, access.c,  374, packet tx return here. . at the handle 4
 0> <t:    1584355>, access_reliable.c,  413, access_model_publish statu 7
 0> <t:    1584359>, access_reliable.c,  442, access_model_reliable_publish failed 7
 0> <t:    1680696>, main.c,  332, Button 0 pressed
 0> <t:    1680700>, access.c,  351,  I am here 
 0> <t:    1680704>, access.c,  352,  App key Handle 0xFFFF
 0> <t:    1680708>, access.c,  353,  publish_address_handle key Handle 0xFFFF
 0> <t:    1680712>, access.c,  354,  Is valid opcode 1??
 0> <t:    1680716>, access.c,  374, packet tx return here. . at the handle 4
 0> <t:    1680721>, access_reliable.c,  413, access_model_publish statu 7
 0> <t:    1680727>, access_reliable.c,  442, access_model_reliable_publish failed 7
 0> <t:    1707525>, main.c,  332, Button 0 pressed
 0> <t:    1707529>, access.c,  351,  I am here 
 0> <t:    1707532>, access.c,  352,  App key Handle 0xFFFF
 0> <t:    1707536>, access.c,  353,  publish_address_handle key Handle 0xFFFF
 0> <t:    1707540>, access.c,  354,  Is valid opcode 1??
 0> <t:    1707544>, access.c,  374, packet tx return here. . at the handle 4
 0> <t:    1707549>, access_reliable.c,  413, access_model_publish statu 7
 0> <t:    1707553>, access_reliable.c,  442, access_model_reliable_publish failed 7
 0> <t:    1710307>, main.c,  801, Node 0x0100 alive with 0 active fault(s), RSSI: -67

Can you teach me your setting on the mp_config_step in the setup_select_steps? I think i am not correctly config all the necessary appkey??

RE: Provisioning problem with Mesh SDK 2.0

Igor — Mon, 21 May 2018 15:41:37 GMT

Yeah. main.c used its own instance of configured_devices variable. Problem solved.

RE: Provisioning problem with Mesh SDK 2.0

Bjørn Kvaale — Fri, 18 May 2018 10:57:18 GMT

I have taken a look at the log & it seems the simple messaging model has been added correctly. Does the configured devices variable (m_nw_state.configured_devices++;) get updated for you in the app_config_successful_cb() inside main.c for your provisioner/client, like it does in the mesh sdk v2.0.0 provisioner example?

RE: Provisioning problem with Mesh SDK 2.0

Igor — Wed, 16 May 2018 14:54:03 GMT

Everything (including simple_message model) was working on Mesh 1.0. But I am not so lucky with the Mesh 2.0 (a lot of corrections had to be done due to extensive changes made in the new Mesh SDK).

RE: Provisioning problem with Mesh SDK 2.0

Bjørn Kvaale — Wed, 16 May 2018 14:39:19 GMT

Sorry about that. Should have noticed that. Have you merged the light switch provisioner & client examples then? Were you able to merge those examples & get everything working correctly with the simple on/off model first before you moved to the simple_message model?

RE: Provisioning problem with Mesh SDK 2.0

Igor — Wed, 16 May 2018 12:55:13 GMT

Bjørn Kvaale The "client" is also a provisioner. You can see its log in my post. I would like to say that I was able to make this working with Mesh 1.0 SDK but I am unsuccessful with the Mesh 2.0 SDK.

RE: Provisioning problem with Mesh SDK 2.0

Bjørn Kvaale — Wed, 16 May 2018 12:46:11 GMT

Could you upload the logging from the provisioner too please? That could give us a bit more information about why the server has not been provisioned correctly, even though it seems like most of the logging looks to be correct. Quite a few customers have had some issues with the devzone answer I posted in the link you mention, so I will need to take a look & see what I have done wrong. I suspect it might be something with the simple message model. Are you using one provisioner, one client & one server in your test?