-
Notifications
You must be signed in to change notification settings - Fork 153
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
Matter Certification Help built with Sample application (CON-1335) #1083
Comments
@dhrishi Hi, we are already able to add everything related to certification available on this link: I just wanted to ask if we need to add anything else related to mandatory clusters or others in application, we built our light device using light sample available in esp-matter sdk. |
@bilalmalik76 It is advisable to execute the certification tests at your end before you send the products to the ATL |
@dhrishi Ok I will do but generally when we build using based solution, we add missing core clusters but what is difference with esp-matter considering it uses models and wrappers on top of connected home ip stack. can you give general idea if sample has all core clusters already implemented required for matter light? |
@bilalmalik76 Ideally the mandatory clusters (core and application) should be present for a selected device types. So, you need not require anything in there. If there are any specific issues that you observe, you can raise then and we will fix :-) |
@dhrishi Sure I will start executing certification tests and raise issues if face any. Thanks |
Are there additional implementations required to be added to the samples other than factory data for Matter certification? For example, we have built a matter light using one of the samples available in esp-matter sdk and added our factory data using our official PID, etc. We are able to comission device and control it from Google and Apple home apps. What else is required for certification before we send our device to ATL?
The text was updated successfully, but these errors were encountered: