RE: Issue with sending message from client to client in mesh

Mttrinh — Thu, 02 Jul 2020 14:45:23 GMT

Hi,

Why do you have two of the same callback?

I'm not sure I understand what you are trying to do here, could you elaborate?

Can you also describe how you configured it in the nRF Mesh app?

RE: Issue with sending message from client to client in mesh

Liv — Thu, 02 Jul 2020 09:51:09 GMT

Hi Mttrinh,

Thanks for reply. I followed the steps you mentioned and now it works. But now I have another issue with action button in periodic publishing like in this code:

/* This callback is called periodically if model is configured for periodic publishing */
static void app_gen_onoff_client_publish_interval_cb(access_model_handle_t handle, void * p_self)
{
     __LOG(LOG_SRC_APP, LOG_LEVEL_WARN, "Publish desired message here.\n");
    
      button_event_handler(1);

//    uint32_t status = NRF_SUCCESS;
//    generic_onoff_set_params_t set_params;
//    model_transition_t transition_params;
//    static uint8_t tid = 0;
//
//    set_params.tid = tid++;
//    transition_params.delay_ms = APP_ONOFF_DELAY_MS;
//    transition_params.transition_time_ms = APP_ONOFF_TRANSITION_TIME_MS;
//
//           nrf_delay_ms(3000);
//
//          set_params.on_off = !set_params.on_off;
//
//         __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Sending msg: ONOFF SET %d\n", set_params.on_off);
//        (void)access_model_reliable_cancel(m_clients[1].model_handle);
//            status = generic_onoff_client_set(&m_clients[1], &set_params, &transition_params);
//            hal_led_pin_set(ONOFF_SERVER_2_LED, set_params.on_off);
//            //break;
//
//        switch (status)
//    {
//        case NRF_SUCCESS:
//            break;
//
//        case NRF_ERROR_NO_MEM:
//        case NRF_ERROR_BUSY:
//        case NRF_ERROR_INVALID_STATE:
//            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Client cannot send\n");
//            hal_led_blink_ms(LEDS_MASK, LED_BLINK_SHORT_INTERVAL_MS, LED_BLINK_CNT_NO_REPLY);
//            break;
//
//        case NRF_ERROR_INVALID_PARAM:
//            /* Publication not enabled for this client. One (or more) of the following is wrong:
//             * - An application key is missing, or there is no application key bound to the model
//             * - The client does not have its publication state set
//             *
//             * It is the provisioner that adds an application key, binds it to the model and sets
//             * the model's publication state.
//             */
//            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Publication not configured for client\n");
//            break;
//
//        default:
//            ERROR_CHECK(status);
//            break;
//    }
}/* This callback is called periodically if model is configured for periodic publishing */
static void app_gen_onoff_client_publish_interval_cb(access_model_handle_t handle, void * p_self)
{
     __LOG(LOG_SRC_APP, LOG_LEVEL_WARN, "Publish desired message here.\n");
    
      button_event_handler(1);

//    uint32_t status = NRF_SUCCESS;
//    generic_onoff_set_params_t set_params;
//    model_transition_t transition_params;
//    static uint8_t tid = 0;
//
//    set_params.tid = tid++;
//    transition_params.delay_ms = APP_ONOFF_DELAY_MS;
//    transition_params.transition_time_ms = APP_ONOFF_TRANSITION_TIME_MS;
//
//           nrf_delay_ms(3000);
//
//          set_params.on_off = !set_params.on_off;
//
//         __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Sending msg: ONOFF SET %d\n", set_params.on_off);
//        (void)access_model_reliable_cancel(m_clients[1].model_handle);
//            status = generic_onoff_client_set(&m_clients[1], &set_params, &transition_params);
//            hal_led_pin_set(ONOFF_SERVER_2_LED, set_params.on_off);
//            //break;
//
//        switch (status)
//    {
//        case NRF_SUCCESS:
//            break;
//
//        case NRF_ERROR_NO_MEM:
//        case NRF_ERROR_BUSY:
//        case NRF_ERROR_INVALID_STATE:
//            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Client cannot send\n");
//            hal_led_blink_ms(LEDS_MASK, LED_BLINK_SHORT_INTERVAL_MS, LED_BLINK_CNT_NO_REPLY);
//            break;
//
//        case NRF_ERROR_INVALID_PARAM:
//            /* Publication not enabled for this client. One (or more) of the following is wrong:
//             * - An application key is missing, or there is no application key bound to the model
//             * - The client does not have its publication state set
//             *
//             * It is the provisioner that adds an application key, binds it to the model and sets
//             * the model's publication state.
//             */
//            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Publication not configured for client\n");
//            break;
//
//        default:
//            ERROR_CHECK(status);
//            break;
//    }
}

I configured them with nRF Mesh app and after that in SES console print "Publication not configured for client 2" from client who publishes:

I don't now where is the problem.

Kind regards,

Liv

RE: Issue with sending message from client to client in mesh

Mttrinh — Wed, 01 Jul 2020 16:36:39 GMT

Hi,

To be able to send from client example to client example, you need to add a server model to the other client example. The server model needs to be on a different element than the client model, so you need to add another element. Also, remember to increase the model count and element count in your configuration.