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
I'm working with a test device that has endpoints with both Level Control and Mode Select clusters.
An odd behavior is happening - when I use the webUI interface to examine attributes of the Level Control cluster, I am seeing double-listing of certain attributes, and listing of both the expected Level Control attributes as well as the Mode Select attributes when I should only see the Level Control attributes. See image below.
Here's an example of the clusters. Note that one oddity, and it may be just formatting, is that certain clusters are only 3 hex digits (e.g., 0x008 or level control compared to 0x0050 for mode select).
The Problem
Then when I look at the attributes for Level Control, I get the listing shown below. Notice how there is a repetition of certain attributes. E.g., CurrentLevel, MinLevel, MaxLevel, etc. Anohter thing that is happening - notice how the first CurrentLevel is a numeric value - i.e., 1, but the repeated CurrentLevel is set to a string label ("Switch Mode"). This "Switch Mode" label value is actually a bleed-over from the Mode Select cluster on the same endpoint. Note again, how some attributes are 3 hex digits rather than the typical use of 4 or 8 hex digits:
The text was updated successfully, but these errors were encountered:
I'm working with a test device that has endpoints with both Level Control and Mode Select clusters.
An odd behavior is happening - when I use the webUI interface to examine attributes of the Level Control cluster, I am seeing double-listing of certain attributes, and listing of both the expected Level Control attributes as well as the Mode Select attributes when I should only see the Level Control attributes. See image below.
Here's an example of the clusters. Note that one oddity, and it may be just formatting, is that certain clusters are only 3 hex digits (e.g., 0x008 or level control compared to 0x0050 for mode select).
The Problem
Then when I look at the attributes for Level Control, I get the listing shown below. Notice how there is a repetition of certain attributes. E.g., CurrentLevel, MinLevel, MaxLevel, etc. Anohter thing that is happening - notice how the first CurrentLevel is a numeric value - i.e., 1, but the repeated CurrentLevel is set to a string label ("Switch Mode"). This "Switch Mode" label value is actually a bleed-over from the Mode Select cluster on the same endpoint. Note again, how some attributes are 3 hex digits rather than the typical use of 4 or 8 hex digits:
The text was updated successfully, but these errors were encountered: