Using Simple message model.

RE: Using Simple message model.

turki — Mon, 26 Nov 2018 16:21:06 GMT

RE: Using Simple message model.

Bjørn Kvaale — Mon, 26 Nov 2018 15:21:51 GMT

turkiIt seems this case was made private. Hence it is not visible to you. Could you please create a new devzone case?

RE: Using Simple message model.

turki — Mon, 26 Nov 2018 12:33:59 GMT

hello Arya

where are you using the RSSI_server_index_get() function and why ?

RE: Using Simple message model.

turki — Mon, 26 Nov 2018 09:27:18 GMT

case ID:213044 is not available

i have the same issue

RE: Using Simple message model.

Arya — Wed, 29 Aug 2018 12:55:50 GMT

New case link.

case ID:213044

RE: Using Simple message model.

Arya — Tue, 28 Aug 2018 13:08:22 GMT

Okay Bjørn, will do that. Thank you

RE: Using Simple message model.

Bjørn Kvaale — Tue, 28 Aug 2018 13:03:27 GMT

Hi Arya,

Yes, please create a new case. Could you please comment here what the case ID of the new case is and/or upload a link to your new case?

RE: Using Simple message model.

Arya — Tue, 28 Aug 2018 08:44:13 GMT

Hi,

I think the error is in the way that I am adding the new model because, publish_appkey_handle, publish_address_handle, and opcodes are invalid in the function check_tx_params. Problem might be with the element index I guess. Should I begin a new case for this?

RE: Using Simple message model.

Arya — Wed, 22 Aug 2018 10:54:53 GMT

Hi Bjørn,

My error comes from simple_RSSI_client_set_unreliable -> access_model_publish -> packet_tx -> check_tx_params. I think the way I am setting the publishing address is wrong. Or is it something related to provisioning? Can you please check the way I am initiating model and setting address to send message. Probably there will be something wrong I guess.

RE: Using Simple message model.

Arya — Tue, 21 Aug 2018 12:28:06 GMT

Provisioner Log:

