Releases: ksheumaker/homeassistant-apsystems_ecur
v1.4.3 Two small fixes
- Filter ECU bug #245 where # of inverters and today_energy become 0 incidently when it shouldn't be. Thanx @marcusds
- Replaced deprecated hass.components usage which will stop working in Home Assistant 2024.9
https://developers.home-assistant.io/blog/2024/02/27/deprecate-bind-hass-and-hass-components - Added configuration help doc. Thanx @RastaChaum
v1.4.1 Added switch to turn on/off the inverters
This release adds a switch entity called ecu_inverters_online. You can use this switch in your automations. When electricity prices become negative and you have to pay for returning energy to the grid, just turn off the inverters!
- The change takes place immediately but will only be visible at the next ECU update
- You will be able to see the immediate change happening on the (P1) meter if you turn the inverters off
- Read the doc for more info
- Forgot to update the version in the manifest file
This additional feature only works for the ECU-R pro and ECU-C type ECU's, not for the ECU-R starting with ID 2160
Special thanks to @harryboer for finding this feature
v1.3.1
Solved issue ECU bug Lifetime Energy is zero
There were conflicting issues for a longer period of time that have now have been resolved with a simple method.
#126
#113
If the ECU (occasionally) returns a zero for Lifetime Energy, this will be captured and the sensor will not update.
With this the "ECU returned 0 for lifetime energy, this is either a glitch from the ECU or a brand new installed ECU." warning should be resolved.
ECU bug Lifetime Energy is zero
There were conflicting issues for a longer period of time that have now have been resolved with a simple method.
#126
#113
If the ECU (occasionally) returns a zero for Lifetime Energy, this will be captured and the sensor will not update.
With this the "ECU returned 0 for lifetime energy, this is either a glitch from the ECU or a brand new installed ECU." warning should be resolved.
This is a beta release for testing puposes, if you encounter an issue on this small change, please raise an issue.
v1.3.0 Added option to suspend graphs
When inverters are offline, you now have the option to suspend the graphs. This was already (non optional) implemented for the inverter temperature because the zero temperature in the graph does not reflect the actual outside temperature.
v1.3.0b Added option to suspend graphs
When inverters are offline, you now have the option to suspend the graphs. This was already (non optional) implemented for the inverter temperature because the zero temperature in the graph does not reflect the actual outside temperature.
This is a beta release, there is a chance that it may contain bugs, although I have tested it extensively beforehand.
v1.2.30
Changes
- Revised documentation
- DS3-H id added (thanks to @Emacee)
- Apache license added (thanks to @fligneul)
- Dictionary correction: Inverter data should not be present in ECU (thanks to @fligneul)
- Cleanup code and minor function changes
- Bug on changed settings being omitted corrected
- Added ability to remove a device
If an inverter fails and it is replaced, the old inverter can now be easily removed from the Device info card. The device is removed from the core.device_registry and placed under the "deleted devices" category.
v1.2.30b
Beta release
For testing purposes only. Before reporting issues make sure your issue is related to this beta release.
Changes
- Revised documentation
- DS3-H id added (thanks to @Emacee)
- Apache license added (thanks to @fligneul)
- Dictionary correction: Inverter data should not be present in ECU (thanks to @fligneul)
- Cleanup code and minor function changes
- Bug on changed settings being omitted corrected
- Added ability to remove a device
If an inverter fails and it is replaced, the old inverter can now be easily removed from the Device info card. The device is removed from the core.device_registry and placed under the "deleted devices" category.
v1.2.29
v1.2.28 Constants release
Updates deprecated constants with current ones.
Thanks to: @IvanSanchez and @mcflexus for their contribution.