project-chip / project-chip/matter-test-scripts

[Bug] TC-DRLK-2.11 is required in the SVE while Currently the cluster doesn’t describe how to create fingerprint/finger vein credentials

Open
#377 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
19
Forks
7
Avg merge
3d 17h
Merged PRs (30d)
3

Description

Describe the bug

./chip-tool doorlock set-credential 0 '{ "credentialType": 4, "credentialIndex": 1 }' "123456789A" null null 0 6452 1 --timedInteractionTimeoutMs 10000

Expected:
[1675102225843] [61811:1859583] [TOO] SetCredentialResponse: {
[1675102225843] [61811:1859583] [TOO] status: 0
[1675102225843] [61811:1859583] [TOO] userIndex: null
[1675102225843] [61811:1859583] [TOO] nextCredentialIndex: 2
[1675102225843] [61811:1859583] [TOO] }

Result
status: 133
userIndex: null
nextCredentialIndex: null

Steps to reproduce the behavior

No response

Expected behavior

update the zap file(FeatureMap=0x7D87, to include FingerCredentials feature), and also update the PICS to select DRLK.S.F02(Lock supports finger related credentials(fingerprint, fingervein)). run the TC_DRLK_2.11, but report error, and all errors are from Finger Vein

Log files

TC_DRLK_2_11_2024_09_27_02_15_22.log

PICS file

Door Lock Cluster Test Plan.zip

Screenshots

image

Environment

Version: v2.11-beta3.1+fall2024

Additional Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the TC_DRLK_2_11 log alongside the attached zap file and PICS file, focusing on the FingerCredentials feature and DRLK.S.F02 selection. Re-run TC_DRLK_2.11 after the configuration updates; done means the finger and finger-vein credential checks no longer report errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.