Comments (5)
@hicklin this is by design. ZAP generally stores all the configurations made by the user into the .zap file in order to retrieve user settings back easily if they want to go back to all the edits made. For eg. user edits a cluster for attributes, commands, etc then by mistake disables the cluster then the user can enable the cluster back and retrieve the changes made. In this case updating the device type on an endpoint does not disable the existing clusters which have been enabled previously since the user may want all those changes. I believe that before you updated the device type to Matter Robotic Vacuum Cleaner, the previous device type had Groups and scenes enabled. I recommend that you delete the endpoint to loose all the configuration on that endpoint and recreate the endpoint with Matter Robotic Vacuum Cleaner device type.
from zap.
@brdandu But should the invalid config not at least be flagged as a warning?
from zap.
@brdandu But should the invalid config not at least be flagged as a warning?
I do not see this to be an invalid config for every use case. I always thought a user can select a device type as a baseline and then add on to the list of clusters coming from the device type for their specific purpose but I see how one could be warned with having a cluster that does not come from your selected device types on that endpoint.
from zap.
I always thought a user can select a device type as a baseline and then add on to the list of clusters coming from the device type for their specific purpose
Matter is moving away from that, because that's not very interoperable. So in general, anything that's not allowed by the device type should be flagged (though perhaps not prevented for now).
from zap.
Matter is moving away from that, because that's not very interoperable. So in general, anything that's not allowed by the device type should be flagged (though perhaps not prevented for now).
Just noticed this thread. This is related to the Feature Request I posted here: #1150 though I have a stronger view that there should be an enforced conformance to the specs.
My view is that there should be no cluster that are not either Mandatory or Optional for the device type. If this isn't the case, then "Optional" in the standard has no meaning as everything becomes Optional and, as prior post pointed out, its an interoperability nightmare that is best avoided. Until Matter controllers have the basics 100% right, less choice can be a benefit.
from zap.
Related Issues (20)
- macOS arm64 release assets damaged and can't be executed HOT 4
- Add Energy management built in types to ZAP tool HOT 3
- Does not generate any files HOT 11
- Add ability to open notifications pane along with the endpoint UI
- "zap convert" and running the ZAP GUI produce different .zap file output HOT 1
- About Profile ID 0x0103 in ZAP tool HOT 1
- ZAP showing warning when enabled and disabled a non required cluster
- ZAP editor should support signed data types
- ZAP bombs out with unhelpful message if derived xml clusters (e.g. xyz-mode-cluster.xml is not in mode-base-cluster.xml) HOT 1
- Add a way to reuse cluster configurations in a form of include files HOT 1
- Compile time error for Struct with isFabricScoped attribute, when Struct is used as command argument type
- Update the CI actions, since they are becoming deprecated
- Disabling optional clusters results in a :red_square: error HOT 1
- How to handle "There are multiple of ZCL metadata loaded. Please select the one you wish to use with this configuration."? HOT 5
- Incorrect warnings about missing clusters for Air Quality? HOT 2
- Rewrite tests using await/async instead of the old .then() patterns
- Features cannot have cluster codes in just like bitmap feature HOT 1
- Open, edit and save a zap file outside the Simplicity Studio environment HOT 1
- types.isFloat is broken HOT 2
- ZAP needs to track endpoint composition types
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zap.