Releases: kpoppel/homeassistant-eforsyning
Fix state_class warning
Finally I got some time to make the very changes requires to fix the warning is Home Assistant.
I hope it works out as I originally did not assign a state_class because the 5 sensors implied are not really measurements.
Warnings for these sensors should now go away:
- energy-used
- energy-exp-used
- water-used
- water-exp-used
- amount-remaining
Fixes #69
Full Changelog: v1.2.7...v1.2.8
v1.2.7
v1.2.6
What's Changed
- Double slash in GetVaerkSettings by @Sdahl1234 in #64
- Fixed a small typo in README.md by @mm98 in #66
New Contributors
- @Sdahl1234 made their first contribution in #64
- @mm98 made their first contribution in #66
Full Changelog: v1.2.5...v1.2.6
Contributors
Assets 2
Fix timeout issues when fetching data from eForsyning.
Fixes entities not populated due to endpoint timeout: #60
What's Changed
- Increase timeout to 10 seconds by @MathiasReker in #62
New Contributors
- @MathiasReker made their first contribution in #62
Full Changelog: v1.2.4...v1.2.5
Contributors
Assets 2
Try fix for GJ billing data
This release attempts to add some support for billing which uses GJ instead of MWh - see #51
Full Changelog: v1.2.3...v1.2.4
Add more parsing of billing information
Contributors
Assets 2
Fix warning in log for sensor class
In the log file a new warning appeared for "ENERGY", "WATER" and "MONETARY" class sensors. This release removes that warning.
Full Changelog: v1.2.1...v1.2.2
v1.2.1
Fixes Home Assistant 2023.3 warning.
Full Changelog: v1.2.0...v1.2.1
Add support for GJ conversion
Adds new feature for issue #51 converting from GJ to kWh. The feature is not complete as the data extracted from the billing module is not converted as it is currently unknown to me if this also is needed. A future fix-release will take care of this if needed.
Full Changelog: v1.1.5...v1.2.0
v1.1.5
This release fixes a New Year issue where data fetches from the API does not resolve to the new year.
It is not as much a bug as it is a feature of the way the local heating company needs to update their settings.
They have to update a 'heating year' maker and that may give some delay for some. Just drop them a note
if this is what you see (seen by getting only 2022 data before this release).
With this release the integration will during January try to get the current year data anyway, and if it looks good, just use that until the marker is updated correctly.
Full Changelog: v1.1.4...v1.1.5