Skip to content

Releases: danwale/SolarUseOptimiser

v1.0.13

11 Jul 04:13

Choose a tag to compare

This version fixes issues with parsing the Growatt data when it's a Hybrid setup with a battery.
Merged in changes from the Huawei project into this one that fixed issues when polling too many devices too fast.

v1.0.12

16 May 03:43
c556243

Choose a tag to compare

Added in the linux/arm/v7 platform image to the Docker repository image manifest.

v1.0.11

15 May 02:54

Choose a tag to compare

Adds the TLX device type for Growatt that appears to be the equivalent of the INV device type with the same data payload.

v1.0.10

09 May 09:37

Choose a tag to compare

Fixed critical bug that prevented the previous version from working. Only discovered when the auth error went away this morning and I could test it properly.

v1.0.9

08 May 11:44

Choose a tag to compare

Added in the ability to send the error message up to the DataTarget, such as the auth failures with Growatt so the target (eg ChargeHQ) can show the end user the error message it's hitting.

v1.0.8

08 May 10:45

Choose a tag to compare

Updated the Growatt producer so that when it fails to authenticate it logs a warning message including the server side reason for the failure.

v1.0.7

19 Apr 14:36

Choose a tag to compare

Fixed a log line indicating the default number of errors that can occur before restarting the data source component if the configuration is missing.
Added in the linux/arm/v8 platform support.

v1.0.6

17 Apr 08:35

Choose a tag to compare

Added in a restart functionality for the producer so that if it's continually causing an error it will reset itself.

v1.0.5

03 Apr 14:03

Choose a tag to compare

Improved the Growatt authentication handling so that it didn't get stuck in tight loops on failure.
Improved the handling when testing with no ChargeHQ API Key.

v1.0.4

23 Feb 05:01

Choose a tag to compare

Added in a timestamp value into the Growatt data sent to the consumer service.
Added support for IoTaWatt power sensor devices, this is untested but was fairly simple so I think I've implemented it correctly.