Provisioner node : Unhandled mesh event

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Wed, 06 Jun 2018 12:56:49 GMT

No worries. Good luck!

RE: Provisioner node : Unhandled mesh event

Arij — Wed, 06 Jun 2018 12:54:12 GMT

Thank you again Bjørn Kvaale, I appreciate your help.

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Wed, 06 Jun 2018 12:42:59 GMT

Not that I am aware of. You can try changing the tx output power so that you do not need to place the nodes so far away from each other. Take a look at this case for more info regarding this.

RE: Provisioner node : Unhandled mesh event

Arij — Wed, 06 Jun 2018 12:28:38 GMT

So nothing related with my message model? do i just have to place nodes in different rooms ?

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Wed, 06 Jun 2018 12:20:49 GMT

Great! Relaying nodes should work out of the box. Take a look at the light switch server example & you will find the bool m_relay_enable. You can see that this bool is set true inside network_init() in network.c. The should_relay() function then decides whether a message should be relayed or not.

RE: Provisioner node : Unhandled mesh event

Arij — Wed, 06 Jun 2018 11:13:55 GMT

Thank you for your help, I solved it , i'am now able to print my message on server main.c file and my message is handled, it was about the configuration of new model in the provisioner node_setup.c, i followed exactly the configuration of simple_on_off model, i just needed to bind the appkey to my new model, now i want to relay my message to another node, could you please guide me on that?

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Wed, 06 Jun 2018 08:27:22 GMT

Again, take a look at the health comment I mentioned before & make sure that you really understand it. Then, you can do something similar. As I mentioned before, every time a mesh message is handled:

"The handle_fault_status() function inside health_client.c handles the incoming health message, sets the event type to HEALTH_CLIENT_EVT_TYPE_FAULT_STATUS_RECEIVED & calls the event_handler() at the bottom, which happens to be the app_health_event_cb() function"

The event_handler() call happens to be the call to app_health_event_cb(). You need to call the callback function every time you get a new mesh message.

RE: Provisioner node : Unhandled mesh event

Arij — Tue, 05 Jun 2018 12:39:27 GMT

I thought it was called with the initialization of the message model server, so do I have to call this function in rx_set_unreliable_cb() because I used simple_message_client_set_unreliable() function on client side to send my message

static void rx_set_unreliable_cb(access_model_handle_t handle, const access_message_rx_t * p_message, void * p_args)
{
    simple_message_server_t * p_server = p_args;
    NRF_MESH_ASSERT(p_server->set_cb != NULL);
    p_server->set_cb(p_server, p_message->meta_data.src, p_message->meta_data.dst, p_message->p_data,p_message->length);
    
}

As you can see i modified this function and set_cb is called inside it and initialized in models_init_cb() function in main.c server node, is that what you told me to do?

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Tue, 05 Jun 2018 12:15:55 GMT

Are you calling this callback function when you receive a message like I have explained in my previous comment (i.e. calling the callback function inside the function that handles all of the mesh messages)?

RE: Provisioner node : Unhandled mesh event

Arij — Tue, 05 Jun 2018 07:58:51 GMT

Yes I'am using the simple_on_off model in addition to the simple_message model and on server side I did make callback function like so :

and initialization in server main.c like so

i believe there is something wrong here or related with configuration of new model, in the provisioner.c I only added this two lines in main provisioner.c to configure my new model, am i supposed to do something else ?

/*Bind message client to App key, and configure publication key */
ERROR_CHECK(access_model_application_bind(m_message_client.model_handle, m_dev_handles.m_appkey_handle));
ERROR_CHECK(access_model_publish_application_set(m_message_client.model_handle, m_dev_handles.m_appkey_handle));

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Tue, 05 Jun 2018 06:58:43 GMT

Does this mean that you are using the simple_on_off model in addition to the simple_message model? If so, it makes sense to increase the ACCESS_MODEL_COUNT. If you are switching out the simple_on_off model with the simple_message model, I would not increase ACCESS_MODEL_COUNT.

You could have a callback function in main that gets called whenever a message gets sent to the server. For an example of how this is initialized & done in practice, have a look at the app_health_event_cb() in the provisioner of the light switch example in Mesh SDK v2.0.1. The app_health_event_cb function gets called in models_init_cb() inside the health_client_init() function. The handle_fault_status() function inside health_client.c handles the incoming health message, sets the event type to HEALTH_CLIENT_EVT_TYPE_FAULT_STATUS_RECEIVED & calls the event_handler() at the bottom, which happens to be the app_health_event_cb() function.

RE: Provisioner node : Unhandled mesh event

Arij — Mon, 04 Jun 2018 12:23:23 GMT

I fixed the errors by increasing ACCESS_MODEL_COUNT to consider the new simple message model with the other models, the initialization of both models works (on_off and message), after that Unhandled mesh event doesn't occur, now still not able to print my message on server main.c, any idea please?

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Mon, 04 Jun 2018 12:15:16 GMT

What errors are you receiving? Do you have a log that you can upload to this case?

RE: Provisioner node : Unhandled mesh event

Arij — Mon, 04 Jun 2018 11:48:35 GMT

Thank you for your reply, i don't understand why errors occur when i do the initialization of simple_message model with simple_on_off initialization, and this new model considered as on_off model intance that cannot be in the same element

RE: Provisioner node : Unhandled mesh event

Bjørn Kvaale — Mon, 04 Jun 2018 11:33:58 GMT

This link might be useful for creating new models. I would definitely try to add the simple message model like it has been done in the simple on_off model to handle the messages. In general, just try to see how the light switch example has initialized the simple on off model & do something similar for your own model.