<t:          0>, main.c,  550, ----- BLE Mesh Light Switch Provisioner Demo -----
<t:          0>, mesh_softdevice_init.c,  112, Initializing SoftDevice...
<t:          0>, mesh_softdevice_init.c,   77, Enabling BLE...
<t:          1>, mesh_softdevice_init.c,   88, Ram base: 0x200032C8
<t:        604>, main.c,  488, Initializing and adding models
<t:        617>, main.c,  531, Setup defaults: Adding keys, addresses, and bindings 
<t:        769>, provisioner_helper.c,  329, netkey_handle: 0
<t:        781>, main.c,  578, <start> 
<t:      27358>, main.c,  117, Flash write complete
<t:      27360>, main.c,  565, Starting application ...
<t:      27362>, main.c,  567, Provisoned Nodes: 0, Configured Nodes: 0 Next Address: 0x0100
<t:      27366>, main.c,  568, Dev key : B3A51809537338801488B944EDE54B01
<t:      27369>, main.c,  569, Net key : 68F6AC161BB591FD9248501CF195BFF4
<t:      27372>, main.c,  570, App key : F927212BDC82948FB0A60E1992F5EE3A
<t:      27375>, main.c,  571, Press Button 1 to start provisioning and configuration process. 
0<t:    2635493>, main.c,  448, Button 1 pressed
<t:    2635495>, main.c,  361, Waiting for Client node to be provisioned ...
<t:    2640249>, provisioner_helper.c,  282, Scanning For Unprovisioned Devices
<t:    2667060>, provisioner_helper.c,  144, UUID seen: 0059FFFF00000000108AD6A930A6E556
<t:    2696197>, provisioner_helper.c,  144, UUID seen: 0059ABCDEFABCDEFACCDEFABCDEFABCD
<t:    2696200>, provisioner_helper.c,   95, UUID filter matched
<t:    2696652>, provisioner_helper.c,  259, Provisioning link established
<t:    2710138>, provisioner_helper.c,  254, Static authentication data provided
<t:    2722171>, provisioner_helper.c,  192, Provisioning completed received
<t:    2722174>, provisioner_helper.c,  197, Adding device address, and device keys
<t:    2722179>, provisioner_helper.c,  214, Addr: 0x0100 addr_handle: 0 netkey_handle: 0 devkey_handle: 2
<t:    2726297>, provisioner_helper.c,  155, Local provisioning link closed: prov_state: 2  remaining retries: 2
<t:    2726301>, main.c,  282, Provisioning successful
<t:    2726303>, provisioner_helper.c,  181, Provisioning complete. Node addr: 0x0100 elements: 5
<t:    2726307>, node_setup.c,  672, Configuring Node: 0x0100
<t:    2726310>, node_setup.c,  586, Config client setup: devkey_handle:2 addr_handle:0
<t:    2726313>, node_setup.c,  361, Getting composition data
<t:    2726377>, main.c,  117, Flash write complete
<t:    2780045>, main.c,  332, Config client event
<t:    2780048>, node_setup.c,  371, Adding appkey
<t:    2800057>, main.c,  332, Config client event
<t:    2800059>, node_setup.c,  234, Unexpected opcode: exp 0x8003  rx 0x0002
<t:    2809682>, main.c,  332, Config client event
<t:    2809684>, node_setup.c,  272, opcode status field: 0 
<t:    2809687>, node_setup.c,  382, App key bind: Health server
<t:    2810584>, main.c,  332, Config client event
<t:    2810586>, node_setup.c,  272, opcode status field: 0 
<t:    2810589>, node_setup.c,  450, Setting publication address for the health server to 0x0001
<t:    2813780>, main.c,  332, Config client event
<t:    2813782>, node_setup.c,  272, opcode status field: 0 
<t:    2813784>, node_setup.c,  416, App key bind: Simple On/Off client on element 0x0101
<t:    2815287>, main.c,  332, Config client event
<t:    2815290>, node_setup.c,  272, opcode status field: 0 
<t:    2815292>, node_setup.c,  416, App key bind: Simple On/Off client on element 0x0102
<t:    2815979>, main.c,  332, Config client event
<t:    2815981>, node_setup.c,  272, opcode status field: 0 
<t:    2815984>, node_setup.c,  416, App key bind: Simple On/Off client on element 0x0103
<t:    2816935>, main.c,  332, Config client event
<t:    2816937>, node_setup.c,  272, opcode status field: 0 
<t:    2816939>, node_setup.c,  416, App key bind: Simple On/Off client on element 0x0104
<t:    2817875>, main.c,  332, Config client event
<t:    2817877>, node_setup.c,  272, opcode status field: 0 
<t:    2817880>, node_setup.c,  301, Set: on/off client: 0x0101  pub addr: 0x0105
<t:    2821600>, main.c,  332, Config client event
<t:    2821602>, node_setup.c,  272, opcode status field: 0 
<t:    2821605>, node_setup.c,  301, Set: on/off client: 0x0102  pub addr: 0x0106
<t:    2825063>, main.c,  332, Config client event
<t:    2825065>, node_setup.c,  272, opcode status field: 0 
<t:    2825067>, node_setup.c,  301, Set: on/off client: 0x0103  pub addr: 0xC002
<t:    2829581>, main.c,  332, Config client event
<t:    2829583>, node_setup.c,  272, opcode status field: 0 
<t:    2829586>, node_setup.c,  301, Set: on/off client: 0x0104  pub addr: 0xC002
<t:    2833837>, main.c,  332, Config client event
<t:    2833839>, node_setup.c,  272, opcode status field: 0 
<t:    2833842>, main.c,  248, Configuration of device 0 successful
<t:    2833845>, provisioner_helper.c,  282, Scanning For Unprovisioned Devices
<t:    2833902>, main.c,  117, Flash write complete
<t:    2864209>, provisioner_helper.c,  144, UUID seen: 0059FFFF00000000108AD6A930A6E556
<t:    2864212>, provisioner_helper.c,   95, UUID filter matched
<t:    2864727>, provisioner_helper.c,  259, Provisioning link established
<t:    2877566>, provisioner_helper.c,  254, Static authentication data provided
<t:    2890351>, provisioner_helper.c,  192, Provisioning completed received
<t:    2890354>, provisioner_helper.c,  197, Adding device address, and device keys
<t:    2890359>, provisioner_helper.c,  214, Addr: 0x0105 addr_handle: 1 netkey_handle: 0 devkey_handle: 3
<t:    2894056>, provisioner_helper.c,  155, Local provisioning link closed: prov_state: 2  remaining retries: 2
<t:    2894060>, main.c,  282, Provisioning successful
<t:    2894062>, provisioner_helper.c,  181, Provisioning complete. Node addr: 0x0105 elements: 2
<t:    2894066>, node_setup.c,  672, Configuring Node: 0x0105
<t:    2894069>, node_setup.c,  586, Config client setup: devkey_handle:3 addr_handle:1
<t:    2894073>, node_setup.c,  361, Getting composition data
<t:    2894136>, main.c,  117, Flash write complete
<t:    2949503>, main.c,  332, Config client event
<t:    2949505>, node_setup.c,  371, Adding appkey
<t:    2952678>, main.c,  332, Config client event
<t:    2952680>, node_setup.c,  272, opcode status field: 0 
<t:    2952683>, node_setup.c,  382, App key bind: Health server
<t:    2953486>, main.c,  332, Config client event
<t:    2953489>, node_setup.c,  272, opcode status field: 0 
<t:    2953491>, node_setup.c,  397, App key bind: Simple On/Off server
<t:    2954236>, main.c,  332, Config client event
<t:    2954238>, node_setup.c,  272, opcode status field: 0 
<t:    2954241>, node_setup.c,  450, Setting publication address for the health server to 0x0001
<t:    2957459>, main.c,  332, Config client event
<t:    2957461>, node_setup.c,  272, opcode status field: 0 
<t:    2957464>, node_setup.c,  476, Set: on/off server pub addr: 0x0101
<t:    2960840>, main.c,  332, Config client event
<t:    2960843>, node_setup.c,  272, opcode status field: 0 
<t:    2960845>, node_setup.c,  487, Adding subscription
<t:    2962841>, main.c,  332, Config client event
<t:    2962843>, node_setup.c,  272, opcode status field: 0 
<t:    2962845>, main.c,  248, Configuration of device 1 successful
<t:    2962848>, provisioner_helper.c,  282, Scanning For Unprovisioned Devices
<t:    2962905>, main.c,  117, Flash write complete
<t:    3140366>, main.c,  311, Node 0x0100 alive with 0 active fault(s), RSSI: -53
<t:    3283386>, main.c,  311, Node 0x0105 alive with 0 active fault(s), RSSI: -50
<t:    3467786>, main.c,  311, Node 0x0100 alive with 0 active fault(s), RSSI: -52
<t:    3611803>, main.c,  311, Node 0x0105 alive with 0 active fault(s), RSSI: -44
<t:    3795738>, main.c,  311, Node 0x0100 alive with 0 active fault(s), RSSI: -52
<t:    3939276>, main.c,  311, Node 0x0105 alive with 0 active fault(s), RSSI: -47

