Dear support,
in nRF Mesh SDK each model can be configured to always publish segmented messages to improve reliability.
For example, the macro for the generic on off server initialization has a _force_segmented parameter to configure this behavior
/**
* Macro to create application level app_onoff_server_t context.
*
* Individual timer instances are created for each model instance.
*
* @param[in] _name Name of the app_onoff_server_t instance
* @param[in] _force_segmented If the Generic OnOff server shall use force segmentation of messages
* @param[in] _mic_size MIC size to be used by Generic OnOff server
* @param[in] _set_cb Callback for setting the application state to given value.
* @param[in] _get_cb Callback for reading the state from the application.
*/
#define APP_ONOFF_SERVER_DEF(_name, _force_segmented, _mic_size, _set_cb, _get_cb) \
APP_TIMER_DEF(_name ## _timer); \
APP_TIMER_DEF(_name ## _retry_timer); \
static app_onoff_server_t _name = \
{ \
.server.settings.force_segmented = _force_segmented, \
.server.settings.transmic_size = _mic_size, \
.p_timer_id = &_name ## _timer, \
.p_timer_retry_id = &_name ## _retry_timer, \
.onoff_set_cb = _set_cb, \
.onoff_get_cb = _get_cb \
};
I cannot find an equivalent machanism in Connect SDK.
Could you please give me an advice?
Thank you
Enrico
