2024.5.1

What's Changed

• Create virtual production meter by summing inverters by @krbaker in #67
• enable marking of sensors as "diagnostic" by @krbaker in #69
• enabled hassfest testing for this integration by @krbaker in #72
• moved polling times to an option so they can be changed without delete/reinstall by @krbaker in #79
• automated finding ESS (removed config option)

Full Changelog: 2024.4.3...2024.5.1

2024.4.3 - ESS Support, Major Refactor (plus ESS bugfix)

What's Changed

• Major refactor and adding support for ESS. Merge work by @krbaker in #64 but major thanks to @CanisUrsa for the initial fork.
• Releasing as pre-release so you may need to flip your HACS config to try this:
• I did not keep the forks entity name and unique ID changes as is, if you are coming from https://github.com/CanisUrsa/hass-sunpower your history will be disconnected. I did try to keep the original installations identities so that shouldn't break (please report if it does)
• I do not have an ESS, some progress was made to make testing easier with fake data but its not there yet, please try and file issues
• Refactored to a more easily modifiable mapping of data to sensors thanks to @CanisUrsa
• Added an ability to add 'product names' to entity names, I don't think the noise is worth it in the UI but tried to allow keeping similar to what the ESS folks may have had. (My recommendation is Detailed Entity: True and Product Names: False)
• Added the ability to set polling rates in setup (ESS and PVS separately) -- read the README, its a bit convoluted.
• Bugfix in .3: turns out ESS parsing used the data from PVS, this has been tested by at least one user

WARNING
My PVS went through the 'not posting to cloud' issues. I think its possible this plugin contributes to those. My working theory is logging can fill up a partition and that then causes something to fail (like an MQTT cert refresh). I think PVSs can lock up like that w/o this integration running against them but it might well contribute. I ran mine for a long time at 120s polling before it stopped posting, now I'm backing off to 300s. I did get my PVS working again through a Firmware update and waiting (I'm guessing it may flush logs over time). I'm going to keep running it and see what happens...

Full Changelog: 2024.4.1...2024.4.2

2024.4.2 - ESS Support, Major Refactor

What's Changed

• Major refactor and adding support for ESS. Merge work by @krbaker in #64 but major thanks to @CanisUrsa for the initial fork.
• Releasing as pre-release so you may need to flip your HACS config to try this:
• I did not keep the forks entity name and unique ID changes as is, if you are coming from https://github.com/CanisUrsa/hass-sunpower your history will be disconnected. I did try to keep the original installations identities so that shouldn't break (please report if it does)
• I do not have an ESS, some progress was made to make testing easier with fake data but its not there yet, please try and file issues
• Refactored to a more easily modifiable mapping of data to sensors thanks to @CanisUrsa
• Added an ability to add 'product names' to entity names, I don't think the noise is worth it in the UI but tried to allow keeping similar to what the ESS folks may have had. (My recommendation is Detailed Entity: True and Product Names: False)
• Added the ability to set polling rates in setup (ESS and PVS separately) -- read the README, its a bit convoluted.

WARNING
My PVS went through the 'not posting to cloud' issues. I think its possible this plugin contributes to those. My working theory is logging can fill up a partition and that then causes something to fail (like an MQTT cert refresh). I think PVSs can lock up like that w/o this integration running against them but it might well contribute. I ran mine for a long time at 120s polling before it stopped posting, now I'm backing off to 300s. I did get my PVS working again through a Firmware update and waiting (I'm guessing it may flush logs over time). I'm going to keep running it and see what happens...

Full Changelog: 2024.4.1...2024.4.2

2024.4.1

What's Changed

• Update README.md for clarity by @krbaker in #51
• fix issue #55 updating sensors classes, new unit constants in prep for 2025.1 by @krbaker in #56, #58
• fix issue #53 power factor reports aren't scaled correctly by @krbaker in #57
• fix issue #59 association link just needs the domain as part of the key by @krbaker in #60

Full Changelog: 2023.5.1...2024.4.1

2023.5.1

Made parsing at runtime more robust to missing feilds

2023.3.1

• Switch to Home Assistant version scheme ( .. )
• Change Meter sensors to be total, not total increasing to remove errors.
  • If anyone sees a 'wrap' I'd be curious, no API docs so hard to tell how big this error is
  • Any other errors please report

0.0.13

Should fix wrong units and handle parsing failures better.

Note: This fixes the wrong unit of VA for Amps on the inverters. The statistics module will complain about this and you have to use the developer tools to fix

Form the developer tools page:
go to statistics
search 'amps'
click 'fix issue'
you should be able to leave it as 'update the unit...'
click fix issue

Rinse and repeat for the rest.

0.0.12

fixes issue 21

0.0.11

Adds Energy Monitoring / Stats Gathering
Fixes bug where some old install data would fail in v.0.0.10

0.0.10

Thanks to crkochan for this release!

Adds an option in the config flow to enable "descriptive entity names". The feature basically adds the component description to the front of the various entity IDs. For example, an inverter's power sensor sensor.power_4 would become sensor.inverter_<downcase_serial>_power.

The upside is unique entity names that are potentially easier to automate with. The downside is the entity names become much longer.

This feature is disabled by default to avoid churn for existing users. It can only be enabled during setup. OptionsFlow might be able to be used to switch on and off the feature without having to reinstall the integration, but that's being left as an exercise for another contributor.