I am looking to design a cloud connected matter Window Covering Controller device that can individually control a variable amount of matter Window Covering devices. How would this be achievable? I have a few ideas, but I am unsure of how this can be implemented or if it is even possible with the Matter SDK today. Please let me know which one of these makes the most sense and if it is achievable with the nRF52840 chipset.
A) A single Window Covering Controller endpoint with multiple bindings. A Matter controller application would need to bind this endpoint with every new Matter Window Covering that is commissioned and on-boarded.
- Would this allow for the Window Covering Controller to individually control multiple Window Covering endpoints individually, or would they all be grouped together?
B) Multiple Window Covering Controller endpoints. This would require dynamic endpoints like a matter bridge, but instead of server endpoints they would be client endpoints. Each endpoint would be bound to a separate Matter Window Covering on the network using the Matter controller application.
- Are multiple client endpoints of the same type supported in the SDK?
C) A dynamic device type with a dynamic endpoint. This is vaguely defined in the matter core specification (7.15.3.4. Dynamic Device Type). It specifically calls out use of external agents like the cloud that are used to manage relationships. From what I gather it is an endpoint that can change what client clusters it contains.
- This idea is the foggiest to me. I don't know exactly how it works or if it could even be supported by the Matter SDK at this point. Any clarity on this device type would be apreciated.
