Mesh: set Message Destination Address

RE: Mesh: set Message Destination Address

Bjørn Kvaale — Tue, 28 Aug 2018 12:52:57 GMT

beparas Could you please open a new devzone question please.

RE: Mesh: set Message Destination Address

beparas — Tue, 28 Aug 2018 09:33:12 GMT

Hi arunbm123

How do you set "unicast address 50" in button_event_handler() function in client code.

RE: Mesh: set Message Destination Address

Bjørn Kvaale — Fri, 11 May 2018 07:33:03 GMT

How many nodes do you want in your mesh network? If you want three nodes (one provisioner, one client & one server), the server will always get the same unicast address. If you have multiple servers,

In the light switch example, the client sends the messages to the server(s) via button presses. As I mentioned above, you can find the unicast node addresses of the client & server(s) by looking at the provisioning_complete_cb() function inside main.c of the light switch client & server examples. Specifically these two lines in mesh sdk 2.0.0 for example:

    dsm_local_unicast_addresses_get(&node_address);
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Node Address: 0x%04x \n", node_address.address_start);

Then, if you open an rtt viewer window for both the client & server (assuming you are using one provisioner, one client & one server), you get the log printout of the unicast address which the messages get sent to.

If you have more than one server (i.e. one provisioner, one client & many servers), I would advise you to take a look at how the provisioner provisions the client. The client UUID is static & known to the provisioner (see CLIENT_NODE_UUID in light_switch_example_common.h). You could assign one of the servers to also have a static UUID (the server that collects the messages) & have an extra else if() block right before:

else if (m_nw_state.provisioned_devices < SERVER_NODE_COUNT)

where you can provision the first server. Something like else if(m_nw_state.provisioned_devices == 1) {// your code to provision first server}

That way, you will know the unicast address of this server.

After that, you can provision the rest of the servers like shown in the light switch example.

RE: Mesh: set Message Destination Address

priya123 — Wed, 09 May 2018 02:52:27 GMT

Any Updates on this Bjorn Kvaale ?

RE: Mesh: set Message Destination Address

priya123 — Mon, 07 May 2018 12:42:40 GMT

yes Bjorn,

I want only one Node to collect the Messages.Since Provisioner Assigns Address , we dont know what address it assigns to Node which going to collect Messages.

RE: Mesh: set Message Destination Address

Bjørn Kvaale — Mon, 07 May 2018 12:25:22 GMT

By static address, do you mean that every time the node gets provisioned & no matter how many nodes are getting provisioned, that one node will always have the same unicast address(es)?

RE: Mesh: set Message Destination Address

Bjørn Kvaale — Mon, 07 May 2018 12:15:52 GMT

If you are able to open an rtt viewer window for the client & the server nodes, you can see that the unicast node addresses get printed in the provisioning_complete_cb() function in main.c:

    dsm_local_unicast_addresses_get(&node_address);
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Node Address: 0x%04x \n", node_address.address_start);

of the light switch client & server examples in Mesh SDK v2.0.0 for example.

RE: Mesh: set Message Destination Address

priya123 — Sat, 05 May 2018 10:09:39 GMT

is it possible to set Static Address to a Node?

RE: Mesh: set Message Destination Address

arunbm123 — Fri, 04 May 2018 16:31:08 GMT

yes the example s working

RE: Mesh: set Message Destination Address

priya123 — Fri, 04 May 2018 13:50:41 GMT

Yes I tried this Example...Works Fine...

My Question is if I have 100 nodes and I want to send Messages only to 50th Node..is it possible ? Since Provisioner Assigns the unicast address .What address is assigned to 50th Node we dont know....

RE: Mesh: set Message Destination Address

Bjørn Kvaale — Fri, 04 May 2018 12:59:28 GMT

You can use the unicast address to send a message from one node to an element in another node. During provisioning, each element in a node is assigned a unicast address. When you then send a message via the unicast address, only the element with that particular unicast address will read the message.

For example, in the light switch example in the newest mesh sdk v2.0.1, when you test this example with three boards (one provisioner, one client & one server), when you press button 2 on the client board, this refers to case 1 in button_event_handler() function in main.c in the client example. This then calls the simple_on_off_client_set() function, which then sends a message through the send_reliable_message() function.

In the server board, this unicast message gets picked up in the mesh_msg_handle() function inside access.c of the light switch server example. The handle_incoming() function then handles the unicast message to turn the LED on the server board on & off.