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
Read Composite with the overlapping path is not possible
We know that there was discussion but we need it for ETS (LightweightM2M-1.1-int-229)
How to reproduce
Preconditions:
The Client supports Configuration C.1 as defined in Annex C
The client is registered with the L2M2M Server
The client supports mandatory resources of Lw2M2M Server and Device Objects
Test Procedure:
Server performs a Read-Composite (CoAP FETCH) on the following combination of Objects, Object Instances, Resources, and Resources Instances:
Device Object (/3)
L2M2M Server Object Instance (/1/x, where x in a LwM2M Server Object Instance)
Lifetime Resource (/1/x/1)
Error Code Resource Instance (/3/0/11/0)
"Accept: Content-format" is set either to SenML CBOR or SenML JSON
Pass-Criteria:
A. Client accepted the request and replied with 2.05 Content. Message payload contains requested data. The content format is either: SenML CBOR or SenML JSON
supports
Relevant Output
No response
The text was updated successfully, but these errors were encountered:
This use case still doesn't make sense to me. Why reading /1/x and 1/x/1 as 1/x/1 is include in /1/x ? In real life what is the use case for this ?
Not sure but I will not be surprised this is rather a bug in ETS draft OR at least a not so good idea to use this corner case for an interoperability test.
AVSystem, IoTerop and 6D Tech LwM2M Server implementation of ETS 229 are suporting Read Composite with the overlapping paths, as-is, since the status is "passed" with some clients (for example Paradox client)
Version(s)
v2.0.0-M11
Which components
Client and Server
Tested With
No response
What happened
Read Composite with the overlapping path is not possible
We know that there was discussion but we need it for ETS (LightweightM2M-1.1-int-229)
How to reproduce
Preconditions:
The Client supports Configuration C.1 as defined in Annex C
The client is registered with the L2M2M Server
The client supports mandatory resources of Lw2M2M Server and Device Objects
Test Procedure:
Device Object (/3)
L2M2M Server Object Instance (/1/x, where x in a LwM2M Server Object Instance)
Lifetime Resource (/1/x/1)
Error Code Resource Instance (/3/0/11/0)
"Accept: Content-format" is set either to SenML CBOR or SenML JSON
Pass-Criteria:
A. Client accepted the request and replied with 2.05 Content. Message payload contains requested data. The content format is either: SenML CBOR or SenML JSON
supports
Relevant Output
No response
The text was updated successfully, but these errors were encountered: