Failed getting composition data after app update to 2.1.0

[torstenbofink]

Hi,

We are using nrf52 dev boards running mynewt and until two days ago we could use the app to identify/provision and get composition data for nodes and get composition data from them. After the update to version 2.1.0 of the android app, it hangs while obtaining composition data, see attached screenshot.

The release notes say something about fixing problems related to composition data. Maybe something was fixed and a new problem introduced?

[Hung Bui]

Hi Torsten,

Could you give some more information on the firmware you are running on the nRF52 ? 

Could you capture a sniffer trace of the provisioning process ? 

After the issue happens, do you see the device advertising as a proxy node ? Can you do the configuration after that ? 

[kolten]

I'm looking at the output log and see that we get a request for the composition data, we get a request for page "255", which seams to cause the error. Why is it requesting for this page, should it not be 0?

[Roshan Rajaratnam]

Hi @kolten, Page 0 is the mandatory page that is to be implemented by the node, still a node could have multiple pages. This is the reason for having the page number set 255. Please refer Mesh Specification section 4.4.1.2.2, This should not affect unless you have modified anything on the Configuration Server (nRF Mesh SDK) as the current implementation works with the Mesh SDK. However there will be a better explanation to this in the upcoming specification 1.1.0

The fix made in 2.1.0 was something relating to acknowledgement timers which is totally unrelated to the Composition Data Page. You could verify this against an included sdk example.

Hope this answers your question.

[kolten]

You said something about acknowledgement timers, this is exactly what the picture above shows, we send the composition data and then get an acknowledge message. We reply to this but something is off with the timing, in your end or our?

[Roshan Rajaratnam]

Hi Kolten, is there any chance you could share your hex file with us? Based on the Mesh SDK examples it seems to be working fine on our end.

[Hung Bui]

FYI: You can convert the case to private case to if you don't want the hex file to be shared publicly . 
I assume you don't have an issue when provisioning the stock example (light switch for example) in the SDK  ? 

[kolten]

The application is a standard Mynewt ble mesh application, blemesh_models_example_2.

[Roshan Rajaratnam]

We would really appreciate if you could provide the specific example to avoid any confusions and we can run a test for you to see if the app behaves any different.