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
Change the switch to first position : echo '{"Name":"SwitchLatched","NewPosition":0}' > /tmp/chip_all_clusters_fifo_<PID> (PID of DUT)
[1686289860.323236][30125:30127] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":0}"
[1686289860.323565][30125:30125] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 89759737
[1686289860.323602][30125:30125] CHIP:-: The latching switch is moved to a new position:0
[1686289860.323618][30125:30125] CHIP:ZCL: SwitchServer: OnSwitchLatch
Change the switch to second position : echo '{"Name":"SwitchLatched","NewPosition":1}' > /tmp/chip_all_clusters_fifo_<PID> (PID of DUT)
[1659600080.279936][7312:7321] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":1}"
[1659600080.280318][7312:7312] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 1755409c
[1659600080.280376][7312:7312] CHIP:-: The latching switch is moved to a new position:1
[1659600080.280412][7312:7312] CHIP:ZCL: SwitchServer: OnSwitchLatch
As per SDK NumberOfPositions value is 2, it should not support more than 2 positions but currently in SDK its able change position up to 255
Change the switch to greater than NumberOfPositions value(Value>2, Ex: 254) : echo '{"Name":"SwitchLatched","NewPosition":254}' > /tmp/chip_all_clusters_fifo_8057
[1691654274.324862][8057:8060] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":254}"
[1691654274.325424][8057:8057] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to e39cff78
[1691654274.325516][8057:8057] CHIP:-: The latching switch is moved to a new position:254
[1691654274.325567][8057:8057] CHIP:ZCL: SwitchServer: OnSwitchLatch
I believe that NumberOfPositions is the maximum position available in the device but the issue here is SDK is able to move the position beyond the NumberOfPositions limit with no error.
The text was updated successfully, but these errors were encountered:
This is an issue with the debugging trigger implementation, which is an artificial switch implementation. It's not a cert blocker per-se since a real switch would not operate via a direct setting if position value.
@yufengwangca could you please update the code to respect the limit in the cluster?
Feature Area
Other
Test Case
TC-SWTCH-2.2
Reproduction steps
Bring up the DUT (all-clusters-app).
Pair the DUT using chip-tool through "onnetwork" transport.
Read NumberOfPositions attribute :
./chip-tool switch read number-of-positions 1 1
echo '{"Name":"SwitchLatched","NewPosition":0}' > /tmp/chip_all_clusters_fifo_<PID> (PID of DUT)
./chip-tool switch read current-position 1 1
echo '{"Name":"SwitchLatched","NewPosition":1}' > /tmp/chip_all_clusters_fifo_<PID> (PID of DUT)
./chip-tool switch read current-position 1 1
As per SDK NumberOfPositions value is 2, it should not support more than 2 positions but currently in SDK its able change position up to 255
echo '{"Name":"SwitchLatched","NewPosition":254}' > /tmp/chip_all_clusters_fifo_8057
9 Read CurrentPosition :
./chip-tool switch read current-position 1 1
Bug prevalence
Every Time
GitHub hash of the SDK that was being used
367a0c6
Platform
raspi
Anything else?
I believe that NumberOfPositions is the maximum position available in the device but the issue here is SDK is able to move the position beyond the NumberOfPositions limit with no error.
The text was updated successfully, but these errors were encountered: