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

Setting up desired permissions (CON-1315) #1064

Open
simonFloat opened this issue Aug 26, 2024 · 1 comment
Open

Setting up desired permissions (CON-1315) #1064

simonFloat opened this issue Aug 26, 2024 · 1 comment

Comments

@simonFloat
Copy link

How does a controller (not commissioner), get required permissions to operate desired devices? The example of a light-switch to on-off light makes sense. But what if, in my case, the devices needs to be monitoring X amount of devices on-off cluster to read if they are on or not.

How would this be set up with regard to permissions? Would the monitoring device still make use of a on-off client cluster? And is there a way for a device to signal what permissions it desire to have on other devices?

@github-actions github-actions bot changed the title Setting up desired permissions Setting up desired permissions (CON-1315) Aug 26, 2024
@wqx6
Copy link
Contributor

wqx6 commented Sep 3, 2024

During commissioning, the commissioner will send AddNOC command to the end-device. This command has a command field named CaseAdminSubject which will be the subject of the default ACL entry after commissioning. So if the commissioner set this command field to a node ID of CAT range(0xFFFF_FFFD_XXXX_XXXX). All the nodes with the NOC of that CAT will be able to access the end-device. So the only thing that you need to do is to assign an NOC of that CAT to your controller. You do not need to change the ACLs of the end-devices.
image

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

No branches or pull requests

2 participants