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?

[kolten]

Here you go!, built for nrf52840.    blemesh_models_example_2.hex

[Roshan Rajaratnam]

Hi Kolten. thanks for this, however I'm unable to get the device advertising. is there anything else I need to do get this up and running?

[kolten]

mynewt.hex

Here is a bootloader, I tested to program a board with nrf-Connect 3.2.0, I used this bootloader and the above application.

[kolten]

Hi, have you had any success testing the problem that we have seen?

[Roshan Rajaratnam]

Hi @kolten, sorry for the delayed reply. I did give this a go. Looking at the logs I see a slight issue here. Everytime when we send the first CompositionDataGet message, the very first segment is not sent by the firmware side (what's received is from the 1st to 5th), but the second time we send a CompositionDataGet it sends all the packets(from 0th segment to the 5th). I will also debug more on my end to see why the 0th segment is not resent.