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

[1.2] Creation/modification of group does not trigger reporting event on GroupKeyManagement cluster #29773

Closed
jonsmirl opened this issue Oct 14, 2023 · 1 comment · Fixed by #30055
Assignees
Labels
bug Something isn't working group messaging needs triage spec Mismatch between spec and implementation v1.2

Comments

@jonsmirl
Copy link
Contributor

Reproduction steps

Set up a wildcard subscribe to a node. Add a group to the node. Note that adding a group alters GroupKeyManagement Attribute 1 -- GroupTable. Observe that no report was generated on the wildcard subscribe even though the attribute on the GroupKeyManagement cluster changed.

Because there is no reporting event on GroupKeyManagement attribute 1 it is not possible to monitor editing of groups.

Bug prevalence

always

GitHub hash of the SDK that was being used

fc2d829858c3f1597d8e5b7d8873d042fa584e04

Platform

core

Platform Version(s)

No response

Type

Common Cluster Logic

Anything else?

No response

@jonsmirl jonsmirl added bug Something isn't working needs triage labels Oct 14, 2023
@jonsmirl jonsmirl changed the title [1.2] [1.2] Creation/modification of group does not trigger reporting event on GroupKeyManagement cluster Oct 14, 2023
@bzbarsky-apple bzbarsky-apple added spec Mismatch between spec and implementation group messaging v1.2 labels Oct 16, 2023
@bzbarsky-apple
Copy link
Contributor

@rcasallas-silabs @lpbeliveau-silabs Please take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working group messaging needs triage spec Mismatch between spec and implementation v1.2
Projects
Development

Successfully merging a pull request may close this issue.

3 participants