Issues with aggregating extended data

[Qubic]

I just noticed that extended data was not aggregated on my system anymore after 23 Aug '25.

My child aggregation modes are set to “All” and parent aggregation for the extended parameters is set to Add. My parent mode is set to “Solar” but this does not aggregate extended data anymore. The parent only aggregates extended data if I set the parent mode to “All”.

This contradicts the documentation:

Extended data is always aggregated when any child system enables the Parent Aggregation option for one or more of its extended parameters.

Secondly, I also aggregate the inverter temperature of the 2 children. Previously they were automatically averaged but now I can only choose between “Add” or “Subtract”. I tried adding an “Extended data rule” in the parent for averaging the temperature (v7 = v7 / 2) but this does not seem to be applied?

[bankstownbloke]

@Qubic

My parent mode is set to “Solar” but this does not aggregate extended data anymore. The parent only aggregates extended data if I set the parent mode to “All”.

Thanks for reporting this, it looks like a bug that has now been fixed. You shuold be able to change the parent to “Solar” and set any of the children extended data “Parent aggregation” settings to either “Add” or “Subtract” and it will add/substract on the parent.

@Qubic

I also aggregate the inverter temperature of the 2 children. Previously they were automatically averaged but now I can only choose between “Add” or “Subtract”

There is an option to pick which child system temperature or voltage a parent should use with (“Use Temperature” / “Use Voltage”) but never an option to average them.

@Qubic

I tried adding an “Extended data rule” in the parent for averaging the temperature (v7 = v7 / 2) but this does not seem to be applied?

Previously extended data rules were not supported for a parent system, but is now supported since 11th Sept 2025. The only flaw with this method is if there is a missing child temperature v7 upload then average isn’t accurate.

[Qubic]

@bankstownbloke

You shuold be able to change the parent to “Solar” and set any of the children extended data “Parent aggregation” settings to either “Add” or “Subtract” and it will add/substract on the parent

I will verify this tomorrow. Sun is down here.

@bankstownbloke

There is an option to pick which child system temperature or voltage a parent should use with (“Use Temperature” / “Use Voltage”) but never an option to average them.

But if you look at my parent system on 23 August 2025. The inverter temperatures (extended data) of the 2 children were automatically averaged.
https://pvoutput.org/intraday.jsp?id=107900&sid=94362&dt=20250823

On 07 September 2025 I changed the parent to “All” and the values came back but were added now.
https://pvoutput.org/intraday.jsp?id=107900&sid=94362&dt=20250907&gs=0&m=1

@bankstownbloke

Previously extended data rules were not supported for a parent system, but is now supported since 11th Sept 2025. The only flaw with this method is if there is a missing child temperature v7 upload then average isn’t accurate.

I can confirm that extended data rules are working for the parent system.
Maybe an average function could be implemented (that takes in account missing child values)?

[bankstownbloke]

@Qubic

The inverter temperatures (extended data) of the 2 children were automatically averaged.

The parent (94362) v7 values look identical to the child system (94360) v7 values on this date.

This suggests the v7 aggregation has been set to “Add” on 94362, while the other children were set to “None”, since averaging extended data from child systems has never been supported (only “Add” and “Substract”) - although it may be an enhancement option in the future.