Failed getting composition data after app update to 2.1.0

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Tue, 19 Nov 2019 08:33:12 GMT

Great, if possible please mark the answer as accepted so we can close the ticket. Thanks

RE: Failed getting composition data after app update to 2.1.0

kolten — Mon, 18 Nov 2019 13:04:07 GMT

Seams like the fix did it, thx for the support!

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Mon, 18 Nov 2019 08:39:41 GMT

I have uploaded a newer version to the play store and it should up in a couple of hours. In the mean time you can find the latest apk on Github as well. Thanks for reporting this issue and for helping us with the provided fws. Hope this fixes your issue. Let us know if I can be of more help.

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Mon, 18 Nov 2019 08:10:53 GMT

I can confirm the issue is on our end, this was indeed based on a fix madee for an issue related to sequence number validation.

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Mon, 18 Nov 2019 06:37:28 GMT

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.

RE: Failed getting composition data after app update to 2.1.0

kolten — Wed, 13 Nov 2019 07:59:06 GMT

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

RE: Failed getting composition data after app update to 2.1.0

kolten — Fri, 08 Nov 2019 09:19:17 GMT

devzone.nordicsemi.com/.../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.

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Fri, 08 Nov 2019 08:26:31 GMT

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?

RE: Failed getting composition data after app update to 2.1.0

kolten — Wed, 06 Nov 2019 18:38:46 GMT

Here you go!, built for nrf52840. devzone.nordicsemi.com/.../blemesh_5F00_models_5F00_example_5F00_2.hex

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Wed, 06 Nov 2019 13:13:36 GMT

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.

RE: Failed getting composition data after app update to 2.1.0

kolten — Wed, 06 Nov 2019 12:36:55 GMT

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

RE: Failed getting composition data after app update to 2.1.0

Hung Bui — Wed, 06 Nov 2019 12:29:35 GMT

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 ?

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Wed, 06 Nov 2019 12:23:39 GMT

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.

RE: Failed getting composition data after app update to 2.1.0

kolten — Tue, 05 Nov 2019 15:21:02 GMT

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?

RE: Failed getting composition data after app update to 2.1.0

Roshan Rajaratnam — Tue, 05 Nov 2019 09:52:32 GMT

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.

RE: Failed getting composition data after app update to 2.1.0

kolten — Tue, 05 Nov 2019 08:37:21 GMT

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?

RE: Failed getting composition data after app update to 2.1.0

torstenbofink — Tue, 05 Nov 2019 08:19:29 GMT

My collegues know more than me about this and will help you with the details...

RE: Failed getting composition data after app update to 2.1.0

kolten — Tue, 05 Nov 2019 08:04:00 GMT

The device do act as an proxy node after the failure, you can connect to it and request for the composition data and you get the data as expected. One thing that does not behave as before is that the "application key" is not set automatically, you have to assign it manually and after this you can configure the device as expected.

RE: Failed getting composition data after app update to 2.1.0

Hung Bui — Mon, 04 Nov 2019 14:42:18 GMT

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 ?