You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specification for Read and Subscribe define the Conformance for DataVersionFilter as "Mandatory if AttributeRequests exists" and same for the EventReports for the EventRequests.
When I know correctly how it is requested by common controllers these days (verified with Apple and Google for Read) - and so must be implemented that way in chip? - then the conformance for DataVersionFilter and EventFilters should be more "optional if other field is set", so more like "[AttributeRequests]" instead "AttributeRequests".
In fact the Message definitionis in e.g. 10.7.2 mark the fields as "optional", should then not also the model details have that?
Platform
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Documentation issues
The specification for Read and Subscribe define the Conformance for DataVersionFilter as "Mandatory if AttributeRequests exists" and same for the EventReports for the EventRequests.
When I know correctly how it is requested by common controllers these days (verified with Apple and Google for Read) - and so must be implemented that way in chip? - then the conformance for DataVersionFilter and EventFilters should be more "optional if other field is set", so more like "[AttributeRequests]" instead "AttributeRequests".
In fact the Message definitionis in e.g. 10.7.2 mark the fields as "optional", should then not also the model details have that?
Platform
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: