Skip to content

v2.49.0

Latest

Choose a tag to compare

@pkuehnel pkuehnel released this 19 Oct 19:17
e342e39

What's Changed

Important notes before updating

  • If you use the BLE API: Also update the BLE API container (ghcr.io/pkuehnel/teslasolarchargerbleapi:latest). Your current container keeps working with this version, but the BLE fixes below marked with (BLE container) only apply after the update.

Features

  • Learned usable energy: Solar4Car now learns the usable energy of your cars and your home battery from past charges, instead of relying only on the value you entered. A value is used once at least 5 consistent measurements exist. For the home battery, the energy needed to charge it and the energy it delivers are learned separately, so the charging schedules and the dynamic home battery min SoC get more accurate. The values you entered are never changed and are still used until enough has been learned. The car dialog and the home battery setting show the learning status, a warning if the learned value differs a lot from the entered one, all measurements with the reason why one was not used, and a reset button. You can switch this off in Base Configuration with Learn usable energies from past charges by @pkuehnel in #2941
  • Tesla cloud key during car setup: Adding a Tesla now guides you in two steps: add the Solar4Car key to your car, then test the connection. Cars set up via Bluetooth get an optional, recommended fallback via the Tesla cloud, so a missing key shows up during setup instead of as an error on the home page by @pkuehnel in #2920
  • Rate limited Tesla cloud commands (BLE fallback for cars without car license, and wake ups) now ask the Solar4Car backend for the remaining command budget before they are sent. The Tesla cloud connection test no longer uses up that budget by @pkuehnel in #2919
  • SMA hybrid inverters: with home battery control enabled, a hint now tells you to disable Forecast-based battery charging in Sunny Home Manager / Sunny Portal. Otherwise it overrides Solar4Car's hold every minute and your house flips between grid and home battery by @pkuehnel in #2926
  • All texts now say Solar4Car, and "Fleet API" is now called "Tesla cloud" by @pkuehnel in #2918

Bugfixes

  • With a charge target (e.g. 80 %), a car that was plugged in for days could charge at full power from grid and home battery to catch up a few percent, although the target had already been reached. A car that is not charging and less than 3 % below its target now counts as having reached it, and a repeating target plans its next occurrence (solar first, then cheap grid) instead of catching up by @pkuehnel in #2936
  • With several solar/grid devices, a failing device (e.g. the grid meter) was silently left out of the totals, so charging was calculated from incomplete values. Solar values are now reported as not available while a device has an error, and template devices are included in that check. If one of your devices has been failing unnoticed, you will now see Solar values are not available by @pkuehnel in #2937
  • With several REST sources (e.g. multiple Home Assistant sensors), solar values could stop updating until Solar4Car was restarted by @pkuehnel in #2928
  • The estimated SoC of non-Tesla cars rose about 15 % too fast, as the charge loss was not taken into account by @pkuehnel in #2941
  • BLE presence: a car that left while the BLE container restarted could stay "at home" forever. Presence now follows one simple rule: heard within the last 3 minutes means at home, not heard by a running scan means away by @pkuehnel in #2927
  • With more than one BLE car, car data was often not refreshed (A second operation was started on this context instance), and two cars on the same Bluetooth adapter could report a healthy car as failing by @pkuehnel in #2922
  • (BLE container) The BLE container could get stuck for hours being unable to scan or connect, so Solar4Car kept showing old car values. The worker now restarts automatically by @pkuehnel in #2924
  • (BLE container) Background scan and presence detection did not run before the first car was paired, and pairing could silently unpair all cars by replacing the existing key. The key is now created on startup and never replaced during pairing by @pkuehnel in #2921
  • If the BLE container's clock was set back, the car state could freeze (e.g. shown as charging long after it stopped) until the container was restarted by @pkuehnel in #2930
  • Tesla cloud fallback commands: charge start/stop could be sent repeatedly, a BLE wake up blocked the cloud wake up for up to 30 minutes, a rejected wake up blocked all fallback commands for almost an hour, and a failed set current was remembered as set by @pkuehnel in #2935, #2919
  • Without a base license, the error message was empty and requests showed a misleading Could not deserialize vehicle. It now explains that no charging is controlled and where to get the license by @pkuehnel in #2939
  • Only 10 of the Smartcar compatible vehicles were shown when adding a car by @pkuehnel in #2940
  • After the app was in the background on a phone, the home battery color in the power flow could stay outdated until reload by @pkuehnel in #2925
  • More detailed BLE presence logging at log level Verbose to analyse BLE issues by @pkuehnel in #2923

Full Changelog: v2.48.2...v2.48.3