Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wakaama-dev] Leshan server communicating with a Wakaama client - 4_06 NOT ACCEPTABLE error

Hi,

 

In my experience this is mainly related to the content format (CoAP Option 12).

Wakaama server seems to use text, leshan TLV.

The LWM2M TS has seen some clarification on that.

So could you provide the information, which content format option was used?

 

Mit freundlichen Grüßen / Best regards

Achim Kraus

(INST/ECS4)
Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY
| www.bosch-si.com


Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Geschäftsführung: Dr.-Ing.
Rainer Kallenbach, Michael Hahn



From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Brady, John
Sent: Dienstag, 30. Mai 2017 10:29
To: wakaama-dev@xxxxxxxxxxx
Cc: Coates, DavidX <davidx.coates@xxxxxxxxx>; Nolan, Michael <michael.nolan@xxxxxxxxx>
Subject: [wakaama-dev] Leshan server communicating with a Wakaama client - 4_06 NOT ACCEPTABLE error

 

Hi Folks,

 

Has anybody managed to have a Leshan server communicating with a Wakaama client?

 

After the one-byte Payload Marker (0xFF) the Wakaama server only sends the payload e.g. ‘FF 31’ – when sending the client a resource value of `1`.    

 

The Leshan server seems to send a ‘header’ within the payload. Taking the same example, sending the client a resource value of `1` to the Wakaama client, it would display ‘FF C1 01 31’ as the payload in the wakaama client console. The Wakaama client responds with a 4_06 NOT ACCEPTABLE error.

 

Does anybody know what these bytes represent and a workaround to have a Leshan server communicating with a Wakaama client?

 

Many thanks

John

 

--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.


Back to the top