I have starting working with UART. I see that there are two options for configuring it: UART_0_ASYNC and UART_0_INTERRUPT_DRIVEN. I want to use ASYNC option for my UART, but when I enable this option, the device is unable to be provisioned anymore. It means if I just enable this configuration in the chat example, it breaks the application for provision.
I also tried to initialize the UART only when the device is provisioned, but it has no effect.
Hi Ashish!
Have you tried doing it using a prj.conf configuration?
I also tried to initialize the UART only when the device is provisioned, but it has no effect.
Could you expand a bit on this? Are you provisioning the device and then re-flashing it?
Best regards,
Elfving
Hi Elfving
Yes, I tried with the prj.conf also by adding following
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_0_INTERRUPT_DRIVEN=n
CONFIG_UART_0_ASYNC=y
Simple explanation is just by adding the above code in prj.conf or enabling the UART from nrf configure tool, the application is disabled for Mesh provisioning.
The issue is somewhere with UART_0_ASYNC because if you configure prj.conf with following, it is okay:
CONFIG_UART_ASYNC_API=y
CONFIG_SERIAL=y
CONFIG_UART_0_INTERRUPT_DRIVEN=y
I use chat example in nrf Connect SDK v1.7.1.
I am not provisioning and then reflashing but everytime I erase all to check the sanity.
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
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
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.
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
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)
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)
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
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?
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
