History

Thales Macedo Garitezi 7ca5205f3f feat: add `peername` to rule events that already have `peerhost` Fixes https://emqx.atlassian.net/browse/EMQX-12342		2024-07-22 16:01:30 -03:00
..
doc	docs(gw_jt808): fix and reformat data exchange guide	2023-12-18 03:21:49 +08:00
include	chore: update copyright-year	2024-02-23 08:21:06 +01:00
src	feat: add `peername` to rule events that already have `peerhost`	2024-07-22 16:01:30 -03:00
test	test(gw): jt808 register failed	2024-05-10 23:09:22 +08:00
.gitignore	feat(gw_jt808): port jt808 gateway from 4.4	2023-11-12 21:44:18 +08:00
BSL.txt	chore: update BSL license change date	2024-01-29 16:47:31 +01:00
README.md	feat(gw_jt808): port jt808 gateway from 4.4	2023-11-12 21:44:18 +08:00
mix.exs	chore: preparing to run common tests / eunit with mix	2024-07-02 09:45:45 -03:00
rebar.config	style: erlfmt all `rebar.config` files and `bin/nodetool`	2023-12-29 09:08:03 +08:00

README.md

emqx_jt808

The JT/T 808 protocol is designed for data interaction between vehicle-mounted satellite terminals and IoT platforms.

The JT/T 808 Gateway in EMQX can accept JT/T 808 clients and translate their events and messages into MQTT Publish messages.

In the current implementation, it has the following limitations:

Only supports JT/T 808-2013 protocol, JT/T 808-2019 is not supported yet.
Based TCP/TLS transport.
Third-party authentication/registration http service required.

Quick Start

In EMQX 5.0, JT/T 808 gateway can be configured and enabled through the Dashboard.

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

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.