Getting a MESH ASSERT on 'subscription delete all'

RE: Getting a MESH ASSERT on 'subscription delete all'

tesc — Fri, 04 Sep 2020 14:44:50 GMT

Hi,

The mesh team has not been able to reproduce.

It would be the best if our setup is as close to yours as possible, for reproducing.

What example (or examples) did you test?
Did you only provision, or did you do some configuration as well?
What device or app did you use for provisioning (and for configuration, if applicable)?
We assume that you send CONFIG_OPCODE_MODEL_SUBSCRIPTION_DELETE_ALL from the provisioner. With what parameters? (And if you do something else, please elaborate on how you trigger the delete.)

Regards,
Terje

RE: Getting a MESH ASSERT on 'subscription delete all'

Heidi — Tue, 28 Jul 2020 13:00:51 GMT

Hi,

Unfortunately, I have no updates yet. The mesh-team will take a look as soon as possible and try to fix it when they confirm it's a real bug.

Due to the holidays in Norway, we are very low on staff in every department so delays are to be expected during the next few weeks.

Best regards,

Heidi

RE: Getting a MESH ASSERT on 'subscription delete all'

benjamin — Tue, 21 Jul 2020 08:57:31 GMT

Any news about this ?

Thank you

Best regards

Ben

RE: Getting a MESH ASSERT on 'subscription delete all'

benjamin — Thu, 09 Jul 2020 14:01:17 GMT

Hi!

thank you for your explainations.

As I said, the easiest way is to erase compeletly the flash, program any mesh example, provision it and send the command.

Thank you

RE: Getting a MESH ASSERT on 'subscription delete all'

tesc — Thu, 09 Jul 2020 12:00:43 GMT

Hi,

I suspect there may be a discrepancy between the states of the access layer and the device state manager. In this part of code, the number of subscriptions are checked using access layer functions, and then used for determining how many entries to delete from DSM. If access and DSM is out of sync at this point, then that could explain this error. If that is the case then I do not see any immediate way to fix this for an application, as it must be fixed in the mesh stack code itself.

I will report the issue to our developers, so they can look into it and hopefully reproduce and suggest a fix. Do you have a project running on an nRF DK or Dongle, where this issue can be easily reproduced?

Regards,
Terje

RE: Getting a MESH ASSERT on 'subscription delete all'

benjamin — Mon, 06 Jul 2020 15:10:54 GMT

Hi, sorry for the late answer

here you have it

Best regards

RE: Getting a MESH ASSERT on 'subscription delete all'

Hung Bui — Wed, 01 Jul 2020 12:27:26 GMT

Hi Benjamin,

Could you let me know what you did before you called the function to erase all subscriptions ? Have you assigned a subscription address to any model ?

It seems that the address has no subscription and then it end up in NRF_ERROR_NOT_FOUND.

I'm curious about subscription_count and the subscribed_addresses[] array you have.