Subscribe a group address for the Mesh Message

[ajay]

Currently, I am working with the Nordic SimpleOnOff Model of the Light switch in the Bluetooth Mesh.

I am good that the light in the mesh can be set on/off after Provisioned.

Now, i would like to divide the Board into 2 Groups, let's said Group A and Group B.

But i am not very sure how to work with that?

How can i drive a specify device to bind to a specific Group Address? I believe that i should subscribe to some service, but any sample code or pointer that can show how can I subscribe the service for that "group"?

After that, how should i send the message to "This Group" of light for On/Off.

I tried to study the code of access_model_publish, from the Mesh SDK, but seems it did not have a way to specify the Group address for boardcast.

And how about the Receiver? Should i define another set of OpCode, like SIMPLE_ON_OFF_OPCODE_GROUP_SET to do the operation there?

[Hung Bui]

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.

[Hung Bui]

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.