Releases: JasperE84/PyFusionSolarDataRelay
v2.0.5 - Bugfix for Huawei docs stating kW units instead of actual W units provided by API
v2.0.4: Bugfix in FusionSolar kiosk quirk
Merge pull request #30 from JasperE84/v2.0.4-dev Bugfix in FusionSolar kiosk quirk
v2.0.3 Bugfix release
Merge pull request #28 from JasperE84/v2.0.2-dev V2.0.3 Bugfix in scheduler
V2.0.2 - Change Hass MQTT discovery template to kW instead of W
Merge pull request #27 from JasperE84/v2.0.2-dev V2.0.2 - Change Hass MQTT discovery template to kW instead of W
Now supporting FusionSolar Northbound OpenAPI for inverters and grid meters, Kenter API v2, Automatic Home Assistant MQTT device discovery
2.0.1 | Now sending MQTT device discovery message for home asisstant
2.0.1 | Bugfix in environment variable parsing for custom pydantic nested env list parser
2.0.0 | BREAKING CHANGE: Environment variables for config changed names and structure. Please review the configuration section in README for updated variable names
2.0.0 | Introduced possibility to configure multiple input sources (kiosks, openapi meters/inverters and kenter meters)
2.0.0 | Implemented Huawei Northbound OpenAPI as data source for metrics
2.0.0 | Now supporting Kenter API v2
2.0.0 | Removed currentPower kiosk property (fetched from powercurve API obj) in favor of realTimePower
2.0.0 | Removed functionality to write utility grid consumption (non-pv) to PVOutput (InfluxDB fully supported!)
2.0.0 | Refactored class names and .py file structure
2.0.0 | Implemented pydantic to replace pvconf.py, now supporting non-environment variable based settings using config.yaml
Bugfix release with some more descriptive exception strings
v1.0.6 fixes faulty config parsing of cron values and adds more descriptive exception messages when kiosk api query fails
Additionally, if debug mode is enabled, fusionsolar will be queried on startup, so we don't have to wait for cron to trigger.
1.0.5
1.0.4
Release 1.0.3
Changelog in README.md