History

Ilya Averyanov 80d724c504 feat(authn): add connection expire based on authn data		2024-04-30 17:04:55 +03:00
..
doc	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
include	chore: update copyright-year	2024-02-23 08:21:06 +01:00
src	feat(authn): add connection expire based on authn data	2024-04-30 17:04:55 +03:00
test	feat(authn): add connection expire based on authn data	2024-04-30 17:04:55 +03:00
.gitignore	refactor(gw): rename all gateway application name	2023-04-13 14:53:47 +08:00
README.md	chore: fix schema desc and README.md typo	2023-11-12 21:43:10 +08:00
rebar.config	style: erlfmt all `rebar.config` files and `bin/nodetool`	2023-12-29 09:08:03 +08: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 gateway 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.