Model expected battery cycle count under dispatch behavior #11

New issue

Open

opened 2026-07-17 01:17:56 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-07-17 01:17:56 +00:00

Contributor

docs/implementation-audit.md under Battery Cycle Information: Current batteries include cycle life and the UI displays approximate years at one cycle/day. There is no modeled expected cycle count under dispatch behavior yet.

One cycle/day is a placeholder. The hourly simulation already knows exactly how much the battery is charged and discharged, so actual annual cycle count can be derived from the selected dispatch rather than assumed.

This matters because dispatch aggressiveness (Smart mid-peak, Ultimate 6am-10pm) directly trades battery lifespan for arbitrage savings, and the app currently shows the savings side of that trade without the wear side.

Supports the roadmap Guiding Decision: Long-term modeling should include battery cycle expectations and solar panel lifetime/degradation. The solar half is done; the battery half is not.

Code: src/lib/simulation.js, src/lib/batteries.js

`docs/implementation-audit.md` under `Battery Cycle Information`: *Current batteries include cycle life and the UI displays approximate years at one cycle/day. There is no modeled expected cycle count under dispatch behavior yet.* One cycle/day is a placeholder. The hourly simulation already knows exactly how much the battery is charged and discharged, so actual annual cycle count can be derived from the selected dispatch rather than assumed. This matters because dispatch aggressiveness (Smart mid-peak, Ultimate 6am-10pm) directly trades battery lifespan for arbitrage savings, and the app currently shows the savings side of that trade without the wear side. Supports the roadmap Guiding Decision: *Long-term modeling should include battery cycle expectations and solar panel lifetime/degradation.* The solar half is done; the battery half is not. Code: `src/lib/simulation.js`, `src/lib/batteries.js`

claude-bot added this to the v1.2.0 - Quote Persistence & Modeling Depth milestone

2026-07-17 01:17:56 +00:00

claude-bot added the

enhancement

label

2026-07-17 01:17:56 +00:00

rbrooks referenced this issue from a commit

2026-07-17 01:58:46 +00:00

Reconcile calculation audit and changelog with degradation work

claude-bot referenced this issue

2026-07-17 01:59:06 +00:00

Reconcile calculation audit and changelog with degradation work #21

claude-bot commented

2026-07-17 02:00:51 +00:00

Author

Contributor

Partially addressed by b31aa8c (Add battery degradation and rate-escalation-adjusted payback), which landed independently.

That commit models degradation over time — a flat degradationPct (2%/yr default) compounded per year in calculateAdjustedPaybackYears and in projections. It does not model cycle count under dispatch, which is what this issue asks for.

The distinction still matters, and arguably matters more now: the flat 2%/yr rate is independent of how hard the battery is actually worked. Selecting Ultimate Savers 6am-10pm dispatch cycles the battery far harder than peak-only dispatch, but both currently degrade at the same 2%/yr. The hourly simulation already knows the real charge/discharge throughput, so actual cycle count is derivable — and could drive the degradation rate rather than assuming it.

Keeping open. Scope is now narrower and better defined: feed simulated cycle count into the existing degradation model rather than build degradation from scratch.

Partially addressed by `b31aa8c` (*Add battery degradation and rate-escalation-adjusted payback*), which landed independently. That commit models degradation **over time** — a flat `degradationPct` (2%/yr default) compounded per year in `calculateAdjustedPaybackYears` and in projections. It does **not** model **cycle count under dispatch**, which is what this issue asks for. The distinction still matters, and arguably matters more now: the flat 2%/yr rate is independent of how hard the battery is actually worked. Selecting Ultimate Savers 6am-10pm dispatch cycles the battery far harder than peak-only dispatch, but both currently degrade at the same 2%/yr. The hourly simulation already knows the real charge/discharge throughput, so actual cycle count is derivable — and could drive the degradation rate rather than assuming it. Keeping open. Scope is now narrower and better defined: feed simulated cycle count into the existing degradation model rather than build degradation from scratch.

claude-bot referenced this issue

2026-07-17 03:06:26 +00:00

Annual bill extrapolation misuses cross-season and partial-month data #23

claude-bot referenced this issue

2026-07-17 03:06:39 +00:00

Enforce inverter power limits in battery dispatch (charge and discharge) #25

claude-bot referenced this issue

2026-07-17 03:09:27 +00:00

Outage log with detected candidates and coverage assessment #47

claude-bot referenced this issue

2026-07-17 03:09:29 +00:00

Payback sensitivity table (escalation × degradation grid) #48