Unable to provision by configuring asynchronous UART

RE: Unable to provision by configuring asynchronous UART

Elfving — Tue, 22 Feb 2022 14:00:56 GMT

Hello Ashish,

Well the app is mainly made with developers in mind, so its understandable if it isnt the perfect fit for your use case. However, there is nothing wrong with creating your own app using our mesh libraries for Android and iOS, to automate that process in the same way our provisioner example does.

When it comes to configuration there are some things that the unit could come equipped with from the factory, while there might be other things that could depend on the network and what role in the network the unit has. Ie. with switches and lights you would most often configure them considering they're in the same room, and to make them publish and subscribe to the room group, respectively.

So in a way this all depends on your use-case. One would often want to maintain and make changes to the network at a later point, which would make using an embedded unit a worse choice and the smart phone, along with its ease of use a better option. But I guess it might be that you would want all of your units configured the same way, and have zero concerns about unauthorized units taking advantage of this.

Instead of simply telling you not to use an embedded device for this I should rather say that Mesh is not designed with that case in mind.

Regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Mon, 21 Feb 2022 18:35:04 GMT

Hi Elfving,

I do understand the static configuration might not be a secure way. But then I want to know what will you suggest when we need to deploy few hundred of devices in a network. Should we use pre-provisioned device using app or a fixed embedded device?

RE: Unable to provision by configuring asynchronous UART

Elfving — Mon, 21 Feb 2022 15:49:13 GMT

Hey Ashish,

The thing with provisioning examples is that we do not want to encourage you to make use an embedded device for it, due to its importance. If you take a look at the documentation for the Provisioner in the nRF5 SDK for Mesh it says: "The provisoner example is the default Bluetooth mesh network configurator. It works in a fixed, predefined way and can be used as the static provisioner with the following examples". The example is there for you to avoid spending a lot of time configuring just to try a few examples. However, it is not meant to be used in production, and is not very scalable.

I believe that is why we haven't included one in NCS. Though I do see how you could use one in this example.

Regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Thu, 17 Feb 2022 08:14:20 GMT

Thanks Elfving,

Yes, I am able to manually configure the device after the reboot. I also checked if it is fixed in the latest release 3.1.7 and its not.

So, I am also wondering if we have provisioner example for nrf connect sdk so that I can use that to provision rather depending on the mobile application? (in nrf mesh sdk I see one example)

RE: Unable to provision by configuring asynchronous UART

Elfving — Thu, 10 Feb 2022 09:48:54 GMT

Hey again,

This seems to be an issue that occurs on Android when a device is unable to send Device Composition Data Status message to the Android app. We believed this should be fixed in the most recent version of the app but it apparently is not. One workaround is to reboot the device and connect to it again using Android app, and carry out configuration manually (for example adding app keys).

We are looking into it, but at least there should be one solution available to you already.

Regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Thu, 03 Feb 2022 10:26:54 GMT

Hi Elfving,

I think when you have only Async line enabled, it is not configuring the UART properly. Therefore, I also use the GUI in segger "Configure nRF Connect SDK project".

And yes, without enabling async and with interrupt based, it works without any issue.

The mobile app version is 3.1.6.

RE: Unable to provision by configuring asynchronous UART

Elfving — Thu, 03 Feb 2022 09:58:13 GMT

But with only the ASYNC line enabled it still works for you I assume then?

What about only having the "CONFIG_UART_0_INTERRUPT_DRIVEN=n" line enabled?

And what app version are you using btw?

Regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Wed, 02 Feb 2022 09:32:17 GMT

I debug a bit, it seems that the error happens in bt_mesh_model_foreach() of v1.7.1\zephyr\subsys\bluetooth\mesh\access.c

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Tue, 01 Feb 2022 15:36:45 GMT

Hi Elfving,

Yes, I still see issue in the project you added if we enable all the four lines in prj.conf

CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_0_INTERRUPT_DRIVEN=n
CONFIG_UART_0_ASYNC=y

RE: Unable to provision by configuring asynchronous UART

Elfving — Tue, 01 Feb 2022 15:25:47 GMT

Hi Ashish,

Yeah, I think I am running into the issue you are describing now. It doesn't show on iPhones, which is what I tried it on earlier. I am looking into it.

Btw, are you getting the same issue in this project here?devzone.nordicsemi.com/.../chat.7z

Regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Tue, 01 Feb 2022 10:46:26 GMT

Hi Elfving

Do you able to reproduce the issue?

Regards,

Ashish

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Wed, 26 Jan 2022 15:54:01 GMT

Hi Elfving,

