Skip logger event-marker lines when loading stats records #6
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-5-analyze-event-lines"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two related changes on one branch:
Skip logger event-marker lines — the logger (PR #4) interleaves
connect/disconnectevent lines into the stats stream.load_records()loaded them as data records: counts were inflated, and a marker arriving at night (irradianceNone, not0) terminated a contiguous night block — splitting overnight discharge episodes and corrupting that section of the report. Fix: skip any parsed line carrying aneventkey. Closes #5.Document desired sensor data — new "Desired sensor data (not yet logged)" section in
mqtt-topic-logger.md: signed battery power (closes the power ledger exactly instead of inferring drain as a residual), battery temperature / BMS charge limit (SoC 95–99 taper modelling), array-plane irradiance (collapses the seasonal slope split, R² 0.69), inverter temperature/derate state — plus what is already covered. Closes #7.TDD: new
EventLineFilterTestsintest_analyze.py— all 7 analyze tests green.Closes #5
Closes #7