From 63031118380b9c0ae6dd0591ebdf0c318ecfd6a5 Mon Sep 17 00:00:00 2001 From: DSikes Date: Wed, 18 Sep 2024 20:21:30 -0400 Subject: [PATCH 1/3] 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. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 964b8f1..2514bed 100644 --- a/README.md +++ b/README.md @@ -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. From 2fbea487c1595f11dfa3da3d9d2e031c40bba06d Mon Sep 17 00:00:00 2001 From: DSikes Date: Thu, 19 Sep 2024 07:34:31 -0400 Subject: [PATCH 2/3] 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 --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2514bed..b75b912 100644 --- a/README.md +++ b/README.md @@ -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 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. From acd1de01691305d90948b7b21d5247777f3563ca Mon Sep 17 00:00:00 2001 From: DSikes Date: Thu, 19 Sep 2024 12:23:34 -0400 Subject: [PATCH 3/3] Keep this line a quote in README.md Co-authored-by: Brian Shea <165865819+brianshea2@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b75b912..c151af4 100644 --- a/README.md +++ b/README.md @@ -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. The most accurate resolution that conforms to this specification is: 364 meters/1194 feet.