Addbatchstatus now requires energy field?

API
#1

I’ve been using addbatchstatus to push some extended data parameters available in the logdata push from Fronius (but not available in the inverter or meter pushes). Thus I only want to push the extended data in addbatchstatus, not any energy or power data etc. I just leave those earlier fields blank. This used to work but I just noticed that this request is failing with error 400 since 29-June-2025, I presume because the API spec now says that the energy field is required. Is there any reason why an energy value is now force required? I tried setting energy to -1 but that did not work.

#2

Hi @bulletmark,

Has your Donor status expired?

I push v7…v12 only using https://pvoutput.org/service/r2/addstatus.jsp from a local script without issue despite the requirements stating that at least one of v1…v4 must be present.

Grannos

#3

Oops, yes that is what it is, thanks. I guess searching out the docs and seeing that requirement that I was violating threw me. Probably the docs have always been incorrect.

#4

I did some searching and found this under Donations — PVOutput documentation

I vaguely remember reading about it sometime ago. At least that explains why it is possible to push the Extended Parameter without one of v1…v4

Add Status

  • The d date parameter must be not be older than 90 days from the current date.
  • Extended parameters v7, v8, v9, v10, v11 and v12
  • Maximum energy consumption v3 value increased to 9,999,999Wh
  • Maximum power consumption v4 value increased to 2,000,000W
    > * Temperature v5 and Extended parameters v7 to v12 can be sent without v1 to v4
  • Text message m1 parameter can be used as part of a custom alert subject or body message.
#5

For a standard account at least one of v1-v6 is required. Donators can omit these and send v7-v12, b1-b6