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

General question for Enhanced Multi-Admin (CON-1606) #1335

Open
simonFloat opened this issue Mar 19, 2025 · 0 comments
Open

General question for Enhanced Multi-Admin (CON-1606) #1335

simonFloat opened this issue Mar 19, 2025 · 0 comments

Comments

@simonFloat
Copy link

Can Joint Fabrics be used to commission a device in as an administrator?

I was reading the new Matter Specification 1.4 and came across the Joint Fabrics, and was wondering if it's a good way to add more administrators into a Fabric?

Im looking into finding a good way of commissioning a device into a Fabric and allow the Device permissions to read all information in the Fabric to sort of act as a "monitor" and potentially also control some devices to certain extends. I found that modifying specific permissions is not that suitable, as different ecosystems didn't seem to have options for this.
So I was wondering if the best way is for the Device to be commissioned into a Fabric and have a TXT key stating it will act as a Joint Fabric Administrator.

I must admit the Specification is hard for me to fully comprehend, so any clarification would be much appreciated!

Thanks in advance.

@github-actions github-actions bot changed the title Enhanced Multi-Admin Enhanced Multi-Admin (CON-1606) Mar 19, 2025
@simonFloat simonFloat changed the title Enhanced Multi-Admin (CON-1606) General question for Enhanced Multi-Admin Mar 19, 2025
@simonFloat simonFloat changed the title General question for Enhanced Multi-Admin General question for Enhanced Multi-Admin (CON-1606) Mar 19, 2025
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

1 participant