Lack of TTL option in Access APIhttps://devzone.nordicsemi.com/f/nordic-q-a/47263/lack-of-ttl-option-in-access-apiSome models such as the Time Server requires that certain messages are sent with a TTL of 0. (See 5.3.1.2.2 Sending a Time Status message). However, not all messages sent from this model should use TTL 0. From the Mesh Profile specification, 3.7.4.1en-USTelligent Community 13Thu, 16 May 2019 09:07:11 GMTRE: Lack of TTL option in Access APIhttps://devzone.nordicsemi.com/thread/187465?ContentTypeID=1Thu, 16 May 2019 09:07:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2db63928-ad21-437e-9c7f-2efcf09a7f66JonasJ<p>The problem with that API call is that it changes the models publish TTL for all messages. It&#39;s only those messages that are sent&nbsp; unsolicited that should have TTL 0.</p> <p>Thanks for pointing it out, it might work to use a get() -&gt; set() -&gt; publish() -&gt; set() sequence, but it doesn&#39;t look very clean.</p><div style="clear:both;"></div>RE: Lack of TTL option in Access APIhttps://devzone.nordicsemi.com/thread/187457?ContentTypeID=1Thu, 16 May 2019 08:57:30 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1f05f6e8-c60d-4104-9f1f-aafdf941e34fBj&#248;rn Kvaale<p>What about using the access_model_publish_ttl_set() function declared in access_config.h &amp; defined in access.c?</p><div style="clear:both;"></div>