Skip to content

v1.59: curtailable inverter note and "Check the numbers" on Solar+? - #56

Merged
RickUsingGitHub merged 1 commit into
mainfrom
claude/amber-app-rebuild-6zrcqo
Nov 9, 2026
Merged

RickUsingGitHub merged 1 commit into
mainfrom
claude/amber-app-rebuild-6zrcqo

Conversation

@RickUsingGitHub

Copy link
Copy Markdown
Owner

What changes

Curtailable inverter

  • On a plan whose feed-in price goes below zero (Amber), the planner assumes by default that the panels switch off at those times. "What to ask installers for" now asks for a "curtailable" inverter of that size.
  • The recommendation and the option's detail say why, with the hours of negative feed-in, and point to Amber's list of supported inverters.
  • For homes that already have panels, they also say the existing inverter needs to be curtailable.
  • With "Panels switch off…" unticked, they instead say what a curtailable inverter would avoid.
  • On Amber, a battery should be one SmartShift can run, or one you automate yourself.
  • The switch-off setting's label and help now say it needs a "curtailable" inverter.

New "Check the numbers" card, following the option on show:

  • Averages: power bought and sent out, average price per kWh bought, average earned per kWh sent out (net of any export charge), daily charges, demand charges and the bill. These are shown for the yardstick, for the same plan with nothing new, and for the option.
  • Prices through the day: the plan's plain average buy and feed-in price for night, morning, middle of the day and afternoon/evening, plus how often feed-in is below zero.
  • Rules of thumb:
    • kWh a day per kW of panels, against installers' usual 3.5 to 4.4.
    • What each kWh of new solar or battery output is worth against what it costs per kWh over its life.
    • Hours of negative feed-in.
    • The planner's bill for the readings' plan, to compare with real bills.
  • What it assumes: panels, inverter, battery, export limit, negative feed-in, up-front cost breakdown, price rises and the money settings.

Help, README and tests are updated. The version is now 1.59.

Testing

  • All unit tests pass.
  • All 54 Playwright tests pass locally, including a new test of Amber's curtailable-inverter note with the setting ticked and unticked.
  • New checks on the numbers card: the bill it shows matches the month table's year.

Generated by Claude Code

…the numbers to check

- Where the plan's feed-in price goes below zero (Amber) and the panels are assumed to switch
  off then, "what to ask installers for" asks for a "curtailable" inverter, and the
  recommendation and the option's detail explain why (and that existing panels' inverter needs to
  be one too). With switch-off unticked, they say what a curtailable inverter would avoid. On
  Amber, a battery should be one SmartShift can run (or one you automate).
- New "Check the numbers" card for the option on show: average price per kWh bought and earned
  per kWh sent out, daily and demand charges and the bill, for the yardstick, the same plan with
  nothing new and the option; the plan's average buy and feed-in prices through the day and how
  often feed-in is below zero; rules of thumb (kWh a day per kW of panels, what each kWh of new
  solar or battery output is worth against what it costs per kWh, hours of negative feed-in, the
  planner's bill for the readings' plan); and the settings it was worked out with.
- Help, README and tests updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L7aZZe8i8qyWD6cwhnihsr
@RickUsingGitHub
RickUsingGitHub merged commit e035e28 into main Nov 9, 2026
1 check passed
@RickUsingGitHub
RickUsingGitHub deleted the claude/amber-app-rebuild-6zrcqo branch November 9, 2026 23:11
RickUsingGitHub added a commit that referenced this pull request Nov 15, 2026
…6zrcqo

v1.59: curtailable inverter note and "Check the numbers" on Solar+?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants