History

JianBo He a132df5568 fix(coap): to better handle coap requests in connection mode Fixes for connection deletion and message publishing requests not taking effect issues once the connection has been created in a different UDP port first.		2023-05-30 21:48:57 +08:00
..
doc	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
include	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
src	fix(coap): to better handle coap requests in connection mode	2023-05-30 21:48:57 +08:00
test	refactor: move emqx_json to emqx_utils_json	2023-04-14 13:31:27 +02:00
.gitignore	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
README.md	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
rebar.config	refactor: move emqx_json to emqx_utils_json	2023-04-14 13:31:27 +02:00

README.md

emqx_coap

The CoAP gateway implements publish, subscribe, and receive messages as standard with Publish-Subscribe Broker for the CoAP.

Quick Start

In EMQX 5.0, CoAP gateways can be configured and enabled through the Dashboard.

It can also be enabled via the HTTP API or emqx.conf, e.g. In emqx.conf:

gateway.coap {

  mountpoint = "coap/"

  connection_required = false

  listeners.udp.default {
    bind = "5683"
    max_connections = 1024000
    max_conn_rate = 1000
  }
}

Note: Configuring the gateway via emqx.conf requires changes on a per-node basis, but configuring it via Dashboard or the HTTP API will take effect across the cluster.