Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TE#7][TC-LVL-3.1] move operation LevelControl exceeding the max level #12011

Closed
Kxuan opened this issue Nov 19, 2021 · 2 comments
Closed

[TE#7][TC-LVL-3.1] move operation LevelControl exceeding the max level #12011

Kxuan opened this issue Nov 19, 2021 · 2 comments
Assignees

Comments

@Kxuan
Copy link
Contributor

Kxuan commented Nov 19, 2021

Problem

The step 2 in the test plan says:

2: TH reads CurrentLevel attribute from DUT
Verify that the DUT response indiicates that the CurrentLevel attribute has the value recorded in 1a, or if the MaxLevel attribute is not supported (PICS_MAXLEVEL = false) 0xFE

But SDK acturally raise the current level to 0xff, which is too large.

logs from DUT;

I (185761) chip[EM]: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:1 on exchange 42936r
I (185771) chip[ZCL]: Event: move from 254
I (185781) chip[ZCL]:  to 255
I (185781) chip[ZCL]: (diff +1)
I (185781) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0008', EndPoint ID: '0x01', Attribute ID: '0x0000'

Proposed Solution

limit the max level to 254

@jmartinez-silabs
Copy link
Member

Let me confirm on monday, but this is fixed.

@jmartinez-silabs
Copy link
Member

Confirmed move command works correctly and stops at the 254 limit not 255

fixed with #13338

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants