TeslaMate changelog

Changelog History

Page 6

• v1.12.0 Changes

  October 28, 2019

  📚 We finally have documentation! Many thanks to @ngardiner, who gave the impulse and did most of the work and also to @krezac, who contributed a guide to creating iOS Shortcuts for TeslaMate!

  🆕 New Features

  Vehicle Efficiency

  Previous versions of TeslaMate shipped with hard-coded efficiency values for the various Tesla models. These efficiency values are needed to calculate trip consumptions, because the Tesla API does not provide them directly.

  The hard-coded values were probably pretty accurate, but it was impossible to ensure the correctness of all of them. In addition, the new Model S and X "Raven" could not be reliably identified because the Tesla API returns wrong option codes for both.

  This version eliminates the need to use these hard-coded values and instead calculates them based on the recorded charging data. It takes at least two charges to display the first estimate. Each subsequent charge will then continue to improve the accuracy of the estimate, which is applied retroactively to all data.

  Charge energy used

  In addition to the kWh added to the battery during the charge TeslaMate now calculates the actual energy used by the charger, which in most cases is higher than the energy added to the battery.

  Consider this feature somewhat experimental. Theoretically, however, it should be pretty accurate as long as the vehicle has a stable internet connection while charging (other paid Tesla loggers use the same calculation method).

  ↪ Currently, a firmware bug in some vehicles may cause the wrong number of phases to be reported when charging at some chargers. As a workaround, a phase correction can be activated per geo-fence.

  🆕 New MQTT Topics

  • ⚡️ teslamate/cars/$car_id/update_available
  • teslamate/cars/$car_id/is_climate_on
  • teslamate/cars/$car_id/is_preconditioning
  • teslamate/cars/$car_id/is_user_present

  ✨ Enhancements

  • 🏁 Show icon indicators for various states (sentry mode, vehicle locked, windows open, pre-conditioning etc.)
  • 💻 Various UI Tweaks
  • Grafana: show the precise duration of a trip in a tooltip
  • 🍱 Serve gzipped assets
  • 🍱 Disable origin check by default to simplify the installation of TeslaMate. (⚠️ For publicly exposed TeslaMate instances it is advisable to re-enable the check by adding the environment variable CHECK_ORIGIN=true.)

  🐛 Bug Fixes

  • Set the correct end date for charges where the vehicle remains plugged in after completion
  • 🛠 Fix an issue with vehicles that were removed from the Tesla Account
  • Correctly handle API responses which indicate that the vehicle is in service
  • Display effects of range gains (e.g. from supercharging pre-conditioning a cold battery) as NULL

  ---

  TeslaMate is open source and completely free for everyone to use.
  
  If you like this project and want to support further development, please consider making a donation.
  

• v1.11.1 Changes

  October 13, 2019

  🐛 Bug Fixes

  • 👉 Show all cars in the Overview dashboard

