RE: iOS NRF Mesh app will only provision and configure one device

Aleksander Nowakowski — Thu, 08 Apr 2021 13:19:48 GMT

There may be a lot of reasons why this happens:

- The node you're connected to has GATT Proxy turned off (this is by default enabled, so you'd have to turn it off)
- The new node is not reachable (also not likely, as you just provisioned it. Check if you can connect to it using the Proxy tab -> disable automatic connection -> connect to it -> repeat sending ConfigCompositionGet)
- Your ConfigCompositionGet is sent in 2 packets:

2021-04-07 14:21:34.336394-0600 nRFMeshProvision_Example[47763:5316610] [Bearer] -> 0x406F48E99DBFF7613B20FB5FFD35C68E27F1561C

2021-04-07 14:21:34.352579-0600 nRFMeshProvision_Example[47763:5305094] [Bearer] -> 0xC0768B

which means, you have MTU = 23. What mesh implementation on the devices are you using? It doesn't look like nRF Mesh SDK or mesh projects from nRF Connect SDK, as as far as I know, they have MTU set to 200+. That is not a problem, MTU = 23 should also work, but if you have a different mesh impl, perhaps there are issues with it. Try connecting directly to the new provisioned node, like I wrote in the 2nd bullet.