-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Set valid device types for application endpoints #13634
Set valid device types for application endpoints #13634
Conversation
3357b35
to
abdd0c7
Compare
examples/all-clusters-app/all-clusters-common/all-clusters-app.matter
Outdated
Show resolved
Hide resolved
@mspang - please update the generated files - I think you picked up the 'unstable run' version of zap output :( |
PR #13634: Size comparison from 8952d1c to abdd0c7 Decreases (3 builds for p6, qpg, telink)
Full report (11 builds for k32w, linux, p6, qpg, telink)
|
abdd0c7
to
a18b711
Compare
Re: all-clusters, the menu system seems to indicate that there should be more endpoints than there actually are. There is definitely more cleanup needed for this application. |
PR #13634: Size comparison from 8952d1c to a18b711 Full report (30 builds for efr32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Several samples are using the root node device type for application endpoints. This prevents proper identification of the device. Add types to all non-root endpoints in examples/. all-clusters-app does not correspond well with any single device type. This sets it to on/off light. It may be useful to reorganize this sample into additional endpoints each with a coherent device type. Multiple root nodes is not compliant. From the spec, "Endpoint Composition" section: There SHALL be only one root node endpoint for the node.
a1ef5d6
to
48a7eab
Compare
PR #13634: Size comparison from 78a6636 to 48a7eab Increases (1 build for esp32)
Decreases (1 build for esp32)
Full report (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
PR #13634: Size comparison from d5e7431 to a9388a1 Increases (1 build for esp32)
Decreases (1 build for esp32)
Full report (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Several samples are using the root node device type for application endpoints. This prevents proper identification of the device. Add types to all non-root endpoints in examples/. all-clusters-app does not correspond well with any single device type. This sets it to on/off light. It may be useful to reorganize this sample into additional endpoints each with a coherent device type. Multiple root nodes is not compliant. From the spec, "Endpoint Composition" section: There SHALL be only one root node endpoint for the node.
Several samples are using the root node device type for application endpoints. This prevents proper identification of the device. Add types to all non-root endpoints in examples/. all-clusters-app does not correspond well with any single device type. This sets it to on/off light. It may be useful to reorganize this sample into additional endpoints each with a coherent device type. Multiple root nodes is not compliant. From the spec, "Endpoint Composition" section: There SHALL be only one root node endpoint for the node. (cherry picked from commit a3409d6)
Several samples are using the root node device type for application endpoints. This prevents proper identification of the device. Add types to all non-root endpoints in examples/. all-clusters-app does not correspond well with any single device type. This sets it to on/off light. It may be useful to reorganize this sample into additional endpoints each with a coherent device type. Multiple root nodes is not compliant. From the spec, "Endpoint Composition" section: There SHALL be only one root node endpoint for the node. (cherry picked from commit a3409d6)
Problem
Several samples are using the root node device type for application
endpoints. This prevents proper identification of the device and is
not compliant with the specification:
From the spec, "Endpoint Composition" section: There SHALL be only
one root node endpoint for the node.
Change overview
Add types to all non-root endpoints in examples/.
all-clusters-app does not correspond well with any single device type.
This sets it to on/off light. It may be useful to reorganize this
sample into additional endpoints each with a coherent device type.
Testing
Built & commissioned each app, read descriptor cluster.