| Re: [wakaama-dev] Leshan server communicating with a Wakaama client - 4_06 NOT ACCEPTABLE error |
Hi, Do not worry, Leshan Servers and wakaama Clients communicate with each others every day both in test and deployed systems. The wakaama payload you quote ‘FF 31’ is a text encoding of the value ‘1’ The Leshan payload ‘FF C1 01 31’ is the TLV encoding of the value 49 of a resource with ID 1. ( see section 6.4.3 of the LwM2M Specification http://www.openmobilealliance.org/release/LightweightM2M/V1_0-20170208-A/). Regarding the 4_06 NOT ACCEPTABLE error, we’d need to know which resource you are trying to write. Apparently, it is not in the expected range. Regards, David Navarro De : wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] De la part de Brady, John 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 -------------------------------------------------------------- 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. |