[Bug] [v2.14+fall2025] TC-AVSM-2.7faild for invalid params in videoStreamAllocate command

[c2sw3Tplink]

Describe the bug

Step 10 and Step 27 in TC-AVSM-2.7 failed. My device supports a maximum frame rate of 25fps, but in Step 10, the minFrameRate is 30fps and maxFrameRate is 25fps, causing the test to fail. It appears that minFrameRate is set to a fixed value. Is there a possibility to set a more reasonable minFrameRate?

When I forcibly modified the device’s maximum frame rate to 30fps to continue the subsequent tests, Step 27 failed again. According to the log, the parameters issued by the TH are as follows: maxFrameRate is 40fps, which once again exceeds the device’s limit, causing the test to fail. Could you please verify if there is an issue with the tool? Thank you.
[MatterTest] 03-02 11:03:14.480 INFO "CameraAvStreamManagement::VideoStreamAllocate" :
[MatterTest] 03-02 11:03:14.480 INFO {
[MatterTest] 03-02 11:03:14.480 INFO "OSDEnabled" : "true",
[MatterTest] 03-02 11:03:14.480 INFO "keyFrameInterval" : "4000",
[MatterTest] 03-02 11:03:14.480 INFO "maxBitRate" : "3072000",
[MatterTest] 03-02 11:03:14.480 INFO "maxFrameRate" : "40",
[MatterTest] 03-02 11:03:14.480 INFO "maxResolution" :
[MatterTest] 03-02 11:03:14.480 INFO {
[MatterTest] 03-02 11:03:14.480 INFO "height" : "2160",
[MatterTest] 03-02 11:03:14.480 INFO "width" : "3840"
[MatterTest] 03-02 11:03:14.480 INFO },
[MatterTest] 03-02 11:03:14.480 INFO "minBitRate" : "3072000",
[MatterTest] 03-02 11:03:14.480 INFO "minFrameRate" : "30",
[MatterTest] 03-02 11:03:14.480 INFO "minResolution" :
[MatterTest] 03-02 11:03:14.480 INFO {
[MatterTest] 03-02 11:03:14.481 INFO "height" : "720",
[MatterTest] 03-02 11:03:14.481 INFO "width" : "1280"
[MatterTest] 03-02 11:03:14.481 INFO },
[MatterTest] 03-02 11:03:14.481 INFO "streamUsage" : "1 == kRecording",
[MatterTest] 03-02 11:03:14.481 INFO "videoCodec" : "1 == kHEVC",
[MatterTest] 03-02 11:03:14.481 INFO "watermarkEnabled" : "true"
[MatterTest] 03-02 11:03:14.481 INFO },

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

TC-AVSM-2.7第27步失败的TH log：UI_Test_Run_2026_03_04_03_25_51.log

PICS file

No response

Screenshots

No response

Environment

No response

Additional Information

No response

[rquidute]

Hi @chulspro , I’m not sure if you’re the right person to ask, but could you help with this issue?

[c2sw3Tplink]

Could someone help answer this question? Is it an issue with the TH tool or with our DUT?

[rquidute]

It seems there is a fix for min framerate here.
According to the logs, you are using 2.14+fall2025 version, could you try using 2.14.1+winter2026 (Matter v1.5.1 version)?
CC @Pradeep-grl

[c2sw3Tplink]

Could you please confirm whether v2.14.1+winter2026 is the final branch for version 1.5.1? Previously, we used v2.14.1-beta2+winter2026. The commit you mentioned should fix the issue, but I see that it was only merged into the master branch. However, the SDK node specified in test_collections/matter/config.py for the v2.14.1+winter2026 branch appears to be e9ecfc2138887d3221dcc2995ad629c8bd4313e4, which is located on the v1.5-branch. Currently, the code on that branch is still the old version. Please help confirm whether we should use the v2.14.1+winter2026 branch. Thank you.

[rquidute]

Hi @c2sw3Tplink, yes, the branch for v1.5.1 is v2.14.1+winter2026 (TH repo). Since the code for this PR was only merged into master, it needs to be cherry-picked into the v1.5-branch as well (from the SDK Repo). I suggest raising this question in the Slack group.

[c2sw3Tplink]

，Hi，@rquidute，Thanks for your help, I manually modified the TC_AVSM_2_7.py script according to the commit, but the test still fails to pass. From the script code, it can be seen that during the first execution of videoStreamAllocate, maxFrameRateConfig is set to aVideoSensorParams.maxFPS (this attribute is the maximum frame rate supported by the camera). The second time, maxFrameRateConfig is increased by 20, which will inevitably exceed the camera’s capabilities, resulting in a DYNAMIC_CONSTRAINT_ERROR status code and test failure. This code appears unable to achieve its intended purpose.

Additionally, I would like to ask: Suppose a camera has two streams with different resolutions (i.e., aMaxConcurrentEncoders=2), but both streams have a fixed, unchangeable frame rate, such as 15fps. In this case, testing whether the encoder limit is reached by modifying the frame rate seems unreasonable, because either one stream can be reused, or the test will fail due to the required frame rate being out of range. Has the consideration been given to devices with fixed frame rates like this?

[c2sw3Tplink]

[rquidute]

Hi @c2sw3Tplink Could you please send this to the camera team in this slack group (#matter-camera-test-harness-subgroup)?

[c2sw3Tplink]

ok，i wll have a try