Hi teams,
As the title describes, how can I find source/destination address inside mesh model callback functions?
Is there any API functions? Or should I modify callback function prototype to include access_message_rx_t or similar ones?
Hi teams,
As the title describes, how can I find source/destination address inside mesh model callback functions?
Is there any API functions? Or should I modify callback function prototype to include access_message_rx_t or similar ones?
Hi,
You can find the meta information (source, destination) inside access_message_rx_meta_t struct this struct is inside access_message_rx_t p_message that you get in the call back for message in the model.
Hi,
You can find the meta information (source, destination) inside access_message_rx_meta_t struct this struct is inside access_message_rx_t p_message that you get in the call back for message in the model.
I know.
I meant, if I want to get addresses when I use BT SIG model implementation in Mesh SDK, I should modify SDK code.
I just want to know whether there is no other way.
You can get the src and dst of any message regardless which model it is. Please check the p_rx_msg for example in the model call back handler. It's the variable with access_message_rx_t format:
It's inside p_rx_msg ->meta_data
Ah sorry I miss understood your question. In that case, yes you can modify the code inside p_rx_msg. As long as it doesn't change the behavior of the module (regarding Mesh activity), it's fine.
Mistake is mine.
I have confused with other callbacks in SDK.
access_message_rx_meta_t has the required information in it.
Thank you.