Skip to content

Releases: insighio/microCoAPy

v0.5.1

26 Feb 08:39
8913869
Compare
Choose a tag to compare

Enhancements

  • Allow using this library on system without usocket module (merged PR #12 by @przemobe )

v0.5.0

03 Feb 16:39
703f4c7
Compare
Choose a tag to compare

New Features:

v0.4.0

13 Nov 14:00
Compare
Choose a tag to compare

Bug fixing:

  • more transparent usage of custom sockets (if enabled). Socket function arguments comply now to the typical socket usage.

Enhancements:

  • Added new examples with custom socket usage.
  • Updated README files.

v0.3.0

30 Mar 08:58
Compare
Choose a tag to compare

New Features:

  • Added "non confirmable" versions of GET, PUT, POST
  • Add option to disable library debug output.
  • Support discard of incoming retransmission (optional)

Bug fixes:

  • Fix return status of poll function
  • Fix typo of boolean when server is enabled

Updated README file.

v0.2.0

17 Mar 17:39
Compare
Choose a tag to compare

New Features:

  • Support Separate response rfc7252 - 5.2.2
  • Support Custom sockets
  • Support of ESP8266
  • added toString function for Coap Packets for convenience

Bug fixes:

  • Fix respect of timeout in poll function
  • Clear separation of Client/Server incoming message handling
  • Properly pass Packet Token in the NOT_FOUND response when received incoming request but no Url Callback is defined.
  • Updated examples to properly handle Packet Token

Code refactoring:

  • Minimize imports per file to optimize memory usage (essential for ESP8266)

New examples for ESP32 / ESP8266

Updated README file.

v0.1.0

31 Oct 14:09
Compare
Choose a tag to compare

The first release brings the following features:

  • CoAP client
    • PUT
    • POST
    • GET
  • CoAP server
  • Example for Pycom device

Mutable properties when sending a packet

  • IP : The IP of the receiving end
  • Port : The listening port of the receiving end
  • URL: The URL path used in the CoAP request
  • Method: The request type: GET, PUT, POST, DELETE
  • Payload: The actual payload to be transferred. The format of the payload is defined at "Content Type"
  • Content Type: format of the "Payload"
  • Query Option: Extra parameters added on the request's URI following the URL query format