Subscribe a group address for the Mesh Message

RE: Subscribe a group address for the Mesh Message

Anthony1055 — Sat, 15 Sep 2018 10:05:00 GMT

Hi Renato, I hope you can help, I'm trying to get my servers to send messages using the broadcast address. How did you do it?

RE: Subscribe a group address for the Mesh Message

Paulo.Zacarias — Mon, 25 Jun 2018 12:05:04 GMT

Hi Hung,

I'm trying to implement your solution in Mesh 1.0.1, but it is crashing at:

ERROR_CHECK(dsm_address_publish_add(GROUP_ADDRESS_CUSTOM, &m_group_handle2));

With error code 4 ("No Memory for operation"?).

What could it be?

My experiment is to have 2 groups, one for 2 of the servers and another for all 3 servers.

So far I modified the do_config_step() in provisioner.c to assign to different groups (as a first step), like:

            if ( m_target_address % 0x02)
            {
                address.value  = GROUP_ADDRESS_CUSTOM;
            }
            else
            {
                address.value  = GROUP_ADDRESS;
            }

This is ok, as I'm able to talk with the nodes that subscribed to GROUP_ADDRESS.

Now I want one of the clients to speak with the node that was assigned to GROUP_ADDRESS_CUSTOM, but it's failing as described above...

RE: Subscribe a group address for the Mesh Message

Hung Bui — Mon, 23 Apr 2018 09:02:58 GMT

Have you tried what I suggested in the first answer of calling dsm_address_subscription_add() and then call access_model_subscription_add() to add the address to the client subscription list ?

It's the same for server and client if you want to configure something locally.

RE: Subscribe a group address for the Mesh Message

Renato Silva — Tue, 17 Apr 2018 14:45:55 GMT

Hi,

I am working in light switch example and (with my modification) the servers are sending a message using the broadcast address 0xCAFE, and in this format all server received the messages. This feature works fine!

This way, the client side also received the messages, but for some reason this message is not trated.

This my question! I know that address_nonvirtual_subscription_exists has a list that has the devices able to receive the message.

My doubt is: How I can to insert the client in this list, for the client device to trate the broadcast message sends from any server.

What I wanna do now is subscribe the client to receive broadcast messages since in light switch example only server side receive the broadcast messages, the client side dont..

How I told above, I already send broadcast messages from server to server (trought 0xCAFE address), but the client dont receive these messages because it is not subscribed.

I need to modify the light switch example to init the client side able to receive broadcast messages.

Can anyone help me in this question?

RE: Subscribe a group address for the Mesh Message

Hung Bui — Wed, 31 Jan 2018 09:11:33 GMT

We currently don't use virtual address in our example. You can read more about virtual address at section 2.3.5 in Mesh spec v1.0 .

DSM_NONVIRTUAL_ADDR_MAX is what you should be concerned when adding address to the DSM (if you don't plan to use virtual address ).

RE: Subscribe a group address for the Mesh Message

ajay — Wed, 31 Jan 2018 03:04:10 GMT

Should we also need to consider to take care the follows in nrf_mesh_config_app.h, while GROUP_COUNT is added for the number of Group that i can support in the Network?

/**
 * @defgroup DSM_CONFIG Device State Manager configuration
 * Sizes for the internal storage of the Device State Manager.
 * @{
 */
/** Maximum number of subnetworks. */
#define DSM_SUBNET_MAX                                  (1)
/** Maximum number of applications */
#define DSM_APP_MAX                                     (1)
/** Maximum number of device keys */
#define DSM_DEVICE_MAX                                  (SERVER_COUNT)
/** Maximum number of virtual addresses. */
#define DSM_VIRTUAL_ADDR_MAX                            (GROUP_COUNT)
/** Maximum number of non-virtual addresses. One for each of the servers and a group address. */
#define DSM_NONVIRTUAL_ADDR_MAX                         (SERVER_COUNT + GROUP_COUNT)
/** Number of flash pages reserved for the DSM storage */
#define DSM_FLASH_PAGE_COUNT                            (1)

Where can i found more about the info of Virtual Vs non-virtual?

RE: Subscribe a group address for the Mesh Message

Hung Bui — Tue, 30 Jan 2018 11:33:43 GMT

I wouldn't suggest to use 2 clients to talk to 2 groups. You can simply change public address of one client using access_model_publish_address_set().

So if you have 2 group addresses you want to send to and want to switch between them you do this:

ERROR_CHECK(dsm_address_publish_add(group_address1, &m_group_address_handle1));
ERROR_CHECK(dsm_address_publish_add(group_address2, &m_group_address_handle2));

You call above codes only once. The purpose is to add the 2 group address into DSM database.

Now if you want the client publication address to group address 1 , you call this:

access_model_publish_address_set(yourgroupclient.model_handle, m_group_address_handle1));

