Please refer to the link below. How can I configure the Commission Flow according to the requirements?
Please refer to the link below. How can I configure the Commission Flow according to the requirements?
Hi,
Please take a look at the fllowng:
https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/matter/overview/commissioning.html
Hope this helps.
-Priyanka
Hi
What I mean is the configuration, which could be factory data or the prj.conf
settings.
As shown in the image below
0:Standard, 1:User-Intent, 2:Custom.
Hi,
I am checking this internally and will get back to you soon.
-Priyanka
Hi,
What I understood from your query is, how to change the Commissioning Flow bits in the BLE advertisement using either prj.conf or Factory Data configuration? ope this is correct.
The Commissioning Flow is not defined by the FW but by QR code and DCL entry. The Custom Flow bits are only part of QR code. When manual pairing code is used, then Custom Flow bits are not present there, but instead Matter Controller can look at VID and PID of the device, and then check if Custom Commissioning Flow is necessary by checking the DCL entry of the given device.
Based on above, there is no KConfig or Factory Data entry for Custom Flow bits.
There is one place in the code where this Custom Flow can be modified in the code, and this is only for debugging purpose to change printed QR code in the console:
Here you may change it - but it does not have any impact on the device behaviour - it's just helper string in debug logs.
-Priyanka
Hi,
What I understood from your query is, how to change the Commissioning Flow bits in the BLE advertisement using either prj.conf or Factory Data configuration? ope this is correct.
The Commissioning Flow is not defined by the FW but by QR code and DCL entry. The Custom Flow bits are only part of QR code. When manual pairing code is used, then Custom Flow bits are not present there, but instead Matter Controller can look at VID and PID of the device, and then check if Custom Commissioning Flow is necessary by checking the DCL entry of the given device.
Based on above, there is no KConfig or Factory Data entry for Custom Flow bits.
There is one place in the code where this Custom Flow can be modified in the code, and this is only for debugging purpose to change printed QR code in the console:
Here you may change it - but it does not have any impact on the device behaviour - it's just helper string in debug logs.
-Priyanka