You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is causing any practical issues / problems, but I notice that the generated QR-code from using the "open_commissioning_window" command to the Python Matter Server is a bit different from the QR-code generated by the equivalent chip-tool command. I find it a bit strange, since it looks like the parameters sendt to the SDK looks identical.
When I send the "open_commissioning_window" specifying just the node_id as an argument, I get a QR-code like this:
MT:00000CQM007KJZ6LN10
If I parse it using the chip-tool command:
./chip-tool payload parse-setup-payload MT:00000CQM007KJZ6LN10, I get:
I'm not sure if this is causing any practical issues / problems, but I notice that the generated QR-code from using the "open_commissioning_window" command to the Python Matter Server is a bit different from the QR-code generated by the equivalent chip-tool command. I find it a bit strange, since it looks like the parameters sendt to the SDK looks identical.
When I send the "open_commissioning_window" specifying just the node_id as an argument, I get a QR-code like this:
MT:00000CQM007KJZ6LN10
If I parse it using the chip-tool command:
./chip-tool payload parse-setup-payload MT:00000CQM007KJZ6LN10, I get:
[1741031765.774] [12542:12542] [DL] ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs
[1741031765.774] [12542:12542] [SPL] Parsing base38Representation: MT:00000CQM007KJZ6LN10
[1741031765.775] [12542:12542] [SPL] Version: 0
[1741031765.775] [12542:12542] [SPL] VendorID: 0
[1741031765.775] [12542:12542] [SPL] ProductID: 0
[1741031765.775] [12542:12542] [SPL] Custom flow: 0 (STANDARD)
[1741031765.775] [12542:12542] [SPL] Discovery Bitmask: 0x04 (On IP network)
[1741031765.775] [12542:12542] [SPL] Long discriminator: 1176 (0x498)
[1741031765.775] [12542:12542] [SPL] Passcode: 76672593
Here both VendorID and ProductID are zero.
Using the chip-tool command to open a commissioning window like this:
./chip-tool pairing open-commissioning-window 1 1 600 1000 3840
results in a QR-code like this:
MT:6FCJ1AFN00ETFH1TR10
If I parse it using the chip-tool command:
./chip-tool payload parse-setup-payload MT:00000CQM007KJZ6LN10, I get:
[1741032369.114] [12551:12551] [DL] ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs
[1741032369.114] [12551:12551] [SPL] Parsing base38Representation: MT:6FCJ1AFN00ETFH1TR10
[1741032369.114] [12551:12551] [SPL] Version: 0
[1741032369.114] [12551:12551] [SPL] VendorID: 65521
[1741032369.114] [12551:12551] [SPL] ProductID: 32773
[1741032369.114] [12551:12551] [SPL] Custom flow: 0 (STANDARD)
[1741032369.114] [12551:12551] [SPL] Discovery Bitmask: 0x04 (On IP network)
[1741032369.114] [12551:12551] [SPL] Long discriminator: 3840 (0xf00)
[1741032369.114] [12551:12551] [SPL] Passcode: 81893170
Here the values for VendorID and ProductID are correct.
Why the difference?
The text was updated successfully, but these errors were encountered: