Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

TeslaMate [megathread]

This site may earn commission on affiliate links.
#3,441
Medved_77 said:
Thanks! That was the case, actually upgraded from 18>22 😲

Wasn't smooth though, was failing due to some issues with the lxd client so had to purge that first.

Now running latest Teslamate version and will try to remember to keep on top of these things in future! :)
Click to expand...
I've just upgraded to TeslaMate v1.28.5 (from .2 I think!) and now the TeslaMate dock is constantly restarting. Just checked and I'm running docker 19 on Debian 9 (see below), so looks like I need to upgrade docker to v22? I've already done an apt-get update and apt-get upgrade, but it's not updated anything. Do you have the step-by-step instructions for what you did to force the upgrade?

myinstance@tm-f1-micro:~$ docker version
Client: Docker Engine - Community
Version: 19.03.15
API version: 1.40
Go version: go1.13.15
Git commit: 99e3ed8919
Built: Sat Jan 30 03:17:11 2021
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.15
API version: 1.40 (minimum version 1.12)
Go version: go1.13.15
Git commit: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Built: Sat Jan 30 03:15:40 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.3
GitCommit: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
runc:
Version: 1.0.0-rc92
GitCommit: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
docker-init:
Version: 0.18.0
GitCommit: fec3683

myinstance@tm-f1-micro:~$ hostnamectl
Static hostname: n/a
Transient hostname: tm-f1-micro
Icon name: computer-vm
Chassis: vm
Machine ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Boot ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Virtualization: kvm
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.9.0-14-amd64
Architecture: x86-64
 
#3,442
@Blokie These aren't exact instructions, just what I can recall. Before running this, ensure you know how to revert if necessary.

Alternatively, if you just want to revert to the previous working version of teslamate you can update the docker-compose.yml file, switching out the latest image for a specified version.

Code: 
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo do-release-upgrade
reboot

During the update process I encountered an error related to the lxd-client. Resolved this with:

Code: 
sudo apt purge lxd lxd-client
 
#3,443
Medved_77 said:
@Blokie These aren't exact instructions, just what I can recall. Before running this, ensure you know how to revert if necessary.

Alternatively, if you just want to revert to the previous working version of teslamate you can update the docker-compose.yml file, switching out the latest image for a specified version.

Code: 
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo do-release-upgrade
reboot

During the update process I encountered an error related to the lxd-client. Resolved this with:

Code: 
sudo apt purge lxd lxd-client
Click to expand...
I don't think that will work. (It didn't for me, because Debian 9 has been deprecated and the sources have been archived. Security repo for Debian stretch not working anymore) I tried updating the sources and couldn't get anything to upgrade, so I gave up and just built a new Debian 12 VM and once I got it working I just backed up the data on the old one and restored to the new one.
 
#3,444
Medved_77 said:
@Blokie These aren't exact instructions, just what I can recall. Before running this, ensure you know how to revert if necessary.

Alternatively, if you just want to revert to the previous working version of teslamate you can update the docker-compose.yml file, switching out the latest image for a specified version.

Code: 
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo do-release-upgrade
reboot

During the update process I encountered an error related to the lxd-client. Resolved this with:

Code: 
sudo apt purge lxd lxd-client
Click to expand...
Thanks. I've reverted to 25.3 (25.4 had the same issue) and working fine, but I'd like to get the upgrade working. The issue is a bunch of errors when I even try to do the apt update...

Code: 
myinstance@tm-f1-micro:~$ sudo apt update
Hit:1 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:2 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease                             
Hit:3 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease                   
Ign:4 http://deb.debian.org/debian stretch InRelease                     
Ign:5 http://security.debian.org stretch/updates InRelease               
Ign:6 http://deb.debian.org/debian stretch-updates InRelease             
Err:7 http://security.debian.org stretch/updates Release                 
  404  Not Found
Ign:8 http://deb.debian.org/debian stretch-backports InRelease           
Err:9 http://deb.debian.org/debian stretch Release
  404  Not Found
Err:10 http://deb.debian.org/debian stretch-updates Release
  404  Not Found
Err:11 http://deb.debian.org/debian stretch-backports Release
  404  Not Found
