[2.8] Annotate BME680 IAQ discontinuity

Open
  • Is something wrong?
#458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
backend, frontend

Research direction

Start with the EnvironmentMetrics model at packets/models.py:150 to see where iaq is stored, then find how a node's firmware version is recorded. The chart code lives in the separate UI repo, which the payload does not name, so locate the IAQ chart component there first. Done means a firmware-change marker appears on IAQ charts, which needs agreement across both repos, so confirm the approach on the issue before writing code.

Written by the indexing model from the issue text.

Description

enhancement meshtastic-2.8

Part of pskillen/meshflow-api#437 (Meshtastic 2.8.x support). Code: TP-5 · Priority: Nice · Size: S

Summary

Cross-repo (api + ui). 2.8 replaces BSEC with an open IAQ estimator, so EnvironmentMetrics.iaq isn't comparable across the upgrade (packets/models.py:150). Annotate charts/stats where a node's firmware changed.

Acceptance criteria

  • Annotation visible on IAQ charts

Depends on: none

Dominant language
Python
Stars
1
Forks
0
Avg merge
1d 20h
Merged PRs (30d)
5

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pskillen/meshflow-api

All issues in pskillen/meshflow-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.