|
|
před 2 roky | |
|---|---|---|
| .. | ||
| doc | 0a62d6c556 refactor(gw): rename all gateway application name | před 2 roky |
| include | 0a62d6c556 refactor(gw): rename all gateway application name | před 2 roky |
| src | 780ca15298 chore: bump application versions | před 2 roky |
| test | 1ce6a225ae feat(authz): add tests for authz extended actions | před 2 roky |
| .gitignore | 0a62d6c556 refactor(gw): rename all gateway application name | před 2 roky |
| README.md | 0a62d6c556 refactor(gw): rename all gateway application name | před 2 roky |
| rebar.config | f8e9e54393 refactor: move emqx_json to emqx_utils_json | před 2 roky |
The CoAP gateway implements publish, subscribe, and receive messages as standard with Publish-Subscribe Broker for the CoAP.
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.
More documentations: CoAP Gateway