That is weird that it is working for you, do not you receive the "initial configuration failed"?
I am using Android and tried on Samsung A31 and One plus Nord2.

Regards,

Ashish

RE: Unable to provision by configuring asynchronous UART

Elfving — Wed, 26 Jan 2022 15:36:46 GMT

Hey Ashish,

Sorry about that, I forgot that you had already sent me those. I only tried to provision the standard projects before (along with your configurations). But I have now also tried to provision your entire project just in case, and that also does work for me.

What type of phone do you have? Have you tried it with another one?

Regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Tue, 25 Jan 2022 10:42:21 GMT

Hi Elfving,

What exactly you need apart from already sent projects ("chat-not-working.zip", "chat-working_fine.zip")? Can you please expand?

Regards,

Ashish

RE: Unable to provision by configuring asynchronous UART

Elfving — Tue, 25 Jan 2022 10:16:00 GMT

Hello again,

Could you send me your project along with the troublesome configurations?

Best regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Fri, 21 Jan 2022 12:51:27 GMT

Hi,

No, that is the only issue I found in the chat example. Normally, I am using the mesh examples, and I tried light_switch, and sensor_client; they are working fine.

RE: Unable to provision by configuring asynchronous UART

Elfving — Wed, 19 Jan 2022 12:06:19 GMT

I see.

And there is nothing else with the behavior that is failing/ strange? Besides not being provisioned, everything works? Is there for instance any issue incorporating the blinky example into the project, and get that working?

Best regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Fri, 14 Jan 2022 08:48:18 GMT

Hi Elfving,

I enable few logs and the failure happens like this:

And when it is successful, the logs are like this:

RE: Unable to provision by configuring asynchronous UART

Elfving — Fri, 14 Jan 2022 07:50:15 GMT

[quote user="Ashishsult"]May be you can try to provision the device (nrf52832) with the changes in prj.conf as mentioned before and see if you are able to do so. I already posted the code as well before.[/quote]

Yeah, I am not able to reproduce this. It does work for me.

[quote user="Ashishsult"]Because even if there is nothing provisioned already, we have the same issue.
[/quote]

That is interesting. I agree that it would be odd if what was already provisioned would cause this error, but I thought that was the only difference between your situation in which it doesn't work, and mine in which it does.

Could you expand a bit on in what way you see provisioning failing? And is there anything else with the behavior of the example that is failing/strange?

Best regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Thu, 13 Jan 2022 10:38:03 GMT

I wanted to have three nodes: 1. With UART as client, 2. Without UART as Relay and 3. Without UART as Server.

But I don't understand how this issue of provisioning a device linked with it.
Because even if there is nothing provisioned already, we have the same issue.

May be you can try to provision the device (nrf52832) with the changes in prj.conf as mentioned before and see if you are able to do so. I already posted the code as well before.

RE: Unable to provision by configuring asynchronous UART

Elfving — Thu, 13 Jan 2022 10:29:46 GMT

What other nodes are on the network? And how many?

Best regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Thu, 13 Jan 2022 10:20:20 GMT

Yes, I add these lines in the prj.conf file, run CMake and then build. I connect, erase device and flash it to the device using Segger.

Next, I use Mobile nRF Mesh App v3.1.6 to provision the device (which fails).

Other nodes in my use case doesn't have the UART so are successfully provisioned.

RE: Unable to provision by configuring asynchronous UART

Elfving — Thu, 13 Jan 2022 10:14:58 GMT

Are these the configurations you added when you attempted to provision?

[quote user="Ashishsult"]

CONFIG_SERIAL=y

CONFIG_UART_ASYNC_API=y

CONFIG_UART_0_INTERRUPT_DRIVEN=n

CONFIG_UART_0_ASYNC=y

[/quote]

And did you provision using the nRF Mesh app? Where any other nodes provisioned as well?

Best regards,

Elfving

RE: Unable to provision by configuring asynchronous UART

Ashishsult — Thu, 13 Jan 2022 10:13:01 GMT

Hi Elving, yes, I tried with unmodified example in two SDK versions 1.71. and 1.6.1. And both of them shows issue during provisioning.

RE: Unable to provision by configuring asynchronous UART

Elfving — Thu, 13 Jan 2022 10:04:11 GMT

I see.

And that is with a completely unmodified example as well?

Might be that when you open the chat example you open it along with a series of other modifications as well, that are the actual cause of the problem. To make sure the example you use isn't modified as well as keeping the projects you have in this version of the SDK, you could try and install another version of NCS and see if the issue occurs in that version of the chat example as well.

Best regards,

Elfving