Hey @moritzholzer, thanks for working on this!

For an easier reviewing process, I'd suggest you try to squash unnecessary commits (e.g., the merges). Please, make sure you check our commit conventions https://github.com/RIOT-OS/RIOT/blob/master/CONTRIBUTING.md#commit-conventions

Regarding the version bump, do you know whether there are plans from Wakaama on releasing a version 2.0? With this update, which is the highest LwM2M version that is supported?

I wil squash the commits later.

The lwm2m version is 1.0, some features 1.1.
See Which LWM2M version Wakaama Client supports?

From what i can get from the issues in the wakaama repo there is not a fixed plan for a new version but it was discussed in the past without an conclusion.

I'v worked through the comments.

I tested it on native and works well

Murdock results

✔️ PASSED

97acd2e examples/lwm2m: changes on example application

Artifacts

• Documentation preview

There seems to be a problem with a printf on object_server.c. Check the CI output

You may want to remove the Makefile.ci and run make generate-Makefile.ci in the example (IT TAKES SOME TIME) to exclude boards that can't fit the application anymore.

Looks good. There's only one style comment pending. Please squash directly, so that we keep only meaningful commits in the history.

Is it enought squashed or are less commits better?

Thanks @moritzholzer. I think there are some mix ups on the commit history. I see, for example, various changes of the pkg version? (ec5d90f and e0fe270)

I would suggest having the following commits:

• version bump (updates on pkg makefiles, updates of the patches)
• changes on config and OS services (addition of random seed, Kconfig)
• adaption of contrib to new interface (changes on our object implementations and their docs)
• changes on example application

Also please check the messages. They should always start with the area of changes (e.g., pkg/wakaama, examples/lwm2m). Also, we use present tense. If you want to elaborate on large changes, do so by leaving a blank line after the short description.

Thank you @leandrolanzieri for the help:)
I did my best to restructure the commits.

@moritzholzer there are some whitespace errors (see https://github.com/RIOT-OS/RIOT/actions/runs/11609350032/job/32530338557?pr=20930)

I removed the whitespaces.

Before the merge queue triggers a timeout, I'll drop and requeue this one.