AlCalzone

This is the first issue on the roadmap to fully support RFC 7959. Receiving fragmented messages is being worked on in #22 so it would be nice to being able...

Support specifying a preferred block size for server responses

1

As defined in https://tools.ietf.org/html/rfc7959#section-2.4, clients can specify a preferred block size for the responses from the CoAP server by using the `Block2` option on a request. This size should be...

When receiving a response (block-wise or not) from the server, containing the `Block1` option, we should remember it for future requests.

When #22 is merged, only a basic implementation of RFC 7959 exists. Inside `CoapClient.onMessage` we should check if the correct (i.e. the requested) message fragment was received and if the...

Requires https://github.com/AlCalzone/node-tradfri-client/issues/102 to be resolved first. Fixes #57

```log 2021-01-20 18:01:15.644 - debug: tradfri.0 (7332) {{blue}} state with id tradfri.0.info.connection updated: ack=true; val=true 2021-01-20 18:01:15.844 - info: tradfri.0 (7332) got all devices: [65536,65538,65537] 2021-01-20 18:01:15.845 - debug: tradfri.0...

See https://forum.iobroker.net/viewtopic.php?p=170563#p170563

See discussion in #40