Compare commits

...

2 commits

Author SHA1 Message Date
DSikes e7b91c3794
Merge 6303111838 into a782f28231 2024-09-18 21:46:58 -04:00
DSikes 6303111838
Add maximum resolution note to location accuracy notice
I had to look up what the setting was allowed to be, so I figured I'd relay that information where it may be useful.
2024-09-18 20:21:30 -04:00

View file

@ -22,7 +22,7 @@ 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. > 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.)
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.