Add mesh model to group address

[Simsim]

Hi Nordic Team

Starting Point:

Provisioning of dimming server is done with code from the PB Remote provisioner, working so far.

Publish of model to group is acived similar to the PB remote model print shows publishing of mesh telegram also working.

//  add dimming server publish to group
    ERROR_CHECK(dsm_appkey_add(0, m_netkey_handle, appkey, &m_appkey_handle));
    ERROR_CHECK(dsm_address_publish_add(PUBLISH_GROUP_DIMMING, &m_Level_address_handle));
    ERROR_CHECK(access_model_application_bind(m_level_server_0.server.model_handle, m_appkey_handle));

    ERROR_CHECK(access_model_publish_address_set(m_level_server_0.server.model_handle, m_Level_address_handle));
    ERROR_CHECK(access_model_publish_application_set(m_level_server_0.server.model_handle, m_appkey_handle));
    
    

subscribing to group i tried the following:

// add subscription of dimming server
    ERROR_CHECK(dsm_address_subscription_add(PUBLISH_GROUP_DIMMING, &m_Level_address_handle));
    ERROR_CHECK(access_model_subscription_add(m_level_server_0.server.model_handle, m_Level_address_handle));    
    

Question 1:

What is missing while adding subsription?

Question 2:

Is there an example or description how to use the config_server.c properly?

thanks for give some advices

[tesc]

Hi,

In general, the config server is not used directly. All nodes have a config server (and are required to have one according to the specification,) but the way it works is it is initialized and then it receives configurations from a configuration client.

Therefore, what you do for configuring a device, is use the configuration client (e.g. on the provisioner) in order to configure the device. For this you use the Configuration client API on the device performing the configuration (may or may not be the same device as the device being configured.)

An example of configuration is found in the provisioning example, in node_setup.c, where the function config_step_execute() is a switchboard for calling configuration client API functions, either directly or through helper functions also found in node_setup.c.

Direct access to dsm should not be needed for configuration. The uses of the dsm API functions in provisioner_helper.c and node_setup.c are for low-level operations such as self-provision (not configure) the provisioner, and retrieve the device key (which is needed for using the configuration model.) You may need to retrieve the device key, but apart from that you should not need to directly use dsm.

Regards,
Terje

[Simsim]

Hi Terje

Sorry for my late reply, ok i see what i did wrong.

Are there plans to implement the Remote Provsioner Example properly in the SDK?

Thanks for the Quick and helpful answer.

Regards Simon