light example often fail to read on-off state

[arikyang]

I 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 "send_reliable_message()" to make sure the data ack, but how about the command from proxy.c?

How can I handle it that App will not wait forever?

Thanks,

Proxy log:

0> <t: 8535724>, proxy.c, 611, RX
0> <t: 8535730>, proxy.c, 553, RX GATT PDU type 0x0, len 20
0> <t: 8551921>, proxy.c, 619, TX complete
0> <t: 8738472>, proxy.c, 611, RX
0> <t: 8738478>, proxy.c, 553, RX GATT PDU type 0x0, len 20

Server log:

0> <t: 6177701>, app_onoff.c, 170, msg: GET
0> <t: 6380449>, app_onoff.c, 170, msg: GET

SDK:

nrf5SDKforMeshv310src

HW:
52DK *2

[arikyang]

Note: My 2.4G environment is crowded. More than 10 BLE devices working.

I just figure out that the issue happens only when the server subscribes a group.

Also, it shows a "Rem. Time:xxx s" text next to the button of "READ STATE".

I set transition time and delay to 0 ms, why do we have this Rem. time?

[Roshan Rajaratnam]

@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.