If you want the client to send to group address 2 you call this:

access_model_publish_address_set(yourgroupclient.model_handle, m_group_address_handle2));

You can switch between them, call above function every time you switch.

The way we use the last client as group client, is just the way we chose to do that. You can use any client to send to group address, just apply the code above.

RE: Subscribe a group address for the Mesh Message

ajay — Tue, 30 Jan 2018 10:24:06 GMT

More hack in the code, seems in the nrf_mesh_config_app.h, also got a boundary that the Group only set with One only??

#define ACCESS_ELEMENT_COUNT (1 + SERVER_COUNT) /* One element per Simple OnOff client instance */

#define ACCESS_MODEL_COUNT (1 + /* Configuration client / \ 1 + / Health client / \ GROUP_COUNT + / Simple OnOff client (group) / \ SERVER_COUNT / Simple OnOff client (per server) */)

I should update this parameters also?

RE: Subscribe a group address for the Mesh Message

ajay — Tue, 30 Jan 2018 09:11:01 GMT

But i am still not full related the m_clients[GROUP_CLIENT_INDEX].model_handle Vs m_group_handler.

Should I call the following routine always in a pair, to maintain their relationship?

ERROR_CHECK(dsm_address_publish_add(group_address, &m_group_handle[m_group_count]));
ERROR_CHECK(access_model_publish_address_set(m_group_clients[m_group_count].model_handle, m_group_handle[m_group_count]));

To be specific, if i would like to call the simple_on_off_client_set_unreliable, how can i related the group_address, such that the group_handle, to the m_client(m_group_client) in my case?

RE: Subscribe a group address for the Mesh Message

ajay — Tue, 30 Jan 2018 08:48:37 GMT

So, in case if i not only have one group will be in the network, i should create

static simple_on_off_client_t m_clients[SERVER_COUNT];
static simple_on_off_client_t m_group_clients[GROUP_COUNT];

such that the m_client is used to talk with the individual server while m_group_client is used to talk with the group?

RE: Subscribe a group address for the Mesh Message

Hung Bui — Fri, 26 Jan 2018 11:33:33 GMT

Yes, but there are 4 clients on the client example (each one is one element ). 3 of them talk to the 3 servers and the last one talks to the group address. That's why you see m_clients[GROUP_CLIENT_INDEX].model_handle there.

RE: Subscribe a group address for the Mesh Message

ajay — Fri, 26 Jan 2018 09:52:52 GMT

Thanks Bui, Your message help a lot

When walk along the code , i am a bit confusion about the

m_clients[GROUP_CLIENT_INDEX].model_handle vs m_group_handle in main.c

ERROR_CHECK(access_model_publish_address_set(m_clients[GROUP_CLIENT_INDEX].model_handle, m_group_handle));

It is found that when the data broadcast to the Group, by sending by the function simple_on_off_client_set_unreliable, it is using the model_handle instead the m_group_handle;

Have i mixed up something there?

So, in case when i have more than one group, I should still make use of the m_clients[GROUP_CLIENT_INDEX],

RE: Subscribe a group address for the Mesh Message

Hung Bui — Thu, 25 Jan 2018 14:07:45 GMT

The group address (GROUP_ADDRESS = 0xCAFE) is assigned to the server in configuration phase.

You can find the assigning at PROV_STATE_CONFIG_SUBSCRIPTION event in do_config_step() in provisioner.c

If you want to assign different group address to different server, you can modify the code inside that event handler, and change the address.value there.

Another option is to change the subscription address locally on the server. To do that you follow what 's inside the configuration server on the server side handle_config_model_subscription_add().

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.

Similarly, when you want to broadcast to a group address or change between broadcast address, you do dsm_address_publish_add() to add the address to the database and then access_model_publish_address_set() to mount the address ID to the model. Check access_setup() in the client's code.

RE: Subscribe a group address for the Mesh Message

ajay — Thu, 25 Jan 2018 10:08:18 GMT

Can i have a pointer, which helper functions should be used to unsubscribe from the Model, when they are in that Group?

Or, should i do it in another way round?

RE: Subscribe a group address for the Mesh Message

ajay — Thu, 25 Jan 2018 02:36:46 GMT

Some study here, may i confirm it is the correct approach?

It seems i need extend the two Nordic models for the device.

Simplie On/Off Model- it is many to handle the optcode for light On/Off, and may be if in case, can add on the intensity parameters for the control of the brightness.

Configuration Model- besides the existing feature that Nordic defined, i need to extend the model, such that it can handle about the Group setting of the Light, such that i can assign the Group ID to the specific device.

?? But I still not very clear, how to link the Group ID that i set above, to the Group address of the Nordic Mesh Arch?? This is some confusion for me yet...

Hope i can make my questions clear.