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
Part of the following PR #25345 fixed a few error codes returned and also the timing at which they were returned (as early as possible)
It was pointed out that a StepMode Stop is implemented with similar behaviour to MoveMode Stop and that there is, however, no StepMode Stop in the spec. #25345 (comment)
StepMode=0 is a reserved value with no current definition. Any step command with a StepMode of 0 should return INVALID_COMMAND
To reproduce the issue send ./chip-tool colorcontrol step-hue 0 200 200 1 1 <node_id> <endpoint>
the command will return a success. It should return a failure
Reproduction steps
Part of the following PR #25345 fixed a few error codes returned and also the timing at which they were returned (as early as possible)
It was pointed out that a StepMode Stop is implemented with similar behaviour to MoveMode Stop and that there is, however, no StepMode Stop in the spec.
#25345 (comment)
StepMode=0 is a reserved value with no current definition. Any step command with a StepMode of 0 should return INVALID_COMMAND
To reproduce the issue send
./chip-tool colorcontrol step-hue 0 200 200 1 1 <node_id> <endpoint>
the command will return a success. It should return a failure
Bug prevalence
Always
GitHub hash of the SDK that was being used
a2f83a9
Platform
core
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: