Bot releases are hidden (Show)
Published by JakobLichterfeld 7 months ago
Published by JakobLichterfeld 9 months ago
To ensure time-related features display accurately in your local timezone, configure the TZ environment variable.
Detailed instructions are available in our configuration guide.
Full Changelog: https://github.com/teslamate-org/teslamate/compare/v1.28.2...v1.28.3
Published by JakobLichterfeld 11 months ago
Full Changelog: https://github.com/teslamate-org/teslamate/compare/v1.28.1...v1.28.2
Published by JakobLichterfeld 11 months ago
Note: First release as @teslamate-org organization.
Full Changelog: https://github.com/teslamate-org/teslamate/compare/v1.28.0...v1.28.1
Full Changelog: https://github.com/teslamate-org/teslamate/compare/v1.27.4...v1.28.0
Published by JakobLichterfeld 11 months ago
Note: First release as @teslamate-org organization.
Full Changelog: https://github.com/teslamate-org/teslamate/compare/v1.27.4...v1.28.0
Published by adriankumpf 11 months ago
Note: TeslaMate moved to the new @teslamate-org organization.
vehicle_data
request to reflect changes to the API (#3398 - @swiffer)DATABASE_SSL_CA_CERT_FILE
)end_date
as dateTimeAsLocal
(#3033 - @DrMichae)Full Changelog: https://github.com/teslamate-org/teslamate/compare/v1.27.3...v1.27.4
Published by adriankumpf over 1 year ago
vehicle_data
response as Tesla has made some changes to the APIFull Changelog: https://github.com/adriankumpf/teslamate/compare/v1.27.2...v1.27.3
Published by adriankumpf almost 2 years ago
Full Changelog: https://github.com/adriankumpf/teslamate/compare/v1.27.1...v1.27.2
Published by adriankumpf about 2 years ago
Protocol 'inet_tcp': register/listen error: econnrefused
error (#2771 - @manuduarte)Full Changelog: https://github.com/adriankumpf/teslamate/compare/v1.27.0...v1.27.1
Published by adriankumpf over 2 years ago
To ensure that the Tesla API tokens are stored securely, an encryption key must be provided via the ENCRYPTION_KEY
environment variable.
If you use a docker-compose.yml
file to run TeslaMate, add a line with the ENCRYPTION_KEY
to the environment
section or check out the updated installation guiddes on docs.teslamate.org:
services:
teslamate:
image: teslamate/teslamate:latest
environment:
- ENCRYPTION_KEY=your_secret_encryption_key
# ...
If no ENCRYPTION_KEY
environment variable is provided when running the database migrations a randomly generated key will be set for you to encrypt the tokens. In that case, a warning with further instructions will be displayed.
charge_current_request
and charge_current_request_max
MQTT topicsDEFAULT_GEOFENCE
environment variable (#2564)Full Changelog: https://github.com/adriankumpf/teslamate/compare/v1.26.1...v1.27.0
Published by adriankumpf over 2 years ago
Published by adriankumpf over 2 years ago
libseccomp2
(see #2302)⚠️ Manually managed Grafana instances have to be upgraded to v8.3.4 or higher!
Published by adriankumpf almost 3 years ago
GLIBC_2.29' not found
errorPublished by adriankumpf almost 3 years ago
Disable anonymous logins to Grafana by default (when using the teslamate/grafana
Docker image)
admin
with the password admin
. After successful login, you will be prompted to change the password.GF_AUTH_ANONYMOUS_ENABLED
to true
(use only if your Grafana instance is not exposed to the internet!)This change only affects users who followed the basic Docker installation guide which, as mentioned in the guide, is intended for home network use only and not for exposure to the internet. Users who followed one of the advanced installation guides are not affected as their Grafana instances always had anonymous logins disabled.
Published by adriankumpf almost 3 years ago
Published by adriankumpf about 3 years ago
Published by adriankumpf about 3 years ago
⚠️ NOTE: Tesla have tightened the captcha security once again and now require Google reCAPTCHA to generate API tokens. reCAPTCHA is implemented in a way that makes it impossible to bypass for applications like TeslaMate. There are third-party services that offer to fill these captchas (by having humans solve them manually), but they're slow and can be pricey if you're making a large amount of requests.
So if you are having issues signing in to your Tesla account via TeslaMate, the only remaining workaround right now is to sign in using existing API tokens
(there is a button on the TeslaMate sign-in form). There are multiple apps available to securely generate access tokens yourself, for example:
Users who are already signed in in do not have to worry about it. TeslaMate will continue to be able to access the Tesla API.
Published by adriankumpf about 3 years ago
display_priority
column in the cars
database tablePublished by adriankumpf over 3 years ago