The configuration client does not receive confirmation for a message with opcode 0x03

[Dmitro Balo]

Mesh SDK 5.0, SoftDevice S140 v7.2.0, NRF52840, SEGGER
------------------------------------------------------------------------------------
Hello! I have a similar problem. However, it manifests itself under other conditions. I have a node that has a configuration client and a configuration server at the same time, and it is convenient for me to use the configuration client to configure other models on the same device. All the functionality of the configuration client works well, I send messages to the server, the configuration happens and I get a status message back, but not a message about setting the publish address. I found out that the message with the 0x03 opcode is successfully received by the server, processed and it sends a response (send replay). But the access layer does not receive this status message and, accordingly, I receive a callback on the timeout event. Please help solve this problem! Thank you!

[Dmitro Balo]

It looks like the 0x8019 response is not being sent and the problem is here (transport.c):

But I don't know how to solve it. 

[Edvin]

Hi,

Sorry for the late reply. I discussed this with our Mesh team, and it is actually a known limitation in the nRF5 SDK for mesh implementation. Please see bullet point number 2 here:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v5.0.0%2Fmd_RELEASE_NOTES.html&anchor=release_notes_500_limitations

So you should try moving the configuration client over to the next element (and keep the configuration server on the primary element).

Try that, and let me know if it doesn't work.

Best regards,

Edvin

[Dmitro Balo]

Thanks Edvin. I did everything as you advised and now everything works fine. However, I'm a little concerned that, despite the existence of such a problem, the indexes of elements during initialization of the client and server are set by hardcode.

[Edvin]

Hello,

Can you please explain what you mean by "indexes of elements during initialization of the client and server are set by hardcode"?

Best regards,

Edvin

[Dmitro Balo]

Hello,

I meant this (config_client.c):

and this (config_server.c):

[Edvin]

I understand. Well, unfortunately, this is a  limitation in our nRF5 SDK Mesh stack, that tese needs to be on different elements. How you want to implement it is up to you (I wouldn't say that this is more "hardcoded" than setting both to 0, but perhaps I misunderstand. 

I am sorry if that is an inconvenience, but this will most likely not be changed, as the nRF5 SDK is in maintenance mode. In the new nRF Connect SDK (NCS), this is no longer a limitation.

Best regards,

Edvin