light example often fail to read on-off statehttps://devzone.nordicsemi.com/f/nordic-q-a/42887/light-example-often-fail-to-read-on-off-stateI am playing the light switch example with nRF mesh app. I am using nRF Mesh app read the light server state. and find out the app is really easy to hang when the device is not ack back the data. The client has &quot;send_reliable_message()&quot; to make sureen-USTelligent Community 13Fri, 25 Jan 2019 14:52:09 GMTRE: light example often fail to read on-off statehttps://devzone.nordicsemi.com/thread/167983?ContentTypeID=1Fri, 25 Jan 2019 14:52:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c997d035-eb84-442b-a448-1f0563acd5a8Roshan Rajaratnam<p>@arikyang, Really sorry about this issue. This was a bug introduced in the version 1.1.0. The transaction ids/delay values have been incorrectly passed causing this issue. This will be fixed in the upcoming version.</p><div style="clear:both;"></div>RE: light example often fail to read on-off statehttps://devzone.nordicsemi.com/thread/167529?ContentTypeID=1Thu, 24 Jan 2019 06:20:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fb1cb2f5-fed1-4bbd-a936-6c67bc42b280arikyang<p>Note: My 2.4G environment is crowded. More than 10 BLE devices working.</p> <p>I just figure out that the&nbsp;issue happens only when the server subscribes&nbsp;a group.</p> <p>Also, it shows a &quot;Rem. Time:xxx s&quot; text next to the button of &quot;READ STATE&quot;.</p> <p>I set transition time and delay to 0 ms, why do we have this Rem. time?</p><div style="clear:both;"></div>