• v1.11.0 Changes

  October 12, 2019

  🆕 New Features

  • ➕ Add overview dashboard (by DBemis;
    #196)
  • 🔧 Make :check_origin option configurable via environment variable
    CHECK_ORIGIN
  • 🚀 Open GitHub release page when clicking the version tag in the navbar
  • Display the current software version

  🆕 New MQTT topics

  • teslamate/cars/$car_id/version: Current software version

  ✨ Enhancements

  • 👉 Tweak the mobile and desktop views
  • Add GIST index based on ll_to_earth to speed up geo-fence lookups
  • 👌 Improve accuracy of geo-fence lookups for some edge cases
  • 🌲 Log option codes as well if the vehicle identification fails
  • ✂ Delete trips with less than 10m driven
  • ➕ Add/Update efficiency factors

  🐛 Bug Fixes

  • 🛠 Fix an issue where postgres' automatic analyze couldn't succeed
  • 🛠 Fix an issue where the derived efficiency factors could not be calculated
  • Exit early if migrations fail
  • ⬇️ Downgrade Grafana to v6.3.5

• v1.10.0 Changes

  October 05, 2019

  ✨ Enhancements

  • 👍 Allow editing of geo-fence positions
  • ⚠ Show warning icon if the health check fails for a vehicle
  • 👉 Use the best available SRTM data source which provides global elevation data
    including 60N and above
  • ⚡️ Optimize the comparison of geo-fences by moving the lookup into the database
  • 👉 Use the exact position instead of the center of an address for the geo-fence
    lookup
  • Generally improve error handling and error messages

  • 👌 Improve landscape mode on devices with a notch

  Open the geo-fence editor by clicking on the start or destination address of
  a trip

  Note: For this feature to work Grafana needs to know the base URL of the
  🌐 TeslaMate web interface. To automatically set the base URL open the web
  ⬆️ interface once after upgrading to this version. Manually changing the base
  URL is possible via the settings page.

  🆕 New MQTT topics

  • teslamate/cars/$car_id/healthy: Reports the health status of the logger
  • 🏁 teslamate/cars/$car_id/windows_open
  • teslamate/cars/$car_id/shift_state
  • teslamate/cars/$car_id/latitude
  • teslamate/cars/$car_id/longitude
  • teslamate/cars/$car_id/odometer
  • teslamate/cars/$car_id/charge_port_door_open
  • teslamate/cars/$car_id/charger_actual_current
  • teslamate/cars/$car_id/charger_phases
  • teslamate/cars/$car_id/charger_power
  • teslamate/cars/$car_id/charger_voltage
  • teslamate/cars/$car_id/time_to_full_charge

  🐛 Bug Fixes

  • Automatically restart parts of the application if Tesla decides yet again to
    🔄 change the IDs of some vehicles
  • Request to sign in again if the access tokens become invalid e.g. because the
    password of the Tesla Account has been changed
  • ⚡️ Protect against empty payloads during an update to prevent an update from
    not being fully logged
  • 🌲 Log the number of charging phases as returned by the API

  🍱 ⚠️ Running Migrations

  🐳 Users of the default docker-compose.yml can skip this part.

  To run the migrations successfully, the database user has to have
  superuser rights (temporarily):

  • To add superuser rights: ALTER USER teslamate WITH SUPERUSER;
  • 🚚 To remove superuser rights: ALTER USER teslamate WITH NOSUPERUSER;

• v1.9.1 Changes

  September 24, 2019

  🐛 Bug Fixes

  • Set position when selecting a search entry
  • 🛠 Fix deletion of geo-fences

• v1.9.0 Changes

  September 24, 2019

  ➕ Added

  • 🌐 Show a map with the current vehicle position on the web interface
  • ➕ Add a satellite/hybrid layer to the geo-fence map
  • 👉 Use elevation data with 1 arc second (~30m) accuracy everywhere not just in
    the US
  • ➕ Add support for MQTT SSL (#140)
  • ➕ Add "Charged" annotation to the degradation dashboard
  • ➕ Add preferred range setting: you can now choose between "ideal" and "rated"
    range to use as the basis for efficiency and other metrics

  🔄 Changed

  Require a data source named "TeslaMate":

  🐳 If you don't run the teslamate/grafana docker container the Grafana data
  0️⃣ source has to have the name "TeslaMate". Prior to this change the default
  data source was used.

  Renamed the MQTT topic teslamate/cars/$car_id/battery_range_km to
  teslamate/cars/$car_id/rated_battery_range_km.

  🛠 Fixed

  • ⚡️ Prevent suspending when an update is in progress
  • 🛠 Fix charge counter when using with multi vehicles
    (#175)

  ✂ Removed

  • ⬇️ Drop support for the deprecated env variables TESLA_USERNAME and
    TESLA_PASSWORD

• v1.8.0 Changes

  September 03, 2019

  ➕ Added

  • Identify cars by VIN: This hopefully eliminates any upcoming problems when Tesla decides yet again to change the IDs of their cars ...
  • Pick geo-fences from a map and show their radius

  🛠 Fixed

  • Only add elevation to positions for which SRTM elevation data is available
  • 🔒 [Security] Bump Grafana version

• v1.7.0 Changes

  August 29, 2019

  ➕ Added

  • Locally (!) query all locations for elevation data from the NASA Shuttle Radar Topography Mission (SRTM)
  • ➕ Add elevation graph to the Drive Details dashboard
  • 🌐 Display rated range on the web interface and on the Drive Details dashboard
  • Switch to the vehicle_config API endpoint to identify vehicles
  • 0️⃣ Display the default and derived efficiency factor on the Efficiency dashboard to detect inaccuracies and to crowdsource the correct factors:

  Note: If there is no default efficiency factor or you think the default factor for your vehicle might be wrong, please open an issue and attach a screenshot of the table showing the efficiency factor(s) for your vehicle.

  • 🌐 Display charger power on the web interface

  🛠 Fixed

  • Fix calculation of charge_energy_added if a previously stopped charge session is resumed

• v1.6.2 Changes

  August 26, 2019

  🛠 Fixed

  • 🛠 Fix migration that could panic when upgrading from v1.4 to v1.6
  • 🛠 Fix efficiency calculation

• v1.6.1 Changes

  August 25, 2019

  ➕ Added

  • ➕ Add separately configurable sleep requirements

  🛠 Fixed

  • 👌 Improve identification of performance models
  • 🛠 Fix Model X identification
  • 👌 Improve browser compatibility of the web interface
  • Disable basic auth in Grafana
  • ✂ Remove pre-calculated consumption columns and instead calculate consumption values dynamically based on the given efficiency factor
  • ➕ Add various database constraints to keep data in a consistent state

• « First
• ‹ Prev
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• Next ›
• Last »