Simple ON Off Client, public address on Mesh 2.0

RE: Simple ON Off Client, public address on Mesh 2.0

Bjørn Kvaale — Tue, 21 Aug 2018 11:25:57 GMT

Hi ajay,

It seems from your logging information that you have done the provisioning & configuration steps correctly. It also seems that the appkey was bound correctly to the light switch server example. Was the appkey bound to the client though? Have you done the provisioning & configuration of the client?

We have some provisioning & configuration documenatation available on our Infocenter.

Also, I would recommend running the regular stock light switch example from one of the newest mesh sdks (>= v2.0.1). Then, you can run the provisioner, client & server examples in debug mode & get debugging RTT logging information directly via Segger Embedded Studio. You can then copy & paste this logging information in a text document & use that as a reference solution to compare with your own logging information.

RE: Simple ON Off Client, public address on Mesh 2.0

ajay — Mon, 20 Aug 2018 02:09:49 GMT

Yes, i have read the migration guide in the In Infocenter?

I think my bluetooth mesh stack and the provision process is done correctly (I can read from my Board #2, it said it is correctly provisioned.)

The problem is, seems i did not make the configuration of the node properly. That's why i am asking a if there is reference config_steps.

As, now i am doing the same in Mesh v1.0, the Board #1 will be the provisioner , also the on/off client. And Board #2 is the on/off server.

Now, sees it said it did not have the publication state set for the board #1

RE: Simple ON Off Client, public address on Mesh 2.0

Bjørn Kvaale — Fri, 17 Aug 2018 11:47:34 GMT

Hi ajay,

Have you taken a look at the migration guide on our Infocenter?

Kind Regards,

Bjørn

RE: Simple ON Off Client, public address on Mesh 2.0

ajay — Thu, 16 Aug 2018 10:28:34 GMT

If i use the server1_server2_config_steps, it give the log as above

RE: Simple ON Off Client, public address on Mesh 2.0

ajay — Thu, 16 Aug 2018 10:27:30 GMT

 0> <t:24>, main.c, 932, ----- BLE Mesh Light Switch Mesh Demo -----
 0> <t:518>, main.c, 861, Initializing and adding models
 0> <t:524>, main.c, 880, Initializing and adding models finish
 0> <t:535>, main.c, 911, Setup defaults: Adding keys, addresses, and bindings
 0> <t:703>, provisioner_helper.c, 376, netkey_handle: 0
 0> <t:6031>, main.c, 1426, Device UUID : 0059ABCDEFABCDEFACCDEFABCDEFABCD
 0> <t:6035>, main.c, 481, Waiting for Server node to be provisioned ...
 0> <t:25>, main.c, 932, ----- BLE Mesh Light Switch Mesh Demo -----
 0> <t:518>, main.c, 861, Initializing and adding models
 0> <t:524>, main.c, 880, Initializing and adding models finish
 0> <t:559>, main.c, 853, Restored: App data
 0> <t:563>, main.c, 920, Restored: Handles
 0> <t:568>, provisioner_helper.c, 348, m_netkey_handle:0 m_appkey_handle:0 m_self_devkey_handle:1
 0> <t:998>, main.c, 1426, Device UUID : 0059ABCDEFABCDEFACCDEFABCDEFABCD
 0> <t:1004>, main.c, 481, Waiting for Server node to be provisioned ...
 0> <t: 6270>, provisioner_helper.c, 329, Scanning For Unprovisioned Devices
 0> <info> app: Debug logging for UART over RTT started.
 0> <t:350217>, provisioner_helper.c, 157, UUID seen: 0059FFFF00000000A117145116817393
 0> <t:350222>, provisioner_helper.c, 96, UUID filter matched
 0> <t:519188>, provisioner_helper.c, 166, Start Provision with : 0059FFFF00000000A117145116817393
 0> <t:519194>, provisioner_helper.c, 115, key data index 0
 0> <t:519198>, provisioner_helper.c, 116, key address 0x100
 0> <t:519203>, provisioner_helper.c,117, key type 1
 0> <t:519208>, nrf_mesh_prov.c, 219, nrf_mesh_prov_provision exit with status 0
 0> <t:520641>, provisioner_helper.c, 306, Provisioning link established
 0> <t:601086>, provisioner_helper.c, 301, Static authentication data provided
 0> <t:679059>, provisioner_helper.c, 210, Provisioning completed received
 0> <t:679064>, provisioner_helper.c, 215, Adding device address, and device keys
 0> <t:679069>, provisioner_helper.c, 225, Going to address [0x0100]key_handle [0], dev_key[536886660]
 0> <t:679078>, access.c, 1092, #### public address handle 0, set to access_model_pool index 2
 0> <t:679083>, config_client.c, 438, >>>>>>>>>>>>>>>>>>>>>>>:0x02 Addr:0x00
 0> <t:679088>, provisioner_helper.c, 261, <t: 682720>, provisioner_helper.c, 173, Local provisioning link closed: prov_state: 2  remaining retries: 2
 0> <t:682726>, main.c, 773, Provisioning successful
 0> <t:682731>, provisioner_helper.c, 199, Provisioning complete. Node addr: 0x0100 elements: 1
 0> <t:682736>, node_setup.c, 679, Configuring Node: 0x0100
 0> <t:682741>, config_client.c, 438, >>>>>>>>>>>>>>>>>>>>>>>:0x02 Addr:0x00
 0> <t:682747>, node_setup.c, 369, Getting composition data
 0> <t:682815>, main.c, 597, <t: 752461>, main.c, 201, Config client event<t: 752466>, node_setup.c,  379, Adding appkey
 0> <t:755406>, main.c, 201, Config client event<t: 755410>, node_setup.c, 272, opcode status field: 0
 0> <t:755415>, node_setup.c, 390, App key bind: Health server
 0> <t:765600>, main.c, 201, Config client event<t: 765604>, node_setup.c, 272, opcode status field: 0
 0> <t:765608>, node_setup.c, 405, App key bind: Simple On/Off server
 0> <t:776555>, main.c, 201, Config client event<t: 776559>, node_setup.c, 272, opcode status field: 0
 0> <t:776563>, node_setup.c, 458, Setting publication address for the health server to 0x0001
 0> <t:781004>, main.c, 201, Config client event<t: 781009>, node_setup.c, 272, opcode status field: 0
 0> <t: 781013>, node_setup.c, 484, Set: on/off server pub addr: 0x00FC
 0> <t: 805714>, main.c, 201, Config client event<t: 805721>, node_setup.c, 272, opcode status field: 0
 0> <t: 805726>, node_setup.c, 495, Adding subscription
 0> <t: 815328>, main.c, 201, Config client event<t: 815332>, node_setup.c, 272, opcode status field: 0
 0> <t: 815337>, main.c, 729, Configuration of device 0 successful

RE: Simple ON Off Client, public address on Mesh 2.0

ajay — Thu, 16 Aug 2018 10:26:54 GMT

I am using the server_config_steps for config and provision the device in the function of setup_select_steps