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

feature for automated uc component removal #1129

Merged
merged 3 commits into from
Sep 8, 2023
Merged

feature for automated uc component removal #1129

merged 3 commits into from
Sep 8, 2023

Conversation

jingteng25742
Copy link
Contributor

No description provided.

jingteng25742 added 3 commits September 8, 2023 10:33
When running embedded as part of Studio, ZAP will enable the
corresponding UC component if an ZCL cluster server/client is enabled.
In reverse, similar behavior will apply.

If there are only a single endpoint, disabling a ZCL cluster will cause
an UC component to be disabled.

If there are multiple endpoints, disabling the last enabled cluster
across all endpoints will trigger the corresponding UC component to be
disabled.
ws connection is between studio/zap backend
@jingteng25742 jingteng25742 merged commit 3ffd71e into project-chip:master Sep 8, 2023
@jingteng25742 jingteng25742 deleted the feature/uc_component_removal branch September 8, 2023 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant