| Re: [wakaama-dev] Write method format issue |
|
Hello, just my first answer: 1. the screenshot shows:
Opt Count: 0
But there are options (at least the uri) shown as payload. (02 31 31 for the „11“ in the uri, followed by ff for the payload). (May be your Wireshark is “old”. Which version do you use?) 2. /1024/11 is a object instance. What should the object instance do with the text “foobar”? That doesn’t make sense. Could you therefore try to test write 0 /1024/11/1 49 What is your result? Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ESY4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn Von: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Alexandru Razvan Caciulescu Hello, We are trying to integrate LWM2M with RIOT-OS and we are currently using the Wakaama code as a starting point. While following the client/server example provided by wakaama we are experimenting with the Write method unsuccessfully and we
noticed something strange in the actual payload of the coap packets in wireshark. The command we used : write 0 /1024/11 foobar besides the "foobar" string the payload does contain some additional bytes which are not part of a TLV encoding as the client expects them, thus resulting in an "internal server error". Does the Write method expect the payload to be directly given in a TLV encoded string ? Or which would be the correct way to use the Write method in this case? Thank you, Alexandru Caciulescu |