Hi,
The content-format is set for all replies with a payload. Are you up-to-date on wakaama sources ?
If so, please provide us some logs in a GitHub issue.
Thanks,
David Navarro
From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
On Behalf Of Riccardo Pozza
Sent: Wednesday, 28 September, 2016 13:05
To: 'Wakaama developer discussions' <wakaama-dev@xxxxxxxxxxx>
Subject: [wakaama-dev] FW: [leshan-dev] Leshan Update from M11-M13
Hi all,
I have an issue with Leshan Server (please see mail thread below).
Basically I updated it and now it can’t decode anymore unless I set the content format in the Wakaama Client responses.
How can I force/set this in Wakaama?
Thanks a lot for any help,
Kind Regards,
Riccardo.
Hi Ricardo,
In M13 there was an incompatible change (from LWM2M client prespective) introduced regarding decoding
here. All LWM2M
client MUST specify the content format in its response. This requirement is as per latest LWM2M Spec. I am not sure of Wakaama code. I think it is not setting the content format in its response to your read requests.
If you can set the content format in your responses then it should work.
Hope it helps.
Regards,
Bala
Dear all,
Just trying to update Leshan Server from M11 to M13.
I haven’t change anything on my Wakaama Client but with the new server I get a lot of “400 Validated object is null”, especially when reading the 1/0, 2/0, … resources, but not only in such cases.
Has anyone else seen the same issue?
Is there something I need to change in the configuration (or in the client itself)?
Thanks a lot for any help,
Kind Regards,
Riccardo.