Re: [wakaama-dev] LWM2M 1.1 next steps

[Scott Bertin <Scott.Bertin@xxxxxxxxxx>]

I’ve completed the bootstrap changes on my lwm2m_1.1 branch. I haven’t created pull requests to the Eclipse Wakaama master branch yet because it quickly gets messy. I plan to create the pull requests in a cleaner manner once some existing pull requests have been merged.

 

I plan to implement the Read-Composite and Send operations next.

 

Regards,

Scott Bertin

 

Scott Bertin

Sr Firmware Engineer

P: +1 678-264-2042 | C: | Scott.Bertin@xxxxxxxxxx

3225 Cumberland Boulevard
Suite 300 | Atlanta | GA 30339 | Telular.com

Telular is a Business Unit of AMETEK, Inc.

From: wakaama-dev-bounces@xxxxxxxxxxx <wakaama-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Bertin
Sent: Monday, July 1, 2019 10:50 AM
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] LWM2M 1.1 next steps

 

***NOTICE*** This came from an external source. Use caution when replying, clicking links, or opening attachments.

I can’t keep waiting indefinitely. I’m going to continue working on LWM2M 1.1 support assuming that the following pull requests will be merged as-is:

#423 Improve floating point conversions.

#430 Make TLV format optional.

#431 [Core reorg] Organize source files per area.

#432 Fix potential type size mismatch through pointers

#435 Handle resource instances in Read, Write, and Observe.

 

Upcoming changes will likely build on each other also. I’ll keep my lwm2m_1.1 branch (https://github.com/sbertin-telular/wakaama/tree/lwm2m_1.1) up to date with the changes I work on as well as creating pull requests to https://github.com/eclipse/wakaama if anyone wants to follow along.

 

Regards,

Scott Bertin

 

Scott Bertin

Sr Firmware Engineer

P: +1 678-264-2042 | C: | Scott.Bertin@xxxxxxxxxx

3225 Cumberland Boulevard
Suite 300 | Atlanta | GA 30339 | Telular.com

Telular is a Business Unit of AMETEK, Inc.

From: wakaama-dev-bounces@xxxxxxxxxxx <wakaama-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Bertin
Sent: Tuesday, March 26, 2019 8:59 AM
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] LWM2M 1.1 next steps

 

I’m holding off on the bootstrap changes until some of the existing pull requests can be merged. In particular #430, #431, and #435.

 

Regards,

Scott

 

From: wakaama-dev-bounces@xxxxxxxxxxx <wakaama-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Bertin
Sent: Wednesday, February 20, 2019 1:20 PM
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] LWM2M 1.1 next steps

 

David,

 

1. Yes, LWM2M_SUPPORT_TLV. Also always defined when LWM2M_BOOTSTRAP_SERVER_MODE is defined. Only off by default for LWM2M 1.1 clients. I actually have this ready to go, it took only about an hour. It might have merge conflicts with the SenML JSON support so I was waiting to create the pull request.
2. Actually I think it is mostly client side. The resource instance ID need to be passed to the object read or write function. I think there are TODOs in the code most places that need to change. On the server side I think it would “just work”, but obviously I haven’t tested it yet.
3. Adding the preferred content format to the Bootstrap-Request. Adding the Bootstrap-Read. There are changes to the BootStrap-Discover, but I need to review the details. The server initiated bootstrap is completely different for LWM2M 1.1. Server object resources 9 (Bootstrap-Request Trigger) and 12 (Last Bootstrapped) would probably be part of this, although Last Bootstrapped may not be possible unless the origin for lwm2m_gettime() is Jan 1 1970. I’ll probably break this up into several pull requests to keep it from being too much at once.

 

Regards,

Scott

 

From: wakaama-dev-bounces@xxxxxxxxxxx <wakaama-dev-bounces@xxxxxxxxxxx> On Behalf Of David Navarro - IoTerop
Sent: Wednesday, February 20, 2019 12:29 PM
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] LWM2M 1.1 next steps

 

Hi Scott,

 

1. Remember that TLV is still mandatory to support for the Server. I guess you consider a compilation flag. Like for  LWM2M_SUPPORT_JSON, it should be always defined when LWM2M_SERVER_MODE is defined.

 

2. I guess you are talking of the Server-side APIs. For the Client-side it should “just work” with the new URIs and the data encoding.

 

3. Could you elaborate ? From the top of my mind, there are the Bootstrap-Read operation, the new Bootstrap-Discover parameters, and some new resources in the Server Object.

 

Regards,

David Navarro

 

From: wakaama-dev-bounces@xxxxxxxxxxx <wakaama-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Bertin
Sent: Wednesday, 20 February, 2019 14:54
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: [wakaama-dev] LWM2M 1.1 next steps

 

The next few things I plan on working on are:

1. Making TLV support optional.
2. Expanding read/write/observe to handle resource instances.
3. Bootstrap changes.

 

Regards,

Scott

 

Scott Bertin
Senior Firmware Engineer

D: 678.264.2042 | F: 678.264.2082 | sbertin@xxxxxxxxxxx 


Telular is a Business Unit of AMETEK, Inc.