Add QMP6988 telemetry sensor type#921
Open
mokjpn wants to merge 1 commit into
Open
Conversation
This was referenced May 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do?
Adds a new
QMP6988value toTelemetrySensorTypeon the protobufsdevelopbaseline used by current meshtastic/firmware.This is needed for firmware support of the QMP6988 environmental sensor. The corresponding firmware work uses this enum value to identify QMP6988 explicitly in telemetry, and firmware generated sources should be regenerated from this protobuf change rather than patched by hand.
Related:
This replaces #899, which was closed because it was based on
masterand would roll backdevelop-only protobuf changes such as the NodeDB split when used for firmware regeneration.Checklist before merging