|
|
1 год назад | |
|---|---|---|
| .. | ||
| doc | 0a62d6c556 refactor(gw): rename all gateway application name | 2 лет назад |
| include | 52f0f403f3 fix(coap): Fixed that incorrect sub-options were displayed in CoAP gateways | 1 год назад |
| src | 40036895e4 fix: add handle_frame_error/2 to all gateway implementations | 1 год назад |
| test | ec183f1d4c test(coap): fix ci errors | 1 год назад |
| .gitignore | 0a62d6c556 refactor(gw): rename all gateway application name | 2 лет назад |
| README.md | 25e277bdc6 chore: fix schema desc and README.md typo | 2 лет назад |
| mix.exs | 19f3b030f9 chore: preparing to run common tests / eunit with mix | 1 год назад |
| rebar.config | 5e100f52b8 style: erlfmt all `rebar.config` files and `bin/nodetool` | 2 лет назад |
The CoAP gateway implements publish, subscribe, and receive messages as standard with Publish-Subscribe Broker for the CoAP.
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.
More documentations: CoAP Gateway