combine light switch and remore mesh don't control light

RE: combine light switch and remore mesh don't control light

Hung Bui — Wed, 21 Nov 2018 15:13:23 GMT

Ok sorry about that. You can find v1.x here.

RE: combine light switch and remore mesh don't control light

turki — Wed, 21 Nov 2018 12:25:55 GMT

if i press on the version of the file i want to download wish is just 2.2.0 available it takes me to a page where there are just the v2.x mesh SDK versions , there is no v1.x

RE: combine light switch and remore mesh don't control light

Hung Bui — Wed, 21 Nov 2018 11:59:28 GMT

Please click on the version of the file you want to download in the download tab, it will open another page that has all the versions.

RE: combine light switch and remore mesh don't control light

turki — Wed, 21 Nov 2018 09:01:05 GMT

hello

how can i download the mesh SDK v1.x to try to understand how to configure manually the client with the provisioner in the same board ???

RE: combine light switch and remore mesh don't control light

Hung Bui — Fri, 25 May 2018 07:43:43 GMT

Hi Giang,

You are doing it incorrectly. config_client_model_subscription_add() is only used when you are a config client and you want to configure a remote node. I already explained this.

Have you really read the case I gave you in earlier answer?

This case. Please follow it. I quoted here:

Basically you need to call dsm_address_subscription_add() to add the group address to the DSM address database. And then call access_model_subscription_add() to assign the server model to listen to that address.

In addition, when you call a function, always check for the return code to make sure there is not any problem with the call. You should not call config_client_model_subscription_add() without any check.

Please study the access_setup() function in the light switch client in SDK v1.0.1. In that example we setup 4 clients locally, assign publication address of the three server to three of the clients. And the last client, we assign the GROUP_ADDRESS (0xCAFE) to the publication address. In your case, you probably want to add the subscription address instead of publication address. Please study that function and let me know which part you don't understand.

How do you plan to send data from the server node to the client node ? I provided you 2 solutions , one is to send via STATUS reply, another is to send as a client (having another element on the server node to work as client)

RE: combine light switch and remore mesh don't control light

Giang — Thu, 24 May 2018 08:31:56 GMT

Hi,

In Provisioner has 2 client , client 1 for group address, client 2 to match to server.

- Provisioner config for serrver :

LOG: Set: on/off server pub addr: 0x00FC

- In side client 2 , I add code :

    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Adding subscription to client\n");
    uint16_t element_address = PROVISIONER_ADDRESS + 2;
    nrf_mesh_address_t address = {NRF_MESH_ADDRESS_TYPE_INVALID, 0, NULL};
    address.type = NRF_MESH_ADDRESS_TYPE_UNICAST;
    address.value = 0x00FC;
    access_model_id_t model_id;
    model_id.company_id = ACCESS_COMPANY_ID_NORDIC;
    model_id.model_id = SIMPLE_ON_OFF_CLIENT_MODEL_ID;
    config_client_model_subscription_add(element_address, address, model_id);

Why client of provisioner still dont receiver messager from server Node ?

I still misunderstand where?

Thank

RE: combine light switch and remore mesh don't control light

Hung Bui — Wed, 23 May 2018 08:45:05 GMT

In the example, the client receive data from the server by the status message reply to the set command of the client (handle_status_cb() with SIMPLE_ON_OFF_OPCODE_STATUS ) , it can also send its status when the client send a simple_on_off_client_get() to get the status.

By design, the command set/get should go from the client to the server, the server reply with its status.

If you want to send data from the server node to the client node, you can implement a client on the server node and a server on the client node as well.

RE: combine light switch and remore mesh don't control light

Giang — Wed, 23 May 2018 08:02:47 GMT

Hi ,

I have 1 provisioner and 1 server .

Provisioner has 2 client , 1 client for group address, 1 client to match to server .

I can send from provisioner to server by 2 way ok (simple_on_off_client_set and simple_on_off_client_set_unreliable) . But I still dont receiver data from server . I follow example light switch client at SDK 1.x . Can you show me the code at this example for the function receiver data from server of client . Thank !!!

RE: combine light switch and remore mesh don't control light

Hung Bui — Tue, 22 May 2018 12:29:23 GMT

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.

RE: combine light switch and remore mesh don't control light

Giang — Tue, 22 May 2018 08:33:03 GMT

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 ?

RE: combine light switch and remore mesh don't control light

Hung Bui — Tue, 22 May 2018 08:01:18 GMT

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.

RE: combine light switch and remore mesh don't control light

Giang — Fri, 11 May 2018 08:52:31 GMT

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

RE: combine light switch and remore mesh don't control light

Hung Bui — Wed, 09 May 2018 15:29:58 GMT

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.

RE: combine light switch and remore mesh don't control light

Giang — Tue, 08 May 2018 08:24:46 GMT

Thank for reply,

After I add light switch client to provisioner , I add some code for set public address for provisioner with Nodes . Provisioner can send data for Node success , But I'm still very vague about configuration part. Why not have a tutorial for this issue ? Can you give a small tutorial on this issue on here . Steps about provisioner add public address with others node. Thank very much !!!

RE: combine light switch and remore mesh don't control light

Hung Bui — Mon, 07 May 2018 14:55:09 GMT

1. As I mentioned, if you add the light switch client to the provisioner, you need to configure the model, add applicationkey, publication address.

2. If you add the remote provisioner client into the light switch client, you still need to configure your light switch client.

What do you mean exactly by "gateway" ? In BLE Mesh there isn't a well defined name for gateway.

In SDK v1.x we combine the provisioner and the light switch into one device, but different elements. The provisioning and configuration of the clients on the device is done manually and locally. It's not standard to do so. The client doesn't have to be on the same device as the provisioner. And in most case it won't.