RE: Using Simple message model.

Bjørn Kvaale — Tue, 21 Aug 2018 12:16:35 GMT

Could you please also upload the provisioner log information? Mesh error 7 refers to NRF_ERROR_INVALID_PARAM from nrf_error.h. It seems to me as if the client was successfully provisioned, but not configured. It would be useful to see the provisioner log to double check this assumption.

RE: Using Simple message model.

Arya — Tue, 21 Aug 2018 12:05:20 GMT

Log of client:

<t:          0>, main.c,  336, ----- BLE Mesh Light Switch Client Demo -----
<t:          0>, mesh_softdevice_init.c,  112, Initializing SoftDevice...
<t:          0>, mesh_softdevice_init.c,   77, Enabling BLE...
<t:          2>, mesh_softdevice_init.c,   88, Ram base: 0x200032C8
<t:        543>, main.c,  303, Initializing and adding models1
<t:       5405>, main.c,  364, Device UUID : 0059ABCDEFABCDEFACCDEFABCDEFABCD
<t:    1058393>, main.c,  127, Successfully provisioned
<t:    1058396>, main.c,  131, Node Address: 0x0100 
4<t:    2727012>, main.c,  228, Button 4 pressed
entering button 4 field
Sending to group address 0xCAFE
<t:    2759785>, app_error_weak.c,  105, Mesh error 7 at 0x00026B15 (C:\Users\arya\Desktop\Bluetooth\BLE Tools\mesh_V_2.0.1\mesh\nrf5_SDK_for_Mesh_v2.0.1_src_II\examples\Simple_RSSI\client\src\main.c:479)

Log of server:

