mirror of
https://github.com/brianshea2/meshmap.net.git
synced 2025-02-02 08:42:28 -08:00
parent
5aeeb3e499
commit
b5ab26a8c2
|
@ -21,11 +21,15 @@ If your node can be heard by another node already reporting to MQTT, that's it!
|
|||
|
||||
#### Important update as of August, 2024
|
||||
Meshtastic has [made a change to their MQTT server](https://meshtastic.org/blog/recent-public-mqtt-broker-changes/):
|
||||
|
||||
> Only position packets with imprecise location information [10-16 bits] will be passed to the topic, ensuring that sensitive data is not exposed.
|
||||
|
||||
Additionally, only the default [LoRa region](https://meshtastic.org/docs/configuration/radio/lora/#region)-based root topics (and all subtopics) are now monitored.
|
||||
|
||||
#### To enable MQTT reporting
|
||||
- Enable the MQTT module, using all default settings, possibly with a custom root topic
|
||||
- View nodes around your area on the map to find MQTT topics being used
|
||||
- Only the official [LoRa region](https://meshtastic.org/docs/configuration/radio/lora/#region)-based root topics (and all subtopics) are monitored
|
||||
- Configure your node to connect to wifi or otherwise connect to the internet
|
||||
- Enable MQTT uplink on your primary channel
|
||||
- It is not necessary, and not recommended unless you know what you're doing, to enable MQTT downlink
|
||||
|
|
Loading…
Reference in a new issue