Periodic reporting of device information to a map via MQTT #3365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
caveman99
requested changes
Mar 10, 2024
caveman99
approved these changes
Mar 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds an easy way to periodically report all kinds of information about the device (long/short name, position with precision, firmware version, LoRa settings, number of local online nodes, etc.) to a map via MQTT only, regardless of any channel and is thus unencrypted. It will be published to a new
/2/map/topic as a protobuf in aServiceEnvelopewithMeshPacketportnumMAP_REPORT_APPand can be decoded using the newMapReportmessage.If map reporting is enabled, the publish interval (default is 15 min.) and position precision (default is full precision) can be configured.
Implements #3336.