combine light switch and remore mesh don't control light

[Giang]

Hi all,

After I combile light switch example and remote example for my client and server board . Function Remote run fine . But when I push button for send unicast message . 2 board seem dont receiver correct .I define light switch and remote is different elements . I use Mesh SDK v2.0.1 . Show my picture : 

 

Please show me my mistake. Thank very much

[Hung Bui]

Hi Giang, 

 

I agree that we lack good tutorial and documentation about Mesh especially provisioning part. I have a plan to make one. For now please try the python interactive API. By going through the tutorial you will have good understanding about provision and configuration. 

[Giang]

Hi , I have question, in the description above , when I send data from provisioner to Node , it ok . But provisioner not receiver data from Node . I guess is due : I don't config for provisioner subscribe to Node for receiver changes from it . So I find out function : 

config_client_model_subscription_add(uint16_t element_address, nrf_mesh_address_t address, access_model_id_t model_id)

But I dont understand parameter of function . Please explain for me , how config for provisioner subscribe to model of Node . Thank for help

[Hung Bui]

Hi Giang, 

 

Sorry for late response. I was on vacation last week. 

config_client_model_subscription_add() is to be used when you do configuration from the provisioner to the provisionee.

Basically the process is like this: provisioner do provision, assign address, device key, network key to the provisionee. 

After that, if the provisioner has the configuration client and the provisionee has the configuration server, the configuration process happens. In this process, the config client assign the application keys to the provisionee, assign the subscription address, publication address to the provisionee via the config server. 

Please follow the interactive python tutorial.

The function you mentioned is used for the config client to assign subscription address to provisionee. 

This is not needed when you have the light switch client on the provisioner. If it's on the provisioner, you need to do it locally. Have a look here.

 

 

[Giang]

Thank for reply, 

I resume that : In server Node , provisioner will config for server node . Server node subscribe to 1 group (0xC002) . In provisoner , I add 1 client and Set publish address for it is 0xC002 . So , I can use simple_on_off_client_set_unreliable for send data from client on provisoner to server node . But on receiver side of provisoner , I dont know how to set up it , So I execute step 2.

2. I add client 2 on provisioner , and set public address of it is 0x0101. In server node , I set public address is 0x0101 . I think this way they can send data to each other . Is this right ? But I  have not done it yet . I do not understand what is wrong ?

[Hung Bui]

There is nothing call "public address" in mesh, it's publication address I assume you talk about ? (or publish address) Or it's the unicast address ? 

You should use subscription address on your client on your provisioner. 

A node can receive data either by their unicast address or the subscription addresses it subscribed to.  

In our example we made up two group address GROUP_ADDRESS_EVEN and GROUP_ADDRESS_ODD that we assign them as subscription address for the light switch servers and as publication address for the light switch client 3 and 4 (button 3 and 4).

Please read more about Bluetooth Mesh concept here.