-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
scdoubleu
Member
I'd be interested in that too. Adjusting the DB timeout has not helped.
Got it, thanks. Confident I can get it sorted with this. Hopefully it resolves the issue going forward too.The code for closing individual drives is in the Github page although there is a typo.
I've got a script to close multiple drives if there are lots of them. I'll PM that over to you.
PS did a double take when I saw Cessnock in the map
Ah yes there's a cessnock in Scotland too!
scdoubleu
Member
240000
Now that I've looked again, I think it has been working after all. The remaining unclosed drives look to predate my timeout change. Your script gave me the clues I needed to clean up those stragglers.
RogerMc
Member
Help!
I messed with a dashboard and did a bad job. Now it is not functional. How can I restore it?
I've been unable to locate someplace where I can ask.
Thanks!
I messed with a dashboard and did a bad job. Now it is not functional. How can I restore it?
I've been unable to locate someplace where I can ask.
Thanks!
RogerMc
Member
You can also grab all the JSONs from the GitHub repo. Albeit if you want to restore some changes you made, as @init6 mentioned - your backup.
Dumb question - when I make changes to the YAML file, do those parameters get loaded when teslamate starts?
Yes, but technically when docker starts. The YAML file is the instructions docker reads to set up your 'application' e.g. start Teslamate, database, etc. and the parameters for each component. So if you make changes you need to down and then up docker.
Beauty, thanks. That's more or less what i assumed. I did do an up after changing the yaml but didn't down it first.
I will do that when the script to close all drives finishes. So slow... (Pi 3b+ on SD card)
Thanks for your help.
RogerMc
Member
I noticed I am getting the ENCRYPTION_KEY warning.
Added an entry to the yml (as below), bounced (docker-compose down & docker-compose up) the container, even rebooted. But I'm still getting the warning. Ideas? Thanks
services:
teslamate:
image: teslamate/teslamate:latest
restart: always
environment:
- ENCRYPTION_KEY=teslamate
- DATABASE_USER=teslamate
.
.
.
Added an entry to the yml (as below), bounced (docker-compose down & docker-compose up) the container, even rebooted. But I'm still getting the warning. Ideas? Thanks
services:
teslamate:
image: teslamate/teslamate:latest
restart: always
environment:
- ENCRYPTION_KEY=teslamate
- DATABASE_USER=teslamate
.
.
.
Anything in the logs?
This thread suggests you need to do a pull before bringing it back up.
github.com
This thread suggests you need to do a pull before bringing it back up.
No encryption key provided · teslamate-org teslamate · Discussion #2798
Hello, I've added the key in the yml file and Pi environment via /etc/profile, rebooted, but I always get the message "No encryption key provided". from the message I don't understand where the key...
github.com
RogerMc
Member
OK, found the logs and the generated key. Added gen'd key to the yml file. Still not fixed, but I am seeing this in logs and wondering what will need to be done. I don't want to lose data. Confirmed, I *AM* losing data because TeslaMate doesn't see that my car is charging. Arrrrrg, what can be done?Anything in the logs?
This thread suggests you need to do a pull before bringing it back up.
No encryption key provided · teslamate-org teslamate · Discussion #2798
Hello, I've added the key in the yml file and Pi environment via /etc/profile, rebooted, but I always get the message "No encryption key provided". from the message I don't understand where the key...
teslamate_1 | 2023-05-18 14:32:09.847 car_id=1 [error] Error / not_signed_in
teslamate_1 | 2023-05-18 14:32:09.857 car_id=3 [error] Error / not_signed_in
teslamate_1 | 2023-05-18 14:32:09.870 car_id=4 [error] Error / not_signed_in
teslamate_1 | 2023-05-18 14:32:09.895 car_id=5 [error] Error / not_signed_in
Last edited:
RogerMc
Member
Trying to login with newly gen'd access & refresh tokens, but TeslaMate reports "Error: Tokens are invalid"
Similar threads
