[BUG] Unable to commission into new fabric using chip-tool api

[pmatsibekker]

[BUG] Unable to commission into new fabric using chip-tool api

[bzbarsky-apple]

I tried using the chip-tool api to connect
./chip-tool pairing code 1 21104754926

Where did that code come from? Is that the one the Android app provided?

./chip-tool payload discover commissionables also fails.

There is no "payload discover" command in chip-tool...

What is avahi, if you have it installed, showing you about the commissionable advertisement in question?

[pmatsibekker]

Thank you for your response! Where did that code come from? Is that the one the Android app provided? Yes, thats from android app I built chip-tool from the connected homepage master branch on my windows Ubuntu distribution. Everything builds fine and the executable can be run. I only use my android to first commission the outlet matter enabled vendor device and I would like to control it out of the new Ubuntu commissioned fabric. I dont think I have avahi installed. I can try to get it if you think that it will provide information. I would think the Use Case should work between the ubuntu chip-tool and the android fabric. Not sure why it should have difficulty with it. Is there a pre-built chip-tool for amd x64 in case something went wrong in the dependency chain?

…

On Mon, Mar 25, 2024, 3:24 PM Boris Zbarsky ***@***.***> wrote: I tried using the chip-tool api to connect ./chip-tool pairing code 1 21104754926 Where did that code come from? Is that the one the Android app provided? ./chip-tool payload discover commissionables also fails. There is no "payload discover" command in chip-tool... What is avahi, if you have it installed, showing you about the commissionable advertisement in question? — Reply to this email directly, view it on GitHub <#32706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5XK6QCMDJMFM2Q35E4FVTDY2B2XZAVCNFSM6AAAAABFHSUJR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG42DMMBVGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pmatsibekker]

Copied the wrong command.. it was ./chip-tool discover commissionables

…

On Mon, Mar 25, 2024, 3:24 PM Boris Zbarsky ***@***.***> wrote: I tried using the chip-tool api to connect ./chip-tool pairing code 1 21104754926 Where did that code come from? Is that the one the Android app provided? ./chip-tool payload discover commissionables also fails. There is no "payload discover" command in chip-tool... What is avahi, if you have it installed, showing you about the commissionable advertisement in question? — Reply to this email directly, view it on GitHub <#32706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5XK6QCMDJMFM2Q35E4FVTDY2B2XZAVCNFSM6AAAAABFHSUJR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG42DMMBVGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bzbarsky-apple]

chip-tool discover commissionables should generally work. So if that's not working, then chances are either a commissioning window is not being opened, or the device that is commissionable and chip-tool are not on the same network, or something on that network is messing with dns-sd.

avahi could be a way to at least cross-check that the issue is not with chip-tool itself, just in case.

[pmatsibekker]

