The official Widgets Development Guide only contains the most basic widget types as example.

There is no functional example for a Flot chart in there right now. Or is it?

Since this is one of the most useful and probably used (at leat to me) widgets it would be very helpful to extend that docum

Environment

• OS: RHEL 7.6
• Erlang/OTP:
• EMQ: 2.3.11

Description

I am using:

NIGINX --> Docker --> custom image with EMQ installed ( same host, SSL offload on nginx)

EMQ works and clients can connect but i see continous multiple crashes/proxy errors in the error.log

2019-08-27 12:12:31.287 [error] <0.11973.534> CRASH REPORT Process <0.11973.534> with 0 neighbou

FEATURE REQUEST

1. Is there an open issue addressing this request? If it does, please add a "+1" reaction to the
   existing issue, otherwise proceed to step 2.
   No.

2. Describe the feature you are requesting, as well as the possible use case(s) for it.
   After adding open tracing support to the existing gRPC and HTTP endpoints in Users and Things service, we should add support for t

When setting the monitor.tail property, it's possible to tail/update only filenames, and not directories:

https://github.com/Landoop/stream-reactor/blob/master/kafka-connect-ftp/src/main/scala/com/datamountaineer/streamreactor/connect/ftp/source/FtpFileLister.scala#L41

So, when a support for a recursive structure is required, it can be done in a way like this:
`connect.ftp.monitor.tail=/**:

While searching I came across
--> Tutorial slides
--> Master's thesis: Scalability for IoT Cloud Services
on http://people.inf.ethz.ch/mkovatsc/californium.php

Is there any other documentation much like a developer manual?

It would be good if we can have an option to perform write attribute on the demo server code, with operations Minimum Period, Maximum Period, Greater Than, Less Than, and Step.

Is there an usage example for OSCORE clien/server similar to the standard CoAP client/server examples here: https://aiocoap.readthedocs.io/en/latest/examples.html

pDescription may be null and causes a hard-fault when observers are notified of a resource update.
https://github.com/Lobaro/lobaro-coap/blob/b6b5ced0f7d013022c848d5f3da4ddb757339b6c/src/coap_interaction.c#L279

It's set to NULL when an null or empty string is passed in as a resource description on CoAP_CreateResource:
https://github.com/Lobaro/lobaro-coap/blob/d7a4c79ad2217f744ac9757d2b4b

The primary reason to do this is to assist porting Awa to other platforms.
A secondary reason is to improve testing and reliability of the network abstraction layer and dtls layer.

Hello,
would it be possible to add a small example that explains the request routing in the server and acceding to an appropriate handler for a given URI path.

Currently we have this: https://github.com/gotthardp/gen_coap/blob/master/examples/src/sample_server.erl, and we can figure out if the type of req was GET, POST, PUT, ..., but I see no information how we parse URL string and based on th

All activities and triggers need to be reviewed, documented and readme updates.