Show the control temperature apart from the individual sensors #9

New issue

Open

opened 2026-10-28 10:32:07 +01:00 by pti · 0 comments

pti commented

2026-10-28 10:32:07 +01:00

Owner

Problem

The dashboard and history graph show every sensor alike, next to the target temperature. Only the control temperature (combined from the healthy room sensors, min on blub) drives the heating. Tracking error is judged on it alone, see GLOSSARY.md and #8.

Example, 2026-10-28: the bathroom sensor read 24.7 °C against a 20 °C target while buros controlled the heating. On the graph the bathroom looks permanently 4.7 °C "wrong". Blub cannot fix that, but users see a systematic surprise and will blame the thermostat.

Proposal

History graph: draw the control temperature as its own, prominent series next to the target temperature. Draw the individual sensors as thinner or muted lines.
Dashboard: label the main temperature as the control temperature. Mark which sensor currently sets it, e.g. with min aggregation the coldest one.
Sensors page: show, per sensor, whether it currently contributes to the control temperature (healthy, weight).

Notes

Storing the control temperature: history currently stores only per-sensor readings. The control temperature series needs to be either stored (e.g. with each control tick or each aggregation) or reconstructed from the readings and the aggregation strategy. Storing it is simpler and stays correct when the strategy or the weights change.
Wording: use the glossary terms in the UI (control temperature, target temperature).

## Problem The dashboard and history graph show every sensor alike, next to the target temperature. Only the **control temperature** (combined from the healthy room sensors, `min` on blub) drives the heating. Tracking error is judged on it alone, see `GLOSSARY.md` and #8. Example, 2026-10-28: the bathroom sensor read 24.7 °C against a 20 °C target while buros controlled the heating. On the graph the bathroom looks permanently 4.7 °C "wrong". Blub cannot fix that, but users see a systematic surprise and will blame the thermostat. ## Proposal - **History graph:** draw the control temperature as its own, prominent series next to the target temperature. Draw the individual sensors as thinner or muted lines. - **Dashboard:** label the main temperature as the control temperature. Mark which sensor currently sets it, e.g. with `min` aggregation the coldest one. - **Sensors page:** show, per sensor, whether it currently contributes to the control temperature (healthy, weight). ## Notes - **Storing the control temperature:** history currently stores only per-sensor readings. The control temperature series needs to be either stored (e.g. with each control tick or each aggregation) or reconstructed from the readings and the aggregation strategy. Storing it is simpler and stays correct when the strategy or the weights change. - **Wording:** use the glossary terms in the UI (control temperature, target temperature).

pti referenced this issue from a commit

2026-10-28 10:37:26 +01:00

Domain glossary and ADR; name the anticipation in its terms

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

pti/blubgo#9

No description provided.

Rows
Columns