v2.0.0 Configuration Migration

[Crim]

2.0.0 (10/11/2026) Update Configuration UI

IMPORTANT UPGRADE NOTE

If your Power/Energy Generation entities are NOT cumulative - After updating this version, edit your config and disable that flag.

Feature Changes

• Reworked the config UI to expose ALL PVOutput API parameters.
• Added support for Extended Data parameters v7 through v12 (PVOutput donation features).
• Added support for explicit Net Flag (n=1) and Cumulative Energy Flag (c1=1).
• Added internal private Notes field per solar array for user reference.

The reason for the change

This version updates how the plugin configures properties to be sent to PVOutput's API.

The previous version tried to simplify the configuration UI presented to the end user and then 'be smart' about how it took that configuration and figure out what values needed to be sent to the API in the various parameters. In the end, 'trying to be smart' probably worked for 80% of the use cases, but ended up being unable to work properly for the remaining 15%.

This update now just lists out the properties that can be submitted over the API and allows the user to directly map them to the appropriate underlying Home Assistant entity. This gives the end user full control of what gets sent and should resolve the outstanding issues/problems users were having.

Upgrade Notes

If your Power/Energy Generation entities are NOT cumulative - After updating this version, edit your config and disable that flag.

After updating the plugin and restarting home assistant, it should perform a migration of your previous config values to the new system. It should be transparent and map things correctly. There is one caveat, the c1 cumulative flag cannot be accurately detected during the migration step because of how Home Assistant treats the internal flag on the entity for this.

The Boring Change Notes

• Upgraded configuration schema to Version 2 with direct 1-to-1 parameter mappings to the PVOutput API (v1–v12, c1 cumulative flag, n net flag).
• Automated, non-destructive migration (async_migrate_entry) from v1 to v2 on installation/startup with zero configuration loss.
• Cumulative Energy Flag (c1) Migration Note:
  • Migrated systems with an Energy Generation sensor (v1) default the Cumulative Energy Flag (c1=1) to enabled. This matches PVOutput's requirement for lifetime counter sensors (such as inverter lifetime yield) so PVOutput calculates interval yields instead of rejecting the value as "Energy value too high".
  • How to verify your configuration: Go to Settings > Devices & Services > PVOutput Publisher > Configure, then click Edit on your array.
    • If your v1 sensor is a lifetime yield counter (monotonically increasing and does not reset to 0 daily), keep Cumulative Energy Flag (c1=1) checked.
    • If your v1 sensor resets to 0 at midnight (daily yield), uncheck this box.

Should resolve issues:

• Extended parameters in donation mode #10
• adding the &c1=1 flag is not always correct #11
• Request: Map the 'grid export today' to PVoutput #12 Potentially with the inclusion of the n Net Export flag being exposed in the updated config ui.