Compare commits

..

2 commits

Author SHA1 Message Date
DSikes 6d4c55305e
Merge 2fbea487c1 into a782f28231 2024-09-19 07:34:40 -04:00
DSikes 2fbea487c1
Reformatted resolution note in readme
Per maintainers request, moved the resolution note for the most accurate resolution available that matches the new Meshtastic specification for sharing location to its own line
2024-09-19 07:34:31 -04:00

View file

@ -22,7 +22,9 @@ If your node can be heard by another node already reporting to MQTT, that's it!
#### Important update as of August, 2024 #### Important update as of August, 2024
Meshtastic has [made a change to their MQTT server](https://meshtastic.org/blog/recent-public-mqtt-broker-changes/): 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. (364 Meters/1194 Feet is the most accurate resolution allowed.) Only position packets with imprecise location information [10-16 bits] will be passed to the topic, ensuring that sensitive data is not exposed.
The most accurate resolution that conforms to this specification is: 364 meters/1194 feet.
Additionally, only the default [LoRa region](https://meshtastic.org/docs/configuration/radio/lora/#region)-based root topics (and all subtopics) are now monitored. Additionally, only the default [LoRa region](https://meshtastic.org/docs/configuration/radio/lora/#region)-based root topics (and all subtopics) are now monitored.