diff --git a/docs/cli-help.md b/docs/cli-help.md index 7ceb2d7b5..515b792cc 100644 --- a/docs/cli-help.md +++ b/docs/cli-help.md @@ -75,7 +75,7 @@ The set of commands that allows you to manage accounts and assigned roles. Roles: - `Trustee` - Is able to create accounts, assign roles, approve root certificates. -- `Vendor` - Is able to add models. +- `Vendor` - Is able to add models that belong to the vendor ID associated with the vendor account. - `TestHouse` - Is able to add testing results for a model. - `CertificationCenter` - Is able to certify and revoke models. - `NodeAdmin` - Is able to add validator nodes to the network. @@ -397,12 +397,69 @@ The set of commands that allows you to manage X.509 certificates. Example: `dclcli query pki all-revoked-x509-root-certs` + +### Vendor Info + +The set of commands that allows the Vendor to update contact information. +##### Transactions +- Add a new vendor contact info. + + Role: `Vendor` + + Command: `dclcli tx vendorinfo add-vendor --companyLegalName= --companyPreferredName= --vendorName= --vid= ----vendorLandingPageUrl= --from=` + + Flags: + - companyLegalName `string (max64)` - Company Legal Name + - companyPreferredName `optional string (max64)` - Company Preferred Name + - vendorLandingPageUrl `optional string (max256)` - Landing Page URL for the Vendor + - vendorName `string (max32)` - Vendor Name + - vid `uint16` - Vendor ID + + + Example: `dclcli tx vendorinfo add-vendor --companyLegalName="XYZ Technology Solutions" --vid=123 --vendorName="XYZ Inc" --from="jack"` + +- Update vendor contact info. + + Role: `Vendor` + + Command: `dclcli tx vendorinfo update-vendor --companyLegalName= --companyPreferredName= --vendorName= --vid= ----vendorLandingPageUrl= --from=` + + + Flags: + - companyLegalName `string (max64)` - Company Legal Name + - companyPreferredName `optional string (max64)` - Company Preferred Name + - vendorLandingPageUrl `optional string (max256)` - Landing Page URL for the Vendor + - vendorName `string (max32)` - Vendor Name + - vid `uint16` - Vendor ID + + Example: `dclcli tx vendorinfo update-vendor --vendorLandingPageUrl="https://producturl.vendor.info" --vid=123 --from="jack"` + +##### Queries +- Query a single vendor info. + + Command: `dclcli query vendorinfo vendor --vid=` + + Flags: + - vid: `uint16` - vendor ID + + Example: `dclcli query vendorinfo vendor --vid=1` + +- Query a list of all vendor infos. + + Command: `dclcli query vendorinfo all-vendors` + + Flags: + - skip: `optional(int)` - number records to skip (`0` by default) + - take: `optional(int)` - number records to take (all records are returned by default) + + Example: `dclcli query vendorinfo all-vendors` + ### Model Info The set of commands that allows you to manage model and model versions. ##### Transactions -- Add a new model. +- Add a new model. Only vendor role with associated vendor ID can add the model for given Vendor ID Role: `Vendor` @@ -413,40 +470,82 @@ The set of commands that allows you to manage model and model versions. Flags: - vid: `uint16` - model vendor ID (positive non-zero) - pid: `uint16` - model product ID (positive non-zero) - - name: `string` - model name - - description: `string` - model description (string or path to file containing data) - - sku: `string` - stock keeping unit - - softwareVersion: `uint32` - Software Version of model (uint32) - - softwareVersionString: `string` - Software Version String of model - - hardwareVersion: `uint32` - version of model hardware - - hardwareVersionString: `string` - Hardware Version String of model - - cdVersionNumber: `uint32` - CD Version Number of the Certification - - from: `string` - Name or address of private key with which to sign - - cid: `optional(uint16)` - model category ID (positive non-zero) - - revoked: `optional(bool)` - boolean flag to revoke the model - - otaURL: `optional(string)` - the URL of the OTA - - otaChecksum: `optional(string)` - the checksum of the OTA - - otaChecksumType: `optional(string)` - the type of the OTA checksum - - otaBlob: `optional(string)` - metadata about OTA + - deviceTypeID: `uint16` - DeviceTypeID is the device type identifier. For example, DeviceTypeID 10 (0x000a), is the device type identifier for a Door Lock. + - productName: `string` - model name + - productLabel: `string` - model description (string or path to file containing data) + - partNumber: `string` - stock keeping unit + - commissioningCustomFlow: `optional(uint8)` - A value of 1 indicates that user interaction with the device (pressing a button, for example) is required before commissioning can take place. When CommissioningCustomflow is set to a value of 2, the commissioner SHOULD attempt to obtain a URL which MAY be used to provide an end-user with the necessary details for how to configure the product for initial commissioning - commissioningCustomFlowURL: `optional(string)` - commissioningCustomFlowURL SHALL identify a vendor specific commissioning URL for the device model when the commissioningCustomFlow field is set to '2' - commissioningModeInitialStepsHint: `optional(uint32)` - commissioningModeInitialStepsHint SHALL identify a hint for the steps that can be used to put into commissioning mode a device that has not yet been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 1 (bit 0 is set) indicates that a device that has not yet been commissioned will enter Commissioning Mode upon a power cycle. - commissioningModeInitialStepsInstruction: `optional(string)` - commissioningModeInitialStepsInstruction SHALL contain text which relates to specific values of CommissioningModeInitialStepsHint. Certain values of CommissioningModeInitialStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeInitialStepsInstruction SHALL be set - commissioningModeSecondaryStepsHint: `optional(uint32)` - commissioningModeSecondaryStepsHint SHALL identify a hint for steps that can be used to put into commissioning mode a device that has already been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 4 (bit 2 is set) indicates that a device that has already been commissioned will require the user to visit a current CHIP Administrator to put the device into commissioning mode. - commissioningModeSecondaryStepInstruction: `optional(string)` - commissioningModeSecondaryStepInstruction SHALL contain text which relates to specific values of commissioningModeSecondaryStepsHint. Certain values of commissioningModeSecondaryStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeSecondaryStepInstruction SHALL be set - - releaseNotesURL: `optional(string)` - URL that contains product specific web page that contains release notes for the device model. - userManualURL: `optional(string)` - URL that contains product specific web page that contains user manual for the device model. - supportURL: `optional(string)` - URL that contains product specific web page that contains support details for the device model. - productURL: `optional(string)` - URL that contains product specific web page that contains details for the device model. - - chipBlob: `optional(string)` - chipBlob SHALL identify CHIP specific configurations - - vendorBlob: `optional(string)` - field for vendors to provide any additional metadata about the device model using a string, blob, or URL. + - Example: `dclcli tx model add-model --vid=1 --pid=1 --productName="Device #1" --productLabel="Device Description" --sku="SKU12FS" --softwareVersion="10123" --softwareVersionString="1.0b123" --hardwareVersion="5123" --hardwareVersionString="5.1.23" --cdVersionNumber="32" --from="jack"` + Example: `dclcli tx model add-model --vid=1 --pid=1 --productName="Device #1" --productLabel="Device Description" --partNumber="SKU12FS" --from="jack"` - Example: `dclcli tx model add-model --vid=1 --pid=1 --productName="Device #1" --productLabel="Device Description" --sku="SKU12FS" --softwareVersion="10123" --softwareVersionString="1.0b123" --hardwareVersion="5123" --hardwareVersionString="5.1.23" --cdVersionNumber="32" --cid=1 --custom="Some Custom information" --otaURL="http://my-ota.com" --otaChecksum="df56hf" --otaChecksumType="SHA-256" --from=jack ` +- Update an existing model. Only the vendor role with associated vendorID can edit a Model. -- Update an existing model info. Only the owner can edit a Model Info. + Role: `Vendor` + + Command: `dclcli tx model update-model --vid= --pid= --from=` + existing Model. + + Flags: + - vid: `uint16` - model vendor ID (positive non-zero) + - pid: `uint16` - model product ID (positive non-zero) + - productName: `string` - model name + - productLabel: `string` - model description (string or path to file containing data) + - partNumber: `string` - stock keeping unit + - commissioningCustomFlowURL: `optional(string)` - commissioningCustomFlowURL SHALL identify a vendor specific commissioning URL for the device model when the commissioningCustomFlow field is set to '2' + - commissioningModeInitialStepsHint: `optional(uint32)` - commissioningModeInitialStepsHint SHALL identify a hint for the steps that can be used to put into commissioning mode a device that has not yet been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 1 (bit 0 is set) indicates that a device that has not yet been commissioned will enter Commissioning Mode upon a power cycle. + - commissioningModeInitialStepsInstruction: `optional(string)` - commissioningModeInitialStepsInstruction SHALL contain text which relates to specific values of CommissioningModeInitialStepsHint. Certain values of CommissioningModeInitialStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeInitialStepsInstruction SHALL be set + - commissioningModeSecondaryStepsHint: `optional(uint32)` - commissioningModeSecondaryStepsHint SHALL identify a hint for steps that can be used to put into commissioning mode a device that has already been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 4 (bit 2 is set) indicates that a device that has already been commissioned will require the user to visit a current CHIP Administrator to put the device into commissioning mode. + - commissioningModeSecondaryStepInstruction: `optional(string)` - commissioningModeSecondaryStepInstruction SHALL contain text which relates to specific values of commissioningModeSecondaryStepsHint. Certain values of commissioningModeSecondaryStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeSecondaryStepInstruction SHALL be set + - userManualURL: `optional(string)` - URL that contains product specific web page that contains user manual for the device model. + - supportURL: `optional(string)` - URL that contains product specific web page that contains support details for the device model. + - productURL: `optional(string)` - URL that contains product specific web page that contains details for the device model. + + + Example: `dclcli tx model update-model --vid=1 --pid=1 --productLabel="New Description" --from=jack ` + + Example: `dclcli tx model update-model --vid=1 --pid=1 --supportURL="https://product-support.url.test" --from=jack ` + + +- Add a new model version. Only vendor role with associated vendor ID can add the model versions for given Vendor ID + + Role: `Vendor` + + Command: `dclcli tx model add-model-version --cdVersionNumber=1 --maxApplicableSoftwareVersion=10 --minApplicableSoftwareVersion=1 --vid=$vid --pid=$pid1 --softwareVersion=$software_version --softwareVersionString=1 --from=$user_address` + + Flags: + - vid: `uint16` - model vendor ID (positive non-zero) + - pid: `uint16` - model product ID (positive non-zero) + - deviceTypeID: `uint16` - DeviceTypeID is the device type identifier. For example, DeviceTypeID 10 (0x000a), is the device type identifier for a Door Lock. + - productName: `string` - model name + - productLabel: `string` - model description (string or path to file containing data) + - partNumber: `string` - stock keeping unit + + - commissioningCustomFlow: `optional(uint8)` - A value of 1 indicates that user interaction with the device (pressing a button, for example) is required before commissioning can take place. When CommissioningCustomflow is set to a value of 2, the commissioner SHOULD attempt to obtain a URL which MAY be used to provide an end-user with the necessary details for how to configure the product for initial commissioning + - commissioningCustomFlowURL: `optional(string)` - commissioningCustomFlowURL SHALL identify a vendor specific commissioning URL for the device model when the commissioningCustomFlow field is set to '2' + - commissioningModeInitialStepsHint: `optional(uint32)` - commissioningModeInitialStepsHint SHALL identify a hint for the steps that can be used to put into commissioning mode a device that has not yet been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 1 (bit 0 is set) indicates that a device that has not yet been commissioned will enter Commissioning Mode upon a power cycle. + - commissioningModeInitialStepsInstruction: `optional(string)` - commissioningModeInitialStepsInstruction SHALL contain text which relates to specific values of CommissioningModeInitialStepsHint. Certain values of CommissioningModeInitialStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeInitialStepsInstruction SHALL be set + - commissioningModeSecondaryStepsHint: `optional(uint32)` - commissioningModeSecondaryStepsHint SHALL identify a hint for steps that can be used to put into commissioning mode a device that has already been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 4 (bit 2 is set) indicates that a device that has already been commissioned will require the user to visit a current CHIP Administrator to put the device into commissioning mode. + - commissioningModeSecondaryStepInstruction: `optional(string)` - commissioningModeSecondaryStepInstruction SHALL contain text which relates to specific values of commissioningModeSecondaryStepsHint. Certain values of commissioningModeSecondaryStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeSecondaryStepInstruction SHALL be set + - userManualURL: `optional(string)` - URL that contains product specific web page that contains user manual for the device model. + - supportURL: `optional(string)` - URL that contains product specific web page that contains support details for the device model. + - productURL: `optional(string)` - URL that contains product specific web page that contains details for the device model. + + + + Example: `dclcli tx model add-model --vid=1 --pid=1 --productName="Device #1" --productLabel="Device Description" --partNumber="SKU12FS" --from="jack"` + +- Update an existing model. Only the vendor role with associated vendorID can edit a Model. Role: `Vendor` @@ -454,30 +553,27 @@ The set of commands that allows you to manage model and model versions. existing Model. Flags: - - vid: `uint16` - model vendor ID - - pid: `uint16` - model product ID - - description: `string` - model description (string or path to file containing data) - - cdVersionNumber: `uint32` - CD Version Number of the Certification - - from: `string` - Name or address of private key with which to sign - - revoked: `optional(bool)` - boolean flag to revoke the model - - otaURL: `optional(string)` - the URL of the OTA - - otaChecksum: `optional(string)` - the checksum of the OTA - - otaChecksumType: `optional(string)` - the type of the OTA checksum - - otaBlob: `optional(string)` - metadata about OTA + - vid: `uint16` - model vendor ID (positive non-zero) + - pid: `uint16` - model product ID (positive non-zero) + - productName: `string` - model name + - productLabel: `string` - model description (string or path to file containing data) + - partNumber: `string` - stock keeping unit - commissioningCustomFlowURL: `optional(string)` - commissioningCustomFlowURL SHALL identify a vendor specific commissioning URL for the device model when the commissioningCustomFlow field is set to '2' - - releaseNotesURL: `optional(string)` - URL that contains product specific web page that contains release notes for the device model. + - commissioningModeInitialStepsHint: `optional(uint32)` - commissioningModeInitialStepsHint SHALL identify a hint for the steps that can be used to put into commissioning mode a device that has not yet been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 1 (bit 0 is set) indicates that a device that has not yet been commissioned will enter Commissioning Mode upon a power cycle. + - commissioningModeInitialStepsInstruction: `optional(string)` - commissioningModeInitialStepsInstruction SHALL contain text which relates to specific values of CommissioningModeInitialStepsHint. Certain values of CommissioningModeInitialStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeInitialStepsInstruction SHALL be set + - commissioningModeSecondaryStepsHint: `optional(uint32)` - commissioningModeSecondaryStepsHint SHALL identify a hint for steps that can be used to put into commissioning mode a device that has already been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 4 (bit 2 is set) indicates that a device that has already been commissioned will require the user to visit a current CHIP Administrator to put the device into commissioning mode. + - commissioningModeSecondaryStepInstruction: `optional(string)` - commissioningModeSecondaryStepInstruction SHALL contain text which relates to specific values of commissioningModeSecondaryStepsHint. Certain values of commissioningModeSecondaryStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeSecondaryStepInstruction SHALL be set - userManualURL: `optional(string)` - URL that contains product specific web page that contains user manual for the device model. - supportURL: `optional(string)` - URL that contains product specific web page that contains support details for the device model. - productURL: `optional(string)` - URL that contains product specific web page that contains details for the device model. - - chipBlob: `optional(string)` - chipBlob SHALL identify CHIP specific configurations - - vendorBlob: `optional(string)` - field for vendors to provide any additional metadata about the device model using a string, blob, or URL. + - Example: `dclcli tx model update-model --vid=1 --pid=1 --cdVersionNumber="32" --productLabel="New Description" --from=jack ` + Example: `dclcli tx model update-model --vid=1 --pid=1 --productLabel="New Description" --from=jack ` - Example: `dclcli tx model update-model --vid=1 --pid=1 --supportURL="https://product-support.url.test" --otaURL="http://new-ota.com" --from=jack ` + Example: `dclcli tx model update-model --vid=1 --pid=1 --supportURL="https://product-support.url.test" --from=jack ` ##### Queries -- Query a single model info. +- Query a single model. Command: `dclcli query model get-model --vid= --pid=` @@ -486,8 +582,19 @@ The set of commands that allows you to manage model and model versions. - pid: `uint16` - model product ID Example: `dclcli query model get-model --vid=1 --pid=1` + +- Query a single model version. + + Command: `dclcli query model get-model-version --vid= --pid= --softwareVersion=` + + Flags: + - vid: `uint16` - model vendor ID + - pid: `uint16` - model product ID + - softwareVersion: `uint32` - model software version + + Example: `dclcli query model get-model-version --vid=1 --pid=1 --softwareVersion=1` -- Query a list of all model infos. +- Query a list of all models. Command: `dclcli query model all-models` @@ -497,6 +604,18 @@ The set of commands that allows you to manage model and model versions. Example: `dclcli query model all-models` +- Query a list of all model versions for a given model. + + Command: `dclcli query model all-model-versions --vid= --pid=` + + Flags: + - vid: `uint16` - model vendor ID + - pid: `uint16` - model product ID + - skip: `optional(int)` - number records to skip (`0` by default) + - take: `optional(int)` - number records to take (all records are returned by default) + + Example: `dclcli query model all-model-versions --vid=1 --pid=1` + - Query a list of all vendors. Command: `dclcli query model vendors` @@ -507,7 +626,7 @@ The set of commands that allows you to manage model and model versions. Example: `dclcli query model vendors` -- Query a list of all model infos for the given vendor. +- Query a list of all models for the given vendor. Command: `dclcli query model vendor-models --vid=` @@ -527,81 +646,86 @@ The set of commands that allows you to manage testing results associated with a Role: `TestHouse` - Command: ` dclcli tx compliancetest add-test-result --vid= --pid= --test-result= --test-date= --from=` + Command: ` dclcli tx compliancetest add-test-result --vid= --pid= --softwareVersion= --test-result= --test-date= --from=` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID + - softwareVersion: `uint32` - model software version - test-result: `string` - test result (string or path to file containing data) - test-date: `string` - date of test result (rfc3339 encoded) - from: `string` - Name or address of private key with which to sign - Example: `dclcli tx compliancetest add-test-result --vid=1 --pid=1 --test-result="Test Document" --test-date="2020-04-16T06:04:57.05Z" --from=jack` + Example: `dclcli tx compliancetest add-test-result --vid=1 --pid=1 --softwareVersion=1 --test-result="Test Document" --test-date="2020-04-16T06:04:57.05Z" --from=jack` - Example: `dclcli tx compliancetest add-test-result --vid=1 --pid=1 --test-result="path/to/document" --test-date="2020-04-16T06:04:57.05Z" --from=jack` + Example: `dclcli tx compliancetest add-test-result --vid=1 --pid=1 --softwareVersion=1 --test-result="path/to/document" --test-date="2020-04-16T06:04:57.05Z" --from=jack` ##### Queries - Query testing results for model associated with the given VID/PID. - Command: `dclcli query compliancetest test-result --vid= --pid=` + Command: `dclcli query compliancetest test-result --vid= --pid= --softwareVersion="` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID + - softwareVersion: `uint32` - model software version - Example: `dclcli query compliancetest test-result --vid=1 --pid=1` + Example: `dclcli query compliancetest test-result --vid=1 --pid=1 --softwareVersion=1` ### Compliance The set of commands that allows you to manage model certification information. ##### Transactions -- Certify a model associated with the given VID/PID. Note that the corresponding model and the test results must present on the ledger. +- Certify a model associated with the given VID/PID/SoftwareVersion. Note that the corresponding model and the test results must present on the ledger. Only the owner can update an existing record. Role: `CertificationCenter` - Command: `dclcli tx compliance certify-model --vid= --pid= --certificationType= --certificationDate= --from=` + Command: `dclcli tx compliance certify-model --vid= --pid= --softwareVersion= --certificationType= --certificationDate= --from=` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID - - certificationType: `string` - certification type (zb` is the only supported value now) + - softwareVersion: `uint32` - model software version + - certificationType: `string` - certification type (zigbee & matter` are the only supported values for now) - certificationDate: `string` - the date of model certification (rfc3339 encoded) - from: `string` - name or address of private key with which to sign - reason: `optional(string)` - an optional comment describing the reason of certification - Example: `dclcli tx compliance certify-model --vid=1 --pid=1 --certificationType="zb" --certificationDate="2020-04-16T06:04:57.05Z" --from=jack` + Example: `dclcli tx compliance certify-model --vid=1 --pid=1 --softwareVersion=1 --certificationType="matter" --certificationDate="2020-04-16T06:04:57.05Z" --from=jack` -- Revoke certification for a model associated with the given VID/PID. Only the owner can update an existing record. +- Revoke certification for a model associated with the given VID/PID/SoftwareVersion. Only the owner can update an existing record. Role: `CertificationCenter` - Command: ` dclcli tx compliance revoke-model --vid= --pid= --certificationType= --revocationDate= --from=` + Command: ` dclcli tx compliance revoke-model --vid= --pid= --softwareVersion= --certificationType= --revocationDate= --from=` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID - - certificationType: `string` - certification type (zb` is the only supported value now) + - softwareVersion: `uint32` - model software version + - certificationType: `string` - certification type (zigbee & matter` are the only supported values for now) - revocationDate: `string` - the date of model revocation (rfc3339 encoded) - from: `string` - name or address of private key with which to sign - reason: `optional(string)` - an optional comment describing the reason of revocation - Example: `dclcli tx compliance revoke-model --vid=1 --pid=1 --certificationType="zb" --revocationDate="2020-04-16T06:04:57.05Z" --from=jack` + Example: `dclcli tx compliance revoke-model --vid=1 --pid=1 --softwareVersion=1 --certificationType="matter" --revocationDate="2020-04-16T06:04:57.05Z" --from=jack` - Example: `dclcli tx compliance revoke-model --vid=1 --pid=1 --certificationType="zb" --revocationDate="2020-04-16T06:04:57.05Z" --reason "Some Reason" --from=jack` + Example: `dclcli tx compliance revoke-model --vid=1 --pid=1 --softwareVersion=1 --certificationType="matter" --revocationDate="2020-04-16T06:04:57.05Z" --reason "Some Reason" --from=jack` ##### Queries -- Check if the model associated with the given VID/PID is certified. +- Check if the model associated with the given VID/PID/SoftwareVersion is certified. Command: `dclcli query compliance certified-model --vid= --pid= --certificationType=` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID - - certificationType: `string` - certification type (zb` is the only supported value now) + - softwareVersion: `uint32` - model software version + - certificationType: `string` - certification type (zigbee & matter` are the only supported values for now) - Example: `dclcli query compliance certified-model --vid=1 --pid=1 --certificationType="zb"` + Example: `dclcli query compliance certified-model --vid=1 --pid=1 --softwareVersion=1 --certificationType="matter"` - Query all certified models. @@ -613,16 +737,17 @@ Only the owner can update an existing record. Example: `dclcli query compliance all-certified-models` -- Check if the model associated with the given VID/PID is revoked. +- Check if the model associated with the given VID/PID/SoftwareVersion is revoked. - Command: `dclcli query compliance revoked-model --vid= --pid= --certificationType=` + Command: `dclcli query compliance revoked-model --vid= --pid= --softwareVersion= --certificationType=` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID - - certificationType: `string` - certification type (zb` is the only supported value now) + - softwareVersion: `uint32` - model software version + - certificationType: `string` - certification type (zigbee & matter` are the only supported values for now) - Example: `dclcli query compliance revoked-model --vid=1 --pid=1 --certificationType="zb"` + Example: `dclcli query compliance revoked-model --vid=1 --pid=1 --softwareVersion=1 --certificationType="matter"` - Query all revoked models. @@ -634,16 +759,16 @@ Only the owner can update an existing record. Example: `dclcli query compliance all-revoked-models` -- Query compliance info for model associated with VID/PID. +- Query compliance info for model associated with VID/PID/SoftwareVersion. - Command: `dclcli query compliance compliance-info --vid= --pid= --certificationType=` + Command: `dclcli query compliance compliance-info --vid= --pid= --softwareVersion= --certificationType=` Flags: - vid: `uint16` - model vendor ID - pid: `uint16` - model product ID - - certificationType: `string` - certification type (zb` is the only supported value now) + - certificationType: `string` - certification type (zigbee & matter` are the only supported values for now) - Example: `dclcli query compliance compliance-info --vid=1 --pid=1 --certificationType="zb"` + Example: `dclcli query compliance compliance-info --vid=1 --pid=1 --softwareVersion=1 --certificationType="matter"` - Query all compliance infos.