mudhorn/meshmap.net
1
0
Fork 0
mirror of https://github.com/brianshea2/meshmap.net.git synced 2025-03-05 21:00:01 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Compare commits

base: mudhorn:6d4c55305ea11b8fa1dd45d468196934221833d7
Branches Tags
mudhorn:main
...
compare: mudhorn:e7b91c37943acd3fac7cd10a670a463506261cab
Branches Tags
mudhorn:main

2 commits
6d4c55305e ... e7b91c3794

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
1 changed files with 1 additions and 1 deletions
Show stats Expand all files Collapse all files

2
README.md
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
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.