Batteries on PVO?

Ideas In Progress
#1

With the Australian Federal Govt battery rebate, battery installations here are about to boom. There are now more requests for battery quotes than for solar PV.

Will PVOutput reconsider the addition of channels for handling of battery charge and discharge data?

I recently moved home and recently installed a new solar PV + battery system. My PV output and consumption data is being uploaded to PVO but without charge and discharge data the rest of the data on PVO makes no sense.

I know this was dismissed previously, just wondering if this decision will be revised given the impending battery boom?

2 Likes
#2

you mean like this?

2025-07-16_191138
2025-07-16_1911381241×624 152 KB

#3

Thanks but where in the documentation does it refer to or show how battery data can be integrated/uploaded?

#4

Support for standard battery parameters is being investigated.

However, you’ll still need retrieve the battery data and send it to PVOutput e.g. b1 - b5 etc . What battery data fields do you have?

#5

You can see the method here in this post, you might need to modify it to suit your own system if you aren’t using a Powerwall.

#6

I have a range of options, charge and discharge energy accumulation sensors and battery power:

Best would be to upload:

  • Battery charge and discharge energy accumulation values (in kWh), either daily accumulation value or lifetime values (best). These could be uploaded at 5, 10 or 15 minute intervals.

Else I also have:

  • Real time battery power, which is positive or negative and available in instant values, not so good for PVO use really
  • Alternatively split registers for battery charge power and battery discharge power.

There is also state of charge data and a range of other metrics which are less important (average cell voltage data, module temperatures).

#7

Is that in the Extended data?
I already use that so if I add a battery i wouldn’t be able to record it.

#8

Currently penciling in -

  • b1 - Battery charge W (+) / discharge (-)
  • b2 - State of charge (%)
  • b3 - Battery Size / Capacity (Wh)
  • b4 - Lifetime Energy Charged (Wh)
  • b5 - Lifetime Energy Discharged (Wh)
  • b6 - Battery Status (0-4)
2 Likes
#9

@bankstownbloke - any info on a timeline when this is likely to be implemented?

I’m trying to decide whether it is worth the effort to manually adjust the energy consumed figure to exclude energy from my battery before sending to PVO, so daily balance figures are calculated correctly.

#10

No concrete timeline, but the backend work has been complete to accept battery data (b1-b6).

If you’re using extended data currently for the battery data, this calculation is now supported with Extended Data rules. This was the result of the recent battery functionality support changes -

e.g. v4 = v4 - v7

See https://forum.pvoutput.org/t/extended-data-rules-v1-v4/5345

1 Like
#11

This is great news.

I have a couple of questions.

Does that mean we could start sending this data now, but we just won’t see it in the charts and tables?

Is this new data taken into consideration when PVOutput auto-calculates consumption/exports/imports?

Is this the Watts over the interval, and will it be automatically calculated if only b4/b5 are provided (i.e. same as v2/v4 for generation/consumption)?

What do 0-4 represent?

Thanks.

#12

The ‘Add Status’ API does accept b1-b6 and will record them, but there is currently no method to view the data.

Update - You can click on the ‘Download’ link below the graph to review the uploaded battery data.

It isn’t, there will be an option to add/subtract the battery power (b1) value from v4

Currently, b1 is mandatory, b2-b6 values are ignored if b1 is missing.

This maps to the [telemetries.power] value on the SolarEdge or [battery.power] on the Powerwall

This will be based on the SolarEdge battery statuses -

  • 0 (Invalid)
  • 1 (Standby
  • 2 (Thermal Mgmt.)
  • 3 (Enabled)
  • 4 (Fault)
#13

As an exercise I have modified a script to start uploading data to b1 and b2 for my friend’s AlphaESS in addition to v8 and v9.

SoC [ State of Charge ] and RoC [ Rate of Charge ]

#14

Okay. Normally you would adjust exports/imports instead of consumption, but since “Add Status” doesn’t upload exports/imports, I can see why you might want such an option.

The Daily/Weekly/Monthly/Yearly charts seem to calculate exports/imports if consumption is uploaded (and conversely calculate consumption if exports/imports are uploaded with the “Add Output” API). Will the battery stats be taken into account when auto-calculating exports/imports on these charts, and/or will exports/imports be able to updated? (At the moment, it seems that if you upload consumption, then the calculated exports/imports cannot be updated.)

Thanks.

#15

For testing purposes, do you mind posting the system id?

#16

Net data (import/export) is calculated from gross generation and consumption, since adding/subtracting the battery power will adjust the consumption value it will ultimately affect the resulting net data.

5-minute consumption/generation data added/updated via ‘Add Status’ will automatically recalculate import/exports.

#17

Hi @bankstownbloke,

sid=66069

v7 → Internal Inverter Temperature from Fronius Symo
v8 → SoC of AlphaESS SMILE G3 B5 INV
v9 → Rate of Charge of AlphaESS SMILE G3 B5 INV

So far so good uploading to ‘b1’ and ‘b2’. I haven’t figured out how to extract the other data from the Alpha ESS yet. b3 etc.

2025-10-13 17:35

Inverter Temperature: 48C
    Max Count: 1
    https://pvoutput.org/service/r2/addstatus.jsp?key=XXXXXXXX&sid=66069&d=20251013&t=17:35:12&v7=48&v8=100&v9=-596&b1=-596&b2=100
    OK 200: Added Status

Grannos

1 Like
#18

Thanks @grannos - b1 and b2 are now displaying on the live system page.

Please refresh the page.

image
image960×450 38.7 KB

Default graph colours can be changed under account ‘Settings’ -

image

1 Like
#19

Hi @bankstownbloke. Working great. Thanks.

Now I guess that it’s time to start digging a bit deeper in to Alpha ESS API.

Grannos

#20

I’m uploading B1-B5 on my system 28198, if its of any use for testing.