Hi Boris, Thank you so much for trying to help me here. I ran avahi_browser on the _matterd._udp.local and I see it getting triggered when i try to do a pairing. I found that running $chip-tool interactive start got me further in the discovery process but still not working. $ pairing code 0x1 26058243772 [1711490840.968705][3123:3123] CHIP:TOO: Command: pairing code 0x1 26058243772 [1711490840.969214][3123:3125] CHIP:CTL: Setting attestation nonce to random value [1711490840.969272][3123:3125] CHIP:CTL: Setting CSR nonce to random value [1711490840.970726][3123:3125] CHIP:CTL: Generating NOC [1711490840.971142][3123:3125] CHIP:FP: Validating NOC chain [1711490840.971615][3123:3125] CHIP:FP: NOC chain validation successful [1711490840.971684][3123:3125] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669 [1711490840.971713][3123:3125] CHIP:TS: Last Known Good Time: 2023-10-14T01:16:48 [1711490840.971716][3123:3125] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00 [1711490840.971720][3123:3125] CHIP:TS: Retaining current Last Known Good Time [1711490841.041703][3123:3125] CHIP:FP: Metadata for Fabric 0x1 persisted to storage. [1711490841.066230][3123:3125] CHIP:TS: Committing Last Known Good Time to storage: 2023-10-14T01:16:48 [1711490841.068374][3123:3125] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: 24EA3F3A4B34EE0E) [1711490841.068413][3123:3125] CHIP:IN: UDP::Init bind&listen port=5550 [1711490841.068435][3123:3125] CHIP:IN: UDP::Init bound to port=5550 [1711490841.068439][3123:3125] CHIP:IN: UDP::Init bind&listen port=5550 [1711490841.068448][3123:3125] CHIP:IN: UDP::Init bound to port=5550 [1711490841.068450][3123:3125] CHIP:IN: TransportMgr initialized [1711490841.068503][3123:3125] CHIP:DIS: Updating services using commissioning mode 0 [1711490841.096093][3123:3125] CHIP:DIS: CHIP minimal mDNS started advertising. [1711490841.096654][3123:3125] CHIP:DL: Using wifi MAC for hostname [1711490841.096686][3123:3125] CHIP:DIS: Advertise operational node 24EA3F3A4B34EE0E-000000000001B669 [1711490841.096737][3123:3125] CHIP:DIS: Responding with _matter._tcp.local [1711490841.096765][3123:3125] CHIP:DIS: Responding with 24EA3F3A4B34EE0E-000000000001B669._matter._tcp.local [1711490841.096814][3123:3125] CHIP:DIS: Responding with 24EA3F3A4B34EE0E-000000000001B669._matter._tcp.local [1711490841.096818][3123:3125] CHIP:DIS: Responding with 00155D8988E20000.local [1711490841.096821][3123:3125] CHIP:DIS: Responding with 00155D8988E20000.local [1711490841.096825][3123:3125] CHIP:DIS: Responding with _I24EA3F3A4B34EE0E._sub._matter._tcp.local [1711490841.096827][3123:3125] CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: 24EA3F3A4B34EE0E-000000000001B669. [1711490841.097312][3123:3125] CHIP:DIS: mDNS service published: _matter._tcp [1711490841.097388][3123:3125] CHIP:DL: Using wifi MAC for hostname [1711490841.097422][3123:3125] CHIP:DIS: Advertise operational node 9F4224575B081A6B-000000000001B669 [1711490841.097461][3123:3125] CHIP:DIS: Responding with _matter._tcp.local [1711490841.097490][3123:3125] CHIP:DIS: Responding with 9F4224575B081A6B-000000000001B669._matter._tcp.local [1711490841.097513][3123:3125] CHIP:DIS: Responding with 9F4224575B081A6B-000000000001B669._matter._tcp.local [1711490841.097516][3123:3125] CHIP:DIS: Responding with 00155D8988E20000.local [1711490841.097519][3123:3125] CHIP:DIS: Responding with 00155D8988E20000.local [1711490841.097541][3123:3125] CHIP:DIS: Responding with _I9F4224575B081A6B._sub._matter._tcp.local [1711490841.097546][3123:3125] CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: 9F4224575B081A6B-000000000001B669. [1711490841.097933][3123:3125] CHIP:DIS: mDNS service published: _matter._tcp [1711490841.098020][3123:3125] CHIP:DL: Using wifi MAC for hostname [1711490841.098102][3123:3125] CHIP:DIS: Advertise commission parameter vendorID=65521 productID=32769 discriminator=0000/00 cm=0 cp=0 [1711490841.098166][3123:3125] CHIP:DIS: Responding with _matterd._udp.local [1711490841.098175][3123:3125] CHIP:DIS: Responding with 0E60B071FA8AA9C3._matterd._udp.local [1711490841.098179][3123:3125] CHIP:DIS: Responding with 00155D8988E20000.local [1711490841.098183][3123:3125] CHIP:DIS: Responding with 00155D8988E20000.local [1711490841.098211][3123:3125] CHIP:DIS: Responding with _V65521._sub._matterd._udp.local [1711490841.098219][3123:3125] CHIP:DIS: Responding with 0E60B071FA8AA9C3._matterd._udp.local [1711490841.098221][3123:3125] CHIP:DIS: CHIP minimal mDNS configured as 'Commissioner device'; instance name: 0E60B071FA8AA9C3. [1711490841.116752][3123:3125] CHIP:DIS: mDNS service published: _matterd._udp [1711490841.169609][3123:3125] CHIP:CTL: Setting attestation nonce to random value [1711490841.169647][3123:3125] CHIP:CTL: Setting CSR nonce to random value [1711490841.169653][3123:3125] CHIP:CTL: Checking ICD registration parameters [1711490841.169673][3123:3125] CHIP:CTL: Stopping commissioning discovery over DNS-SD [1711490841.169680][3123:3125] CHIP:CTL: Starting commissioning discovery over DNS-SD [1711490841.169809][3123:3125] CHIP:DL: Long dispatch time: 201 ms, for event type 2 [1711490871.171686][3123:3125] CHIP:CTL: Discovery timed out [1711490871.171727][3123:3125] CHIP:CTL: Stopping commissioning discovery over DNS-SD [1711490871.171736][3123:3125] CHIP:TOO: Secure Pairing Failed [1711490871.171743][3123:3125] CHIP:TOO: Run command failure: ../../examples/chip-tool/commands/pairing/PairingCommand.cpp:341: CHIP Error 0x00000003: Incorrect state i ran avahi-browser on _matterd._ud= $ avahi-browse _matterd._udp -r txt = ["VP=65521+32769"] + eth0 IPv6 0E60B071FA8AA9C3 _matterd._udp local = eth0 IPv6 0E60B071FA8AA9C3 _matterd._udp local hostname = [00155D8988E20000.local] address = [172.31---.--] port = [5550] txt = ["VP=65521+32769"]