Get:12 https://download.docker.com/linux/debian stretch InRelease [44.8 kB]
Reading package lists... Done                                   
E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-backports Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
 
#3,445
MP3Mike said:
I don't think that will work. (It didn't for me, because Debian 9 has been deprecated and the sources have been archived. Security repo for Debian stretch not working anymore) I tried updating the sources and couldn't get anything to upgrade, so I gave up and just built a new Debian 12 VM and once I got it working I just backed up the data on the old one and restored to the new one.
Click to expand...

Just seen this reponse after posting my latest update - seems this is exactly the issue I'm now facing. Looks like I'm going to have to create a new Debian12 disk when I get the chance.
 
#3,449
init6 said:
9-10 and that was enough to upgrade docker to get Teslamate working.
Click to expand...

So how did you do the upgrade with the Debian 9 sources having been deprecated? This is what I get when I try the upgrade...

Code: 
myinstance@tm-f1-micro:~$ sudo apt update
Hit:1 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:2 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease                             
Ign:3 http://security.debian.org stretch/updates InRelease                                     
Ign:4 http://deb.debian.org/debian stretch InRelease                                           
Hit:5 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease
Err:6 http://security.debian.org stretch/updates Release                                       
  404  Not Found
Ign:7 http://deb.debian.org/debian stretch-updates InRelease             
Ign:8 http://deb.debian.org/debian stretch-backports InRelease
Err:9 http://deb.debian.org/debian stretch Release
  404  Not Found
Err:10 http://deb.debian.org/debian stretch-updates Release
  404  Not Found
Err:11 http://deb.debian.org/debian stretch-backports Release
  404  Not Found
Get:12 https://download.docker.com/linux/debian stretch InRelease [44.8 kB]
Reading package lists... Done                                   
E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-backports Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


myinstance@tm-f1-micro:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  firmware-linux-free google-cloud-cli linux-image-4.9.0-19-amd64
The following packages will be upgraded:
  google-cloud-sdk linux-image-amd64
2 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 145 MB of archives.
After this operation, 65.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://packages.cloud.google.com/apt cloud-sdk-stretch/main amd64 google-cloud-sdk all 467.0.0-0 [1,706 B]
Get:2 http://packages.cloud.google.com/apt cloud-sdk-stretch/main amd64 google-cloud-cli amd64 471.0.0-0 [105 MB]                                               
Get:3 http://deb.debian.org/debian stretch/main amd64 firmware-linux-free all 3.4 [19.2 kB]                           
Err:4 http://security.debian.org stretch/updates/main amd64 linux-image-4.9.0-19-amd64 amd64 4.9.320-2   
  404  Not Found
Err:5 http://security.debian.org stretch/updates/main amd64 linux-image-amd64 amd64 4.9+80+deb9u17
  404  Not Found
Fetched 105 MB in 2s (46.5 MB/s)                                 
E: Failed to fetch http://security.debian.org/pool/updates/main/l/linux/linux-image-4.9.0-19-amd64_4.9.320-2_amd64.deb  404  Not Found
E: Failed to fetch http://security.debian.org/pool/updates/main/l/linux-latest/linux-image-amd64_4.9+80+deb9u17_amd64.deb  404  Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?


myinstance@tm-f1-micro:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  firmware-linux-free google-cloud-cli linux-image-4.9.0-19-amd64
The following packages will be upgraded:
  google-cloud-sdk linux-image-amd64
2 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.5 MB/145 MB of archives.
After this operation, 65.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://security.debian.org stretch/updates/main amd64 linux-image-4.9.0-19-amd64 amd64 4.9.320-2
  404  Not Found
Err:2 http://security.debian.org stretch/updates/main amd64 linux-image-amd64 amd64 4.9+80+deb9u17
  404  Not Found
E: Failed to fetch http://security.debian.org/pool/updates/main/l/linux/linux-image-4.9.0-19-amd64_4.9.320-2_amd64.deb  404  Not Found
E: Failed to fetch http://security.debian.org/pool/updates/main/l/linux-latest/linux-image-amd64_4.9+80+deb9u17_amd64.deb  404  Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
 
