<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mesh Provisioning: how to streamline provisioning of many identical nodes.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/107513/mesh-provisioning-how-to-streamline-provisioning-of-many-identical-nodes</link><description>We are developing a mesh lighting application. 
 We have hundreds of identical nodes. 
 Currently we are provisioning them manually using the nRF Mesh App: this is of course the basic option, but we believe that this approach can be useful for initial</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Jan 2024 14:22:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/107513/mesh-provisioning-how-to-streamline-provisioning-of-many-identical-nodes" /><item><title>RE: Mesh Provisioning: how to streamline provisioning of many identical nodes.</title><link>https://devzone.nordicsemi.com/thread/465366?ContentTypeID=1</link><pubDate>Mon, 22 Jan 2024 14:22:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:deb2cb79-6c42-4aee-bd86-1bdde360aad3</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Davide,&lt;/p&gt;
&lt;p&gt;I am sorry, but I am not aware of any such plans. I talked to our Bluetooth Mesh team, and they said the following:&lt;/p&gt;
&lt;p&gt;Seems like Remote Provisioning is what should help to satisfy the customer requirements. Talking about remote interface, aka PyACI in the nRF5 SDK. The customer can use this if it is not a requirement that the devvice needs to be a Zephyr based solution. They can use Linux solution based on Zephyr API (mesh, host). They can locate the controller on device and HOST+Mesh on PC communicating over serial interface that HCI implementation supports (for example UART). This is Bluetooth architecture in Zephyr (with description of Host-only and Controller-only, meaning:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.zephyrproject.org/latest/connectivity/bluetooth/bluetooth-arch.html#bluetooth-build-types"&gt;https://docs.zephyrproject.org/latest/connectivity/bluetooth/bluetooth-arch.html#bluetooth-build-types&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is how to use QEMU or native POSIX host with controller:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.zephyrproject.org/latest/connectivity/bluetooth/bluetooth-tools.html#bluetooth-qemu-native"&gt;https://docs.zephyrproject.org/latest/connectivity/bluetooth/bluetooth-tools.html#bluetooth-qemu-native&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;An alternative, according to the Bluetooth Mesh team can also be to modify the mesh_shell with e.g. UART to funnel messages to/from a pc. This has&amp;nbsp; been done on several occasions, but mostly for demo cases. Mesh shell is not streamlined for the described use case, so I am not sure it is suitable for production.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Provisioning: how to streamline provisioning of many identical nodes.</title><link>https://devzone.nordicsemi.com/thread/465096?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 15:11:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96df781e-051c-4e82-87e7-8f1aeb97389e</guid><dc:creator>DavideDN</dc:creator><description>&lt;p&gt;thank you for the hint Edvin.&lt;/p&gt;
&lt;p&gt;Can you tell me if there are plans to expose an interface more suitable to be used programmatically as an regular API?&lt;/p&gt;
&lt;p&gt;Moreover, what is the approach you are suggesting to any company that is going to build a Mesh gateway? I believe that there should be a lot of customers of yours with this kind of need.&lt;/p&gt;
&lt;p&gt;br&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Davide&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Provisioning: how to streamline provisioning of many identical nodes.</title><link>https://devzone.nordicsemi.com/thread/465090?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 14:59:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a72b013c-a691-48d2-a12e-889c650b51f3</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello.&lt;/p&gt;
&lt;p&gt;There is a shell sample, found in &amp;lt;sdk_folder&amp;gt;\zephyr\tests\bluetooth\mesh_shell, which you can use for provisioning. Check the &lt;a href="https://docs.zephyrproject.org/latest/connectivity/bluetooth/api/mesh/shell.html"&gt;sample&amp;#39;s description here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Note that this is using serialization, which is intended for human interface, and not scripting. This means that the throughput is not great, so keep that in mind if you intend to use this for scripting. Add sufficient delays.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>