Encountered these while trying out Light Switch proxy example in Mesh SDK

[Sivaguru Ravi]

I am using the proxy server and the proxy client example

1. Initially Proxy Client and Proxy Server are present in MESH network. Once the Proxy Client recycle the power (power off and on), it’s not able to join back to the same network until the Provisioner is reset by clearing all the states.
2. Initially Proxy Client and Proxy server are in MESH network.  When 3^rd party BLE mobile application (using GATT barrier) is trying to connect to Proxy  Client/Server which leads the Client/Server to malfunction and got disconnected from the MESH network. Error info (<t: 5840504>, app_error_weak.c,   95, Mesh assert at 0x0002DB3E (:0))

[David Edwin]

I am assuming that you are using the Mesh SDK v2.0.1 

Regarding 1. , is the node going back to unprovisioned state after a reset ? get a sniffer trace of the advertising being seen after a power cycle may be helpful.

Regarding 2. Is the proxy client getting the assert or the proxy server ? again get a sniffer trace on the connection and a complete log on the RTT.

[Sivaguru Ravi]

Hi David,

Sorry for the late response and thank you for the reply.

1.

Client Case:

         Yes it is going back to unprovisioned  state after reset. And we were able to see the advertisement packet of the client but the provisioner was not able to re-provision/re-include the client back in to the mesh until the Provisioner is reset by clearing all the states.

Server Case:

Yes it is going back to unprovisioned  state after reset. And we were able to see the advertisement packet of the client but the provisioner was not able to reprovision/re-include the client back in to the mesh until the server was reset by clearing all the states, which wen done gets provisioned by the provisioner as a new server with a different id than the previous one.

2.

Both client and the server are getting assert when trying to connect via 3^rd party BLE mobile application.

Thnk you

Sivaguru Ravi

[FormerMember]

1. In the Proxy Client example, storing to flash is by default disabled ("PERSISTENT_STORAGE = 0" in preprocessor symbols). To enable flash storing, change it to '1':

 

 

2. What you are seeing is a bug in the client/server proxy example. Please have a look at this thread for a workaround.

[FormerMember]

I have updated the answer.