Indeed.
Single instance objects must declare the “0” instance anyway. This is an easy fix for current objects. I’m on it.
Regards,
David Navarro
From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kraus Achim (INST/ESY4)
Sent: Friday, 27 February, 2015 14:12
To: wakaama-dev@xxxxxxxxxxx
Subject: [wakaama-dev] registration list of object and instances
Hi all,
The current implementation of the test client cause an issue in the registration.
According LWM2M TS, 5.2.1, objects are listed as “/<oid>“ and already available object instances as “/<oid>/<iid>”.
But the current test client implementation for “single” objects mislead the “getRegisterPayload” function to interpret the empty “instanceList” as “no available instances”.
This results in
objects: /1/0, /3, /4, /5, /6, /1024/10, /1024/11, /1024/12,
instead
objects: /1/0, /3/0, /4/0, /5/0, /6/0, /1024/10, /1024/11, /1024/12,
So, are there any points against using instances also for “single” objects to fix the registration payload?
Or are there different interpretation of the register specification?
Mit freundlichen Grüßen / Best regards
Achim Kraus
Bosch Software Innovations GmbH
Communications (INST/ESY4)
Stuttgarter Straße 130
71332 Waiblingen
GERMANY
www.bosch-si.de
www.blog.bosch-si.com
achim.kraus@xxxxxxxxxxxx
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn