Skip to content

v1.10

Compare
Choose a tag to compare
@adriankumpf adriankumpf released this 05 Oct 13:17
· 1924 commits to master since this release

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;