Powerwall Capacity Panel stacks charge graphs

[nadams5755]

Problem
In the last few releases, maybe longer, it seems the PW capacity chart stacks the current capacity graphs. It works with the right axis where their capacities can be added. However it looks a little strange with the theoretical axis on the left. With more than one PW, it looks like a large disparity between PW capacities.

To Reproduce
Please paste a screenshot or steps to reproduce the behavior:

1. Go to Load the default Powerwall - Power Flow dashboard
2. Click on '....'
3. Scroll down to 'Powerwall Capacity'
4. See error

Screenshots

System Details

• Powerwall Installation: PW+ and PW2
• Powerwall Firmware Version 26.18.1
• Host System Hardware and OS: Rocky Linux 10.2
• Other Specifics

Additional context
Powerwall Dashboard Installation: Cloud, Local, TEDAPI
Add any other context about the problem here.

Changing this value from normal to none seems to fix the chart behavior. https://github.com/jasonacox/Powerwall-Dashboard/blob/main/dashboards/dashboard.json#L10399

I suppose we could instead sum the capacity for the left legend. i can submit a PR to change the stacking behavior.

[jasonacox-sam]

Thanks for the detailed report and for tracking down the exact line — really helpful.

This is the same behavior discussed at length in #569. The stacking was added intentionally so that the right-axis charge values would sum to show total system charge across multiple Powerwalls. The tradeoff, as you've noticed, is that the left-axis capacity values also stack, which looks odd when the theoretical capacity per unit is the more meaningful read.

Jason explored separating the charge and capacity graphs as a possible middle ground, but no resolution has landed yet.

A PR would be very welcome. The two approaches worth considering:

1. Unstack everything (stack: none) — what you proposed. Cleanest visual, but loses the total-charge-at-a-glance read that some users rely on.
2. Keep charge stacked, unstack capacity — requires splitting the panel overrides so each series type has its own stacking config. More work but preserves both views.

Option 2 is probably the sweet spot if you're up for it. Either way, drop the PR and link it here and to #569 so folks following that thread can test.