<t:          0>, main.c,  236, ----- BLE Mesh Light Switch Server Demo -----
<t:          0>, mesh_softdevice_init.c,  112, Initializing SoftDevice...
<t:          0>, mesh_softdevice_init.c,   77, Enabling BLE...
<t:          2>, mesh_softdevice_init.c,   88, Ram base: 0x200032C8
<t:        584>, main.c,  204, Initializing and adding models
<t:       5456>, main.c,  264, Device UUID : 0059FFFF00000000108AD6A930A6E556
<t:      83213>, main.c,   97, Successfully provisioned
<t:      83215>, main.c,  101, Node Address: 0x0105

RE: Using Simple message model.

Bjørn Kvaale — Tue, 21 Aug 2018 11:28:57 GMT

Could you please upload the logging information from the client & server? You can run a debugging session using Segger Embedded Studio & just copy the logging information directly from the debug terminal.

RE: Using Simple message model.

Arya — Tue, 21 Aug 2018 10:52:02 GMT

Hi Bjørn,

Now I don't get all those errors. But I can not send a string message. I added one button to send message using app timer in each one second using the the same function of simple message model, except that I am using my own API now. But it is returning NRF_ERROR_INVALID_PARAM. I know that this is because publication address allocation problem. How can I set my address properly? Or is it because model is not bound to appkey? The function is as shown below.

void address_new_set(uint16_t addr)                   //setting address for sending message
{
  ERROR_CHECK(dsm_address_publish_add(addr, &m_central_handle));
  ERROR_CHECK(access_model_publish_address_set(r_server.model_handle, m_central_handle));
}

void send_new_message(void)                         //function for sending a simple message
{
    uint32_t status=0;
    uint8_t buffer[5] = "hello";
    uint8_t length;
    uint16_t address;
    access_message_tx_t msg;
    length = sizeof(buffer); 
    
    if(length)
    {
      address = 0xCAFE; 
      address_new_set(address);
      SEGGER_RTT_printf(0,"Sending to group address 0x%04x\n", address);
      status= simple_RSSI_client_set_unreliable(r_clients.model_handle, &buffer, GROUP_MSG_REPEAT_COUNT);

      if(status == NRF_ERROR_INVALID_STATE ||
      status == NRF_ERROR_BUSY||
      status == NRF_ERROR_NO_MEM)
      {
        __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Cannot send. Device is busy.\n");
        hal_led_blink_ms(LEDS_MASK, 50, 4);
      }
      else
      {
         ERROR_CHECK(status);
      }
    }
  
}

I took this function from simple message model and modified it.

RE: Using Simple message model.

Arya — Mon, 20 Aug 2018 11:07:29 GMT

Hi Bjørn,

It got resolved. I need only one switch for this model so I updated my function as this:

static void models_init_cb(void)
{
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Initializing and adding models1\n");
    uint32_t status = 0;

    for (uint32_t i = 0; i < CLIENT_MODEL_INSTANCE_COUNT; ++i)
    {
        m_clients[i].status_cb = client_status_cb;
        m_clients[i].timeout_cb = client_publish_timeout_cb;
        status = simple_on_off_client_init(&m_clients[i], i + 1);
        ERROR_CHECK(status);
        if(status == NRF_SUCCESS)
          {
            printf("NRF_SUCCESS\n");
          }

        ERROR_CHECK(access_model_subscription_list_alloc(m_clients[i].model_handle));
    }
    
        r_clients.status_cb = client_RSSI_status_cb;
        r_clients.timeout_cb = client_publish_timeout_cb;
        
        status = simple_RSSI_client_init(&r_clients, 0);
        ERROR_CHECK(status);
        if(status == NRF_SUCCESS)
          {
            printf("NRF_SUCCESS\n");
          }
        ERROR_CHECK(access_model_subscription_list_alloc(r_clients.model_handle));
}

changed this function too RSSI_server_index_get().

uint32_t index = p_client - &r_clients;

Also increased ACCESS_MODEL_COUNT. Now there is no error. Is this the correct way to do it? Assuming that this is the correct way to do it, how should I modify if I had more than one switch for this model?

RE: Using Simple message model.

Arya — Mon, 20 Aug 2018 07:12:58 GMT

Hi Bjørn,

Sorry for the delay in reply. Error is coming from the function given below.

static void models_init_cb(void)
{
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Initializing and adding models1\n");
    uint32_t status = 0;

    for (uint32_t i = 0; i < CLIENT_MODEL_INSTANCE_COUNT; ++i)
    {
        m_clients[i].status_cb = client_status_cb;
        m_clients[i].timeout_cb = client_publish_timeout_cb;
        r_clients[i].status_cb = client_RSSI_status_cb;
        r_clients[i].timeout_cb = client_publish_timeout_cb;
        status = simple_on_off_client_init(&m_clients[i], i + 1);
        ERROR_CHECK(status);
        if(status == NRF_SUCCESS)
          {
            printf("NRF_SUCCESS\n");
          }

        ERROR_CHECK(access_model_subscription_list_alloc(m_clients[i].model_handle));
        status = simple_RSSI_client_init(&r_clients[i], i + 2);
        ERROR_CHECK(status);
        if(status == NRF_SUCCESS)
          {
            printf("NRF_SUCCESS\n");
          }
        ERROR_CHECK(access_model_subscription_list_alloc(r_clients[i].model_handle));
    }
}

error is in the 13th line of function given above. It executes once i.e when i = 0 and when i becomes one it gives an error at that point.

Output is:

NRF_SUCCESS
NRF_SUCCESS
<t:       7696>, app_error_weak.c,  105, Mesh error 15 at 0x000267CD

I could not find the address 0x000267CD in .map file.

As you said the error is "Multiple model instances per element is not allowed".

I have both custom server model as well as custom client model. Now I am trying to add custom client model. I am initializing my custom model like simple_on_off_client model. I have a function similar to that named simple_RSSI_client_init().

Sorry I could not understand this question.

"Do you want four client models (e.g. one for each button) on the client board?"

I don't have a clear idea about element index.I still have the above error. I changed some parameters in function element_has_model_id but no change.

RE: Using Simple message model.

Bjørn Kvaale — Fri, 17 Aug 2018 11:36:40 GMT

Hi Arya,

Mesh error 15 refers to NRF_ERROR_FORBIDDEN (see nrf_error.h). Do you have any idea where this error is called? What you can do is open the .map file in the build folder of your mesh example & find the location of 0x000267CD. It might be between two values.

Most likely it is an error when you initialize the simple_model_client_init(). If it is, then the error says that "Multiple model instances per element is not allowed" (see declaration of function in simple_on_off_client.h). What this means is that you are initializing the simple_on_off_model & the simple_message_model on the same element (i.e. element indexes 2,3,4).

I will double check about this internally & get back to you.

Are you trying to initialize the custom client or the custom server model? The custom model should be initialized similar to the simple_on_off_client model (i.e. via the simple_on_off_client_init() function), like you have done above.

Do you want four client models (e.g. one for each button) on the client board?

Kind Regards,

Bjørn

RE: Using Simple message model.

Arya — Tue, 14 Aug 2018 12:58:12 GMT

Hi Bjørn,

I tried this way.

static void models_init_cb(void)
{
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Initializing and adding models1\n");
    uint32_t status = 0;

    for (uint32_t i = 0; i < CLIENT_MODEL_INSTANCE_COUNT; ++i)
    {
        m_clients[i].status_cb = client_status_cb;
        m_clients[i].timeout_cb = client_publish_timeout_cb;
        r_clients[i].status_cb = new_client_status_cb;
        r_clients[i].timeout_cb = client_publish_timeout_cb;
        ERROR_CHECK(simple_on_off_client_init(&m_clients[i], i + 1));
        ERROR_CHECK(access_model_subscription_list_alloc(m_clients[i].model_handle));
        status = simple_model_client_init(&r_clients[i], i + 2);
        ERROR_CHECK(status);
        if(status == NRF_SUCCESS)
          {
            printf("NRF_SUCCESS\n");
          }
        ERROR_CHECK(access_model_subscription_list_alloc(r_clients[i].model_handle));
    }
}

But it is returning this error

app_error_weak.c, 105, Mesh error 15 at 0x000267CD. Can you help me with this?

RE: Using Simple message model.

Arya — Tue, 14 Aug 2018 11:29:56 GMT

Hi Bjørn,

Thank you for that suggestion. I have created a new model based on that. How can I init that new model? I tried adding the new model in 'models_init_cb()', along with simple on off model. I added a snippet given below.

