Document sensor data we want logged that is not currently present

agent-pi commented

2026-09-09 03:14:46 +00:00

Collaborator

The analysis work keeps hitting the same walls: battery flow is inferred as a residual, the SoC 95-99 taper is excluded instead of modelled, and the irradiance-to-power model needs per-season slopes because the sensor is horizontal while the arrays are tilted. The sensor data that would fix these is not collected anywhere in the current log.

These wishes should be written down somewhere durable so instrumentation decisions (and any new MQTT topics) have a reference, with the analysis each field would unlock.

The analysis work keeps hitting the same walls: battery flow is inferred as a residual, the SoC 95-99 taper is excluded instead of modelled, and the irradiance-to-power model needs per-season slopes because the sensor is horizontal while the arrays are tilted. The sensor data that would fix these is not collected anywhere in the current log. These wishes should be written down somewhere durable so instrumentation decisions (and any new MQTT topics) have a reference, with the analysis each field would unlock.

agent-pi commented

2026-09-09 03:14:46 +00:00

Author

Collaborator

Plan of attack

Add a top-level Desired sensor data (not yet logged) section to mqtt-topic-logger.md (the logger reference doc, where TOPICS config lives), listing each missing field, its likely source, and the analysis it unlocks - grounded in existing findings (residual-based fast-charge drain, SoC 95-99 taper exclusion, seasonal slope split R2 0.69).
Also note what is already covered (zappi mode/plug/cooldown, forecast snapshots - verified ~100% presence since 2026-08-10) so the list stays honest.
Fields whose availability depends on hardware/BMS support are phrased conditionally, not as confirmed capabilities.
Commit :memo: document desired sensor data not yet in the log on fix/issue-5-analyze-event-lines so it lands with PR #6.

**Plan of attack** - Add a top-level **Desired sensor data (not yet logged)** section to `mqtt-topic-logger.md` (the logger reference doc, where TOPICS config lives), listing each missing field, its likely source, and the analysis it unlocks - grounded in existing findings (residual-based fast-charge drain, SoC 95-99 taper exclusion, seasonal slope split R2 0.69). - Also note what is already covered (zappi mode/plug/cooldown, forecast snapshots - verified ~100% presence since 2026-08-10) so the list stays honest. - Fields whose availability depends on hardware/BMS support are phrased conditionally, not as confirmed capabilities. - Commit `:memo: document desired sensor data not yet in the log` on `fix/issue-5-analyze-event-lines` so it lands with PR #6.

agent-pi referenced this issue from a commit

2026-09-09 03:16:54 +00:00

:memo: document desired sensor data not yet in the log

agent-pi referenced this issue from a pull request that will close it,

2026-09-09 03:17:12 +00:00

Skip logger event-marker lines when loading stats records #6

marvin8 closed this issue

2026-09-09 03:24:35 +00:00

Rows
Columns

Document sensor data we want logged that is not currently present #7