https://devzone.nordicsemi.com/f/nordic-q-a/33474/general-purpose-provisionerHi, I found out, that in the light switch example (SDK for Mesh v.1.0.1) after adding second element with Simple OnOff model in the light_switch_server, it is not possible to provision that second element. After searching in DevZone, I found out, thaten-USTelligent Community 13Wed, 18 Apr 2018 06:11:01 GMThttps://devzone.nordicsemi.com/thread/128718?ContentTypeID=1Wed, 18 Apr 2018 06:11:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f9d019aa-305e-4d36-9e45-86aa0579bd43David Edwin<p>Why would you want to bind to the AppKey ? The configuration client is configuring individual nodes so it would use the devkey of the node that is being configured.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/128662?ContentTypeID=1Tue, 17 Apr 2018 14:52:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:01515bee-414c-4dce-9875-6f3e70f94cfcPatrik<p>One more question. Can be the Configuration Client Model bound with the AppKey? If yes, which function to use? Because in the light switch example if I&#39;m right, it is bound just with the DevKey.&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/128591?ContentTypeID=1Tue, 17 Apr 2018 09:10:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a451bd9c-26ab-4eda-b51f-fdc88ad33e82David Edwin<p>Use the pyACI python interface to run the provisioning and configuration. This would allow to to understand things better by running it from the command line.</p> <p>Switch to the next release of the Mesh SDK (after 1.0.1) when it gets released as the pyACI has a bit more features in the configuration stage.</p> <p>(1) is generally true.</p> <p>(2) Typically a single device key is obtained during provisioning, the device key is per device. Configuration support is better on the pyACI in the newer release that comes after 1.0.1 Mesh SDK.</p> <p>&nbsp;</p> <p>&nbsp;</p><div style="clear:both;"></div>