static void models_init_cb(void)
{
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Initializing and adding models\n");
    uint32_t status = 0;

    for (uint32_t i = 0; i < CLIENT_MODEL_INSTANCE_COUNT; ++i)
    {
        m_clients[i].status_cb = client_status_cb;
        m_clients[i].timeout_cb = client_publish_timeout_cb;
        ERROR_CHECK(simple_on_off_client_init(&m_clients[i], i + 1));
        ERROR_CHECK(access_model_subscription_list_alloc(m_clients[i].model_handle));
    }
    for (uint32_t j = 0; j < CLIENT_MODEL_INSTANCE_COUNT; ++j)
    {
        r_clients[j].status_cb = new_client_status_cb;
        r_clients[j].timeout_cb = client_publish_timeout_cb;
        ERROR_CHECK(simple_model_client_init(&r_clients[j], j + 1));
        ERROR_CHECK(access_model_subscription_list_alloc(r_clients[i].model_handle));
    }

}

But it is returning error. when I removed the simple on off part, it is returning NRF_SUCCESS. Should I add it in a different function similar to 'models_init_cb'? If then how should I add the new model to the structure 'mesh_stack_init_params_t'? Like this?

static void mesh_init(void)
{
    mesh_stack_init_params_t init_params =
    {
        .core.irq_priority       = NRF_MESH_IRQ_PRIORITY_LOWEST,
        .core.lfclksrc           = DEV_BOARD_LF_CLK_CFG,
        .core.p_uuid             = m_client_node_uuid,
        .models.models_init_cb   = models_init_cb,
        .models.models_init_cb   = models_init_cb2,
        .models.config_server_cb = config_server_evt_cb
    };
    ERROR_CHECK(mesh_stack_init(&init_params, &m_device_provisioned));
}

Where the 'models_init_cb2' is a function which initializes only the new client model? Is it like I can not add a new model apart from simple on off model with out removing it?

RE: Using Simple message model.

Bjørn Kvaale — Fri, 10 Aug 2018 11:56:15 GMT

What about if you create a new model based off of the simple on off model instead? If you take a look at the light switch client example, you can see that when a user presses button 1 on the dev kit, the client sends a unicast message to the first provisioned server using the simple_on_off_client_set() function. This function first makes sure that the parameter pointer p_client & the status_cb pointer are not null. Then, a check is done to make sure the client is not in an invalid state.

It's this struct that is interesting for us:

/** Simple OnOff Client state structure. */
struct __simple_on_off_client
{
    /** Model handle assigned to the client. */
    access_model_handle_t model_handle;
    /** Status callback called after status received from server. */
    simple_on_off_status_cb_t status_cb;
    /** Timeout callback called after acknowledged message sending times out */
    simple_on_off_timeout_cb_t timeout_cb;
    /** Internal client state. */
    struct
    {
        bool reliable_transfer_active; /**< Variable used to determine if a transfer is currently active. */
        simple_on_off_msg_set_t data;  /**< Variable reflecting the data stored in the server. */
    } state;
};

The simple_on_off_msg_set struct contains the on_off state (i.e. whether the server light should be on or off).

The simple_on_off_client_set() function then calls send_reliable_message(), which will then send the data via the access_model_reliable_publish() call on the access layer of the mesh stack.

What if you try to create a new model based on the simple on off model & then update the simple_on_off_msg_set_t struct to send a string message instead of uint8_t on_off?

I would also recommend making a copy of each of the three light switch examples (provisioner, client, server) & modify those. This way, if you were to make a mistake & the mesh network does not work anymore, you can refer back on the working light switch example. Hope that helps!

RE: Using Simple message model.

Arya — Thu, 09 Aug 2018 09:16:53 GMT

Hi Bjørn,

I am working in mesh 2.0.1. I have added this simple message model into my light switch example. What I actually want is to send a string from client to server. That is done through simple message model. But it is not handling messages as it is in simple on off model. I have gone through light switch model as well as the documentation on adding new models. I think I should merge these two models (Light switch and simple message model). Or I should remove on off model and add a new model which can send a string and can handle messages. Would that be possible?

RE: Using Simple message model.

Bjørn Kvaale — Thu, 09 Aug 2018 06:54:18 GMT

Hi,

I would not refer to this simple message model, as it is using an outdated mesh sdk. I would rather take a look at the light switch example in the newest mesh sdk v2.1.1. Follow the testing guidelines there and run a debug session or have an rtt viewer open in each of the three boards (provisioner, client, server) & take a look at how the light switch example works.

Also, make sure to take a look at the configuration model in the provisioner (config_client.c & config_client.h), as well as config_server.c & config_server.h in the client example. I would also recommend taking a look at this documentation, as well as the simple OnOff Model documentation.