Database for telemetry readings #9519
Draft
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 is a proof of concept PR to be elaborated further, but featuring a small database for telemetry. The idea is to create something similar to: https://docs.smartcitizen.me/hardware/firmware/?h=flash#flash-storage
The database contains a set of records in memory, ideally (although not working yet) encoded to protobuf and writable to the FS. This would allow to:
SENSOR) in which telemetry is interestingCurrent implementation relies on a protobuf definition implemented in meshtastic/protobufs#854
This is simply a PoC, not sure it's a good idea. If moving forward, it'd require work on:
GROUPS, keeping a separate index for the currently used group, to avoid writing / reading big groups every time.SENSOR), to avoid gaps in received packets.This is currently disabled by default and needs:
#define MESHTASTIC_EXCLUDE_AIR_QUALITY_DB 0🤝 Attestations