Why exactly do you want to combine the light switch to the light blub ?

Can you use an extra device to work as provisioner and can do remote provisioning. But be aware even you do so, you still need to do configuration from the provisioner.

Of course, there is nothing wrong to combine the provisioner to the light switch client, for example you can sell a package of 1 or multiple light blub and one light switch. And the light switch should be able to do provisioning and setup the network. If you want to do that, you follow what we do in SDK v1.x

RE: combine light switch and remore mesh don't control light

Giang — Fri, 04 May 2018 09:20:57 GMT

I am confused between two directions:

1. Use provisioner is gateway . So , it had provision part and configuration part. And I have to add remote client part and simple on/off client for send data to Nodes (simple on/off server + remote server) . And I have a question : When I add simple on/off client to provisioner , I have to add public address for it match with Nodes . It correct?

2. Use light switch client is gateway. So , I have to add remote client and configuration part for send data to Nodes (light switch server + remote server) . And about configuration part, I realize that provisioner example (v2.1) and light switch client (v1.x) had it . And I wondered which one was right . I am trying add configuration part of provisioner example to (light switch client + remote client) , and want it is gateway . I have the following error :

Any suggest for it ?

Sorry for the inconvenience ! Thank!

RE: combine light switch and remore mesh don't control light

Hung Bui — Fri, 04 May 2018 08:18:11 GMT

If you plan to use a provisioner to provision+configuration your client, then it's fine to use that provisioner.

If you want to integrate provisioner on the light switch client, you need to do configuration locally on the light switch client, and you need to follow what we did in SDK v1.x. Have you read the case I referred to in my first reply 2 days ago ?

RE: combine light switch and remore mesh don't control light

Giang — Fri, 04 May 2018 02:56:59 GMT

Hi,

Follow me, provisioner example v2.1 had provision and configuration . And can I use configuration part of it for add to light swight client example ? Or I have to use configuration part of switch light client example v1.x for this ? Thank

RE: combine light switch and remore mesh don't control light

Hung Bui — Thu, 03 May 2018 13:37:37 GMT

There are 2 separated procedures, one is provisioning and second is configuration. Have a look here.

The remote provisioner only do the provisioning part. You need a configuration client to do the configuration part. This is handled by node_setup.c and provisioner_helper.c

If you simply combine the light switch example and the remote provisioning example, you won't be able to configure the server. In addition, the light switch client need to be configured as well.

Configuration is the process of exchanging&binding the application key and assigning publication/subscription address. That what you need to do. Without configuration, your nodes won't function.

To understand the process of provisioning and configuration, I strongly suggest you to try playing with the interactive python script we have. The instruction is here.

RE: combine light switch and remore mesh don't control light

Giang — Thu, 03 May 2018 08:46:27 GMT

Hi ,

After I using light switch client provisioning for light switch server . I only need use access_model_publish_address_set for Set publish address for the client to the corresponding server . We can send data to each other . It correct ?

RE: combine light switch and remore mesh don't control light

Giang — Thu, 03 May 2018 02:27:17 GMT

Exactly what I do is :

1. Add provision remote client to light switch client.

2. Add provision remote server to light switch server.

I want client is gateway and servers is node , can remote and send data.

But, I'm confused between choosing provisioner example is gateway. Can you give me 1 correct model of mesh network ?

And I have a question:

1. When I use provisioner example + (light switch client + remote server - Node1) + (light switch server + remote server - Node 2) . Provisioner is provisioning and config for 2 node correct . But don't send data control light . If I delete code

 /* TODO: This should be handled by the configuration server model. */
    mesh_key_index_t net_key_index;
    uint32_t count = 1;
    ERROR_CHECK(dsm_subnet_get_all(&net_key_index, &count));
    m_netkey_handle = dsm_net_key_index_to_subnet_handle(net_key_index);

    uint8_t appkey[NRF_MESH_KEY_SIZE] = {0};
    ERROR_CHECK(dsm_appkey_add(0, m_netkey_handle, appkey, &m_appkey_handle));
    ERROR_CHECK(dsm_address_publish_add(PROVISIONER_ADDRESS, &m_provisioner_address_handle));
    ERROR_CHECK(access_model_application_bind(m_remote_server.model_handle, m_appkey_handle));
    ERROR_CHECK(access_model_publish_address_set(m_remote_server.model_handle, m_provisioner_address_handle));
    ERROR_CHECK(access_model_publish_application_set(m_remote_server.model_handle, m_appkey_handle));
    ERROR_CHECK(access_model_publish_ttl_set(m_remote_server.model_handle, 6));
    ERROR_CHECK(pb_remote_server_enable(&m_remote_server));
    ERROR_CHECK(pb_remote_server_prov_bearer_set(&m_remote_server, nrf_mesh_prov_bearer_adv_interface_get(&m_prov_bearer_adv)));

in each Node . It send data control light correct . But remote function of each Node don't run if I use remote client example for provisioning .

How I can use both remote function and control light function ?

Can you explain for me the meaning of the above code?

2. Can I use provisioner example for config Node ?

Thank very much !

RE: combine light switch and remore mesh don't control light

Hung Bui — Wed, 02 May 2018 12:36:18 GMT

Hi Giang,

Remote you mean remote provisioning client or server ?

I assume it's server.

If you have a look into the code (button_event_handler() ) you can find that "Ignored. Node is not configured.\n" thrown when the light switch client is not configured.

You need to configure the client locally, in this case setting the publication address. It's similar to this case. Have a look at Mesh SDK v1.x to see how it works.

RE: combine light switch and remore mesh don't control light

Giang — Wed, 02 May 2018 07:27:59 GMT

Any suggestion ?