mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-01-14 07:20:44 -08:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

Merge pull request #873 from pdxlocations/mqtt-image

Browse source 
Add MQTT Network Example Image
This commit is contained in:
rcarteraz 2023-11-10 11:24:00 -07:00 committed by GitHub
parent bbc30f1a7f b740058b41
commit 9f3d893610
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/software/mqtt/index.mdx
View file

@ -7,6 +7,8 @@ sidebar_position: 6
## Bridging networks
![Common MQTT Layout](/img/software/mqtt/mqtt.png)
Meshtastic networks in different locations beyond the reach of LoRa can be easily bridged together using MQTT. The simplest option is to connect your mesh to the official Meshtastic MQTT broker. This makes your devices appear on the world map, and provides a copy of your mesh traffic, translated into JSON. All you have to do to join the public MQTT server is to Enable MQTT and set Uplink and Downlink on the channels that you want to share over MQTT. The default device configuration using the public MQTT Server is encrypted.
You can also share channel settings with a remote network. If you use the default Meshtastic MQTT server, packets are always encrypted. If you use a custom MQTT broker (ie set `mqtt.address`), the `mqtt.encryption_enabled` setting applies, which by default is false. You can also specify your own private MQTT broker and specify authentication for that broker to bridge several mesh networks together, via the internet (or just a local IP network).

BIN
static/img/software/mqtt/mqtt.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 315 KiB