…

On Tue, Mar 26, 2024 at 4:42 PM Boris Zbarsky ***@***.***> wrote: chip-tool discover commissionables should generally work. So if that's not working, then chances are either a commissioning window is not being opened, or the device that is commissionable and chip-tool are not on the same network, or something on that network is messing with dns-sd. avahi could be a way to at least cross-check that the issue is not with chip-tool itself, just in case. — Reply to this email directly, view it on GitHub <#32706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5XK6QEBDEYDE6ZHZQIQED3Y2HMTRAVCNFSM6AAAAABFHSUJR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGQZTCMZWGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pmatsibekker]

Ok, so I have it working now. Couple of things to note.

1. This does not work with WSL for me. It seems to need the full ubuntu install desktop install.
2. You need to --bypass-attestation-verifier=true to complete the commissioning.

Commissioning then complete successfully and I could see the new fabric linking on my android.
However, one concern was that the logging didn't provide me with the discriminator code that I could understand. I was able to successfully toggle a matter plug by using discriminator set to 1.
If you know how to distinguish it from the logs that would be very helpful going forward.

Otherwise, the controller does as advertised. Thank you!

[bzbarsky-apple]

You need to --bypass-attestation-verifier=true to complete the commissioning.

Probably because it's signed by a PAA that has not been imported into the SDK source tree yet.... I hope.

the logging didn't provide me with the discriminator code that I could understand. I was able to successfully toggle a matter plug by using discriminator set to 1.

I'm not sure what you mean @pmatsibekker. Discriminator is only used during commissioning, to narrow the set of things you might try to commission.

Where are you using the discriminator in any way? Normally you "use" it just by using the pairing code (which encodes the discriminator, or part of it in the case of the numeric code).

[pmatsibekker]

Hi, If I understand the api correctly, the controllers need the descriptor id to distinguish the individual devices on the fabric node once commissioned. I don't use the commissioning code after that. I assumed its the same as discriminator, and I chose '1' because it was the first item in the fabric node. But I couldn't find a unique identifier from the commissioning in the logs.

…

On Fri, Mar 29, 2024, 11:45 PM Boris Zbarsky ***@***.***> wrote: You need to --bypass-attestation-verifier=true to complete the commissioning. Probably because it's signed by a PAA that has not been imported into the SDK source tree yet.... I hope. the logging didn't provide me with the discriminator code that I could understand. I was able to successfully toggle a matter plug by using discriminator set to 1. I'm not sure what you mean @pmatsibekker <https://github.com/pmatsibekker>. Discriminator is only used during commissioning, to narrow the set of things you might try to commission. Where are you using the discriminator in any way? Normally you "use" it just by using the pairing code (which encodes the discriminator, or part of it in the case of the numeric code). — Reply to this email directly, view it on GitHub <#32706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5XK6QGSVQEY2S4TYXCUPY3Y2YYM3AVCNFSM6AAAAABFHSUJR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXHA4TSMRRGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bzbarsky-apple]

If I understand the api correctly, the controllers need the descriptor id to distinguish the individual devices on the fabric node once commissioned.

Once the device is commissioned, all you need is the node ID.

The node ID is assigned by the commissioner, and can be anything the commissioner wants, as long as it's unique within the commissioner's fabric. The commissioning command used above:

pairing code 0x1 26058243772

is using 0x1 as the node ID to assign to the commissionee. After that, you need to use the same node ID to sent it commands. You can use any other node ID you want here, as desired.... It's totally up to you, as the commissioner.

I'm not sure whether that actually answers your question/concern, though. If it doesn't, can you please clearly explain what problem you are trying to address here?

[pmatsibekker]

Yes, very helpful.

…

On Mon, Apr 1, 2024, 11:59 AM Boris Zbarsky ***@***.***> wrote: If I understand the api correctly, the controllers need the descriptor id to distinguish the individual devices on the fabric node once commissioned. Once the device is commissioned, all you need is the node ID. The node ID is assigned by the commissioner, and can be anything the commissioner wants, as long as it's unique within the commissioner's fabric. The commissioning command used above: pairing code 0x1 26058243772 is using 0x1 as the node ID to assign to the commissionee. After that, you need to use the same node ID to sent it commands. You can use any other node ID you want here, as desired.... It's totally up to you, as the commissioner. I'm not sure whether that actually answers your question/concern, though. If it doesn't, can you please clearly explain what problem you are trying to address here? — Reply to this email directly, view it on GitHub <#32706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5XK6QDCGV3VFUOU7KP33NDY3F77ZAVCNFSM6AAAAABFHSUJR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZQGA2TEMZQGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>