v2.3.0

What's Changed

Features

• Allow adding headers to grid and inverter requests (e.g. to use Bearer Token for Homeassitant integration) by @pkuehnel in #206
• Add float conversion to modbus plugin by @pkuehnel in #209
• Do not call PV separate for grid and inverter values if url and headers are the same by @pkuehnel in #211

Bugfixes

• On unknown charge limit wakeup car only if not awake by @pkuehnel in #203
• Update jobintervalls on changing base configuration by @pkuehnel in #213
• Do not update cars more often than getting new values from grid endpoint by @pkuehnel in #214

Full Changelog: v2.2.3...v2.3.0

v2.2.3

What's Changed

Bugfixes

• Crashed on startup if basic config does not exist by @pkuehnel in #187

Full Changelog: v2.2.2...v2.2.3

v2.2.2

What's Changed

New Features

• As some inverters struggle with getting to many modbus requests you now can add a new environement variable RequestBlockMilliseconds. For more detailed information see Using Modbus plugin by @pkuehnel in #182

Full Changelog: v2.2.1...v2.2.2

v2.2.1

What's Changed

New Features

• Autodetect SolarEdge plugin and fill corrent power to grid url by @pkuehnel in #180
• Autodetect modbus plugin an use better ui to generate powert to grid url by @pkuehnel in #180

Full Changelog: v2.2.0...v2.2.1

v2.2.0

What's Changed

Updated README for easier setup by @pkuehnel in #176

New Features

• Adding support for Modbus TCP devices. Added new sections to README for installation and configuration. It is planned to create templates for different inverters, so feel free to create a discussion in the show and tell section and I will implement templates for future users. @pkuehnel in #165
• Add Int16 datatype. If your inverter needs different datatypes, feel free to create a new issue by @pkuehnel in #178

Bugfixes

• Application was not starting up without environment variables by @pkuehnel in #171
• Could not add Telegram Key and Group ID by @pkuehnel in #179

Full Changelog: v2.1.0...v2.2.0

v2.1.0

What's Changed

Features

• Adding base configuration page, replacing environement variables. Note: All environment variables are taken into account and converted to the values on the new base configuration page but as these settings are saved for the first time all set environment variables don't matter anymore (plugin configurations still have to be done via environmentvariables for now) by @pkuehnel in #155
• Use Average of requested and actual current for calculating power as Tesla's API displays more current than actually consumed on low power by @pkuehnel in #159
• Allow switch off and switch on time spans to be changed without restarting the application by @pkuehnel in #163

Bugfixes

• Update Intervall is now using the configured value and not default value of 20 seconds by pkuehnel in #153
• Save minimum current for each car and do not replace it with 1 on every startup by @pkuehnel in #157
• Consider whitespace characters on xml and json patternconfiguration as not configured. Until now it was not possible to remove a configured json/xml pattern by @pkuehnel in #158
• Do not use requested current for power calculation if car is not charging by @pkuehnel in #161

Full Changelog: v2.0.2...v2.1.0

v2.0.2

What's Changed

Bugfixes

• Use minutes until switch off correctly by @pkuehnel in #149

Full Changelog: v2.0.1...v2.0.2

v2.0.1

What's Changed

The software has been renamed to TeslaSolarCharger, current setups should continue to work without changes but feel free to rename everything in your docker-compose.yml

Features

• Use two new mqtt topics from TeslaMate to optimize charging experience. Note: you have to update TeslaMate to at least Version 1.27.0 by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/143

Full Changelog: pkuehnel/smartteslaampsetter@v1.8.0...v2.0.1

v1.8.0

What's Changed

Breaking changes

To further use the software you have to add environment variables to let SmartTeslaAmpSetter access your TeslaMate database. This is needed to get the latest Charter current pilot because this topic is not published by TeslaMate over MQTT. These are the default settings (If you did not change any passwords or service names you do not have to do anything, only add this environment variables if they are different from the default values):

- TeslaMateDbServer=database
- TeslaMateDbPort=5432
- TeslaMateDbDatabaseName=teslamate
- TeslaMateDbUser=teslamate
- TeslaMateDbPassword=secret

Note: since v2.1.0 you need to configure these settings on the BaseConfiguration site of TeslaSolarCharger.

Features

• Inverter power can be JSON formatted by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/132
• Inverter and grid power can be XML formatted, details see corresponding README section by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/132
• SolarEdge Cloud API integration implemented, see corresponding README section. Note this feature is not tested by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/129
• Reduce charging speed based on charger pilot current. If charger does not allow maximum configured ampere (probably due to power management of your Wallbox) a Telegram Message is sent if configured by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/135

Full Changelog: pkuehnel/smartteslaampsetter@v1.7.0...v1.8.0

v1.7.0

What's Changed

Features

• Split getting pv values and setting car amp into two different timers, so on amp change not the current pv overage power is set but a weighted average since last amp set by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/127

Bugfixes

• Make amp change dependent on actual phases connected to car by @pkuehnel in https://github.com/pkuehnel/SmartTeslaAmpSetter/pull/123

Full Changelog: pkuehnel/smartteslaampsetter@v1.6.1...v1.7.0