#3,451
Blokie said:
Thanks. I've reverted to 25.3 (25.4 had the same issue) and working fine, but I'd like to get the upgrade working. The issue is a bunch of errors when I even try to do the apt update...

Code: 
myinstance@tm-f1-micro:~$ sudo apt update
Hit:1 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:2 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease                            
Hit:3 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease                  
Ign:4 http://deb.debian.org/debian stretch InRelease                    
Ign:5 http://security.debian.org stretch/updates InRelease              
Ign:6 http://deb.debian.org/debian stretch-updates InRelease            
Err:7 http://security.debian.org stretch/updates Release                
  404  Not Found
Ign:8 http://deb.debian.org/debian stretch-backports InRelease          
Err:9 http://deb.debian.org/debian stretch Release
  404  Not Found
Err:10 http://deb.debian.org/debian stretch-updates Release
  404  Not Found
Err:11 http://deb.debian.org/debian stretch-backports Release
  404  Not Found
Get:12 https://download.docker.com/linux/debian stretch InRelease [44.8 kB]
Reading package lists... Done                                  
E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-backports Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Click to expand...
TBH, I can't remember which version I upgraded from, was all a bit rushed.
 
#3,452
Th
init6 said:
I googled "upgrade Debian from 9 to 10" and followed one of the many sets of instructions :)

IIRC this one:

Click to expand...
Thanks - I've successfully upgraded to Debian 10 (buster) - clearly going from 9 to 12 (I'd used the same process and it failed badly!) was too much for it.

I've also updated TM to 28.5 too and that's working fine.
 
  • Like
Reactions: cwanja and GeorgeSymonds
#3,454
init6 said:
I suspect your mistake was not to change the references to stretch in the sources.list file, hence the mentions of stretch in your errors.
Click to expand...
I thought I'd captured them all (sources.list and the various files in sources.list.d folder), but maybe not. When I get the time I might upgrade from 10 to 12 so I'm completely current (might even go 10 -> 11 -> 12).
 
#3,458
I have created Teslamate dashboard for my personal use which focuses on speed and temperature related statistics. There are few options on the top of the dashboard to finetune the panels, selected date range also affects the panel data.

Screenshot below.

If you would to try or use it, you can download it from: GitHub - tero-jarvinen/teslamate-speed-temperature: Speed and temperature related dashboard for Teslamate

If you are using miles instead of kilometers, download the correct json file. One uses kilometers and the other one miles.


speed-temperature-consumption.jpg
 
  • Like
  • Love
  • Helpful
Reactions: zknobody, Dave EV, bsf29 and 6 others
#3,459
Very nice, just a couple of points.
I had to change my datasource manually in the JSON section of the dashboard - not sure if I missed something while importing - it's late here :)

The short and Long trip consumption panel still has km in the miles json.

But a very good addition to Teslamate.
 
#3,460
init6 said:
I had to change my datasource manually in the JSON section of the dashboard - not sure if I missed something while importing - it's late here :)

The short and Long trip consumption panel still has km in the miles json.
Click to expand...
I fixed the short and long trip unit problem. Also updated it to only include two trip lengths, three was probably too much for it.

But I could not find out what caused the datasource problem. If someone knows the reason I'll fix it.
 
  • Like
Reactions: init6
You must log in or register to reply here.

Similar threads

K
M3 windows opened/vented themselves this morning
Replies
5
Views
540
The UK and Ireland
dirty_park
D
J
Question: How to report cameras to Tesla navigation's new speed camera detection feature?
Replies
10
Views
663
Software: Firmware Updates, Features, Tesla App
Cley
C
X
Using Fleet API to Control My Powerwall Reserve Percentage
Replies
25
Views
2K
Tesla Energy
Mark Purcell
Mark Purcell
A
Switch from TeslaMate to Tessie
Replies
3
Views
4K
Software: Firmware Updates, Features, Tesla App
Muffstic
M
J
Why has Tesla taken so long to sort how 2 Gateways are "seen" in the app?
Replies
6
Views
575
Tesla Energy
BGbreeder
B
Top
Back
Blog
New
Forum list
Marketplace
Menu