TeslaMate [megathread]

[cwanja]

some commands I may try to figure out the drive ID numbers or whatever to see if they even exist in the db.

In addition to @shyboy questions, are there drives after those dates logged? If so, can you see in the URL the `drive_id` and is there a skipped ID? If so, you might need to manually close the drive. Same thing for charges.

Manually fixing data | TeslaMate

Get the ID

docs.teslamate.org

 

[Blokie]

I have been running teslamate since probably Feb 2023, and it appeared to capture all the data real well. I run it on a synology using docker, and I checked today and it auto-updates and is at the current version.

The issue I'm facing is that on 11/11/23 I took the car for it's furthest drive ever, nearly 600 miles round trip, charging 4 times enroute, which were actually my only times I've used a supercharger. When I went to look at the data, the drives don't show up, the charging sessions don't show up, and the "visited" dashboard in teslamate doesn't have that long drive depicted anywhere. Is this data lost forever? So far other than the install on docker, which was easy by following a guide, is the only experience I have with digging into it. I found some threads on terminating drives, and such, but the command don't seem to be based on my synology docker type install. Wondering if anyone can give me insight into what the chances are that my data can be displayable from that long trip, or some commands I may try to figure out the drive ID numbers or whatever to see if they even exist in the db.

Anything is appreciated.

Have subsequent drives since then appeared in Teslamate?

 

[cwanja]

After updating back to the original Teslamate image:
View attachment 992669

Also, last drives are from 10/11/2023, nothing newer and for whatever reason the States segment of the graph is soooo zooomed in that it does not show anything...

Is your Tesla asleep? What if you wake it up, does the dashboards update?

The states visualization looks normal, it is just showing that your car is asleep for the last 24 hours which is the default timeline for that dashboard.

 

[DeltaOne]

I have been running teslamate since probably Feb 2023, and it appeared to capture all the data real well. I run it on a synology using docker, and I checked today and it auto-updates and is at the current version.

The issue I'm facing is that on 11/11/23 I took the car for it's furthest drive ever, nearly 600 miles round trip, charging 4 times enroute, which were actually my only times I've used a supercharger. When I went to look at the data, the drives don't show up, the charging sessions don't show up, and the "visited" dashboard in teslamate doesn't have that long drive depicted anywhere. Is this data lost forever? So far other than the install on docker, which was easy by following a guide, is the only experience I have with digging into it. I found some threads on terminating drives, and such, but the command don't seem to be based on my synology docker type install. Wondering if anyone can give me insight into what the chances are that my data can be displayable from that long trip, or some commands I may try to figure out the drive ID numbers or whatever to see if they even exist in the db.

Anything is appreciated.

I had been running TeslaMate on my Synology using Docker for 2.5 years. Then the news that TeslaMate may quit working after 12/31.

My TeslaMate missed a drive on 11/4. That, and the news of it maybe ceasing to function, I moved to Tessie.

So far I like Tessie very much. I was able to export my TeslaMate data and import into Tessie. If you decide to look for alternatives, I can recommend Tessie. I considered TeslaFi too. Both cost $50/year. The Tessie app and dashboard (viewed in a web browser) are quite nice.

 

[init6]

I have been running teslamate since probably Feb 2023, and it appeared to capture all the data real well. I run it on a synology using docker, and I checked today and it auto-updates and is at the current version.

The issue I'm facing is that on 11/11/23 I took the car for it's furthest drive ever, nearly 600 miles round trip, charging 4 times enroute, which were actually my only times I've used a supercharger. When I went to look at the data, the drives don't show up, the charging sessions don't show up, and the "visited" dashboard in teslamate doesn't have that long drive depicted anywhere. Is this data lost forever? So far other than the install on docker, which was easy by following a guide, is the only experience I have with digging into it. I found some threads on terminating drives, and such, but the command don't seem to be based on my synology docker type install. Wondering if anyone can give me insight into what the chances are that my data can be displayable from that long trip, or some commands I may try to figure out the drive ID numbers or whatever to see if they even exist in the db.

Anything is appreciated.

In addition to what @shyboy said, what version of Teslamate are you using? There have been a few ad hoc version of late, so the precise version would be handy. Also what version of software do you have in your car? There was a change recently that stopped Teslamate from working.
What do you see in the logs? Any errors?

 

[RVTim]

is the only drive missing is the 11/11?
is the data is pulled and saved as of 11/21?

As far as the missing drive(s), I can't say with 100% certainty that it's the ONLY one, but it does log most every day. Now that you ask that though,
I don't have any drives showing from 11/9 thru 11/14, but I think I only drove possibly on 11/10 and 11/11 out of those days. So it is possible that 11/10 is also missing.

When you ask about the data being pulled and saved, I'm assuming you mean automatically pulled by teslamate, right? I do have drives from 11/15-11/20, basically every single day, so it's been pulling data since after the gap days.

 

[RVTim]

Software versions I can provide for today, but since a few days have passed I can't say for sure what versions were running on either on that 11/10-11/11 time period.
Today my teslamate says 1.27.4 for version.
The car is a model Y and is 2023.38.6 today.

I do have about 25 drive entries listed between 11/15 and 11/20 (haven't driven today yet), so it does appear to still be logging.

Thanks for the recommendation for Tessie as a site. Generally I shy away from anything that has a significant cost/yr, and $50 is a lot when you can do it yourself on your own hardware, but I may consider going that route if this isn't going to be reliable. It's really sad that the FIRST long trip I ever did, where I could record significant miles and charges, aren't listed. Would love to get them listed.

I'd been happy with Teslamate until this point.

 

[init6]

I don't know your skill level, but you should be able to find (or check for) unclosed drives by running this query in the database or via grafana:

SELECT
id,
start_date,
start_address_id,
end_address_id
FROM drives
WHERE
end_date is null
ORDER BY 1

That should give you a list of unclosed drive records.

 

[yessuz]

Is your Tesla asleep? What if you wake it up, does the dashboards update?

The states visualization looks normal, it is just showing that your car is asleep for the last 24 hours which is the default timeline for that dashboard.

by default, it is very zoomed in. once I zoom out (to let's say last 2 days) - it shows all. it is either corrupt data or connection...

dashboard parts without data shows empty bits of dashboard.

 

[yessuz]

could it be that after each image change I need to reconnect car with teslamate?!

 

[init6]

could it be that after each image change I need to reconnect car with teslamate?!

|'ve never had to do that after an update.

 

[init6]

Just had a look at your image @yessuz Looks like data is missing. What do you see in the logs?

 

[electrikcuban]

Wondering if anyone here is able to import from TeslaFi into Teslamate anymore. I'm trying to import my data, but after reading some posts, looks like I needed to add a "1" under the "vehicle_id" column.
Unfortunately after I do this (using notepad++ to edit the file), Teslamate doesn't even process the file. It shows a checkmark like it worked, but nothing gets added.
One thing to note, if I import an older file (lets say April 2023), after making the same change, it works fine.

Anyone has any idea why this doesn't work?

 

[init6]

Anyone has any idea why this doesn't work?

What do the log files say?

 

[RVTim]

Just catching back up on the thread. I do see that my drive 1207 is there, and 1209 is there. Those are the last drive before the gap and the first drive after the gap. So it may be correct that I just have to close out drive 1208. I'm not super low-skilled, but not a super expert either. Mainly due to the fact that I've not worked much with docker. Been in IT for 25+ years and spent time with sql/oracle/mysql and done all sorts of things, so this shouldn't be super hard to figure out, once I figure out the nomenclature for getting connected to the db. The catch is, a lot of info out there doesn't seem to address synology docker installs, so some of the commands differ. Got to go do some volunteer work but Thanksgiving day is gonna be a slow one for me this year so I should be able to sit down and dig in.

Oh, one example of the commands is, on the "how to close a drive" tip that I saw, it uses "docker compose" but in my instance it's "docker-compose" I believe. So I have to get that figured out. Not sure what else is different.

 

[electrikcuban]

What do the log files say?

There were no errors, however I figured out how to fix this. I deleted and rebuilt the containers. Then just added the "1" under vehicle_id to the first line that also had the vehicle name. I had to do this within my linux box using nano editor though. Using any other editor and uploading the file would not work. I succesfully imported about 7 months worth of data. Graphs look really nice now.

 

[init6]

Just catching back up on the thread. I do see that my drive 1207 is there, and 1209 is there. Those are the last drive before the gap and the first drive after the gap. So it may be correct that I just have to close out drive 1208. I'm not super low-skilled, but not a super expert either. Mainly due to the fact that I've not worked much with docker. Been in IT for 25+ years and spent time with sql/oracle/mysql and done all sorts of things, so this shouldn't be super hard to figure out, once I figure out the nomenclature for getting connected to the db. The catch is, a lot of info out there doesn't seem to address synology docker installs, so some of the commands differ. Got to go do some volunteer work but Thanksgiving day is gonna be a slow one for me this year so I should be able to sit down and dig in.

Oh, one example of the commands is, on the "how to close a drive" tip that I saw, it uses "docker compose" but in my instance it's "docker-compose" I believe. So I have to get that figured out. Not sure what else is different.

As long as you can ssh or run the docker-compose commands then you'll be fine.
Just note there is a typo in the official doc for closing drives. There's a spurious ! between Teslamate.Repo.get and the opening bracket preceding Teslamate.Log.Drive.xxx

 

[yessuz]

Just had a look at your image @yessuz Looks like data is missing. What do you see in the logs?

@init6

Spoiler: log

pi@raspberrypi:~ $ docker-compose logs teslamate
Attaching to pi_teslamate_1
teslamate_1 | 2023-11-20 01:01:55.253 [info] Migrations already up
teslamate_1 | 2023-11-20 01:01:58.706 [info] System Info: Erlang/OTP 26 (emu)
teslamate_1 | 2023-11-20 01:01:58.707 [info] Version: 1.27.4
teslamate_1 | 2023-11-20 01:01:58.711 [warning]
teslamate_1 | ------------------------------------------------------------------------------
teslamate_1 | No ENCRYPTION_KEY was found to encrypt and securely store your API tokens.
teslamate_1 |
teslamate_1 | Therefore, the following randomly generated key will be used instead for this
teslamate_1 | session:
teslamate_1 |
teslamate_1 |
teslamate_1 | [CENSORED]
teslamate_1 |
teslamate_1 |
teslamate_1 | Create an environment variable named "ENCRYPTION_KEY" with the value set to
teslamate_1 | the key above (or choose your own) and pass it to the application from now on.
teslamate_1 |
teslamate_1 | OTHERWISE, A LOGIN WITH YOUR API TOKENS WILL BE REQUIRED AFTER EVERY RESTART!
teslamate_1 | ------------------------------------------------------------------------------
teslamate_1 |
teslamate_1 | 2023-11-20 01:01:59.352 [warning] Could not decrypt API tokens!
teslamate_1 | 2023-11-20 01:01:59.358 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
teslamate_1 | 2023-11-20 01:01:59.360 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate_1 | 2023-11-20 01:01:59.456 [warning] Using fallback vehicles:
teslamate_1 |
teslamate_1 | [
teslamate_1 | %TeslaApi.Vehicle{
teslamate_1 | id: [CENSORED],
teslamate_1 | vehicle_id: [CENSORED],
teslamate_1 | vin: "[CENSORED]",
teslamate_1 | tokens: [],
teslamate_1 | state: "unknown",
teslamate_1 | option_codes: [],
teslamate_1 | in_service: false,
teslamate_1 | display_name: "Ninja",
teslamate_1 | color: nil,
teslamate_1 | calendar_enabled: nil,
teslamate_1 | backseat_token: nil,
teslamate_1 | backseat_token_updated_at: nil,
teslamate_1 | api_version: nil,
teslamate_1 | charge_state: nil,
teslamate_1 | climate_state: nil,
teslamate_1 | drive_state: nil,
teslamate_1 | gui_settings: nil,
teslamate_1 | vehicle_config: nil,
teslamate_1 | vehicle_state: nil
teslamate_1 | }
teslamate_1 | ]
teslamate_1 | 2023-11-20 01:01:59.456 [info] Starting logger for 'Ninja'
teslamate_1 | 2023-11-20 01:01:59.533 car_id=1 [error] Error / not_signed_in
teslamate_1 | 2023-11-20 01:01:59.539 [info] MQTT connection has been established
teslamate_1 | 2023-11-20 01:02:02.436 [info] tzdata release in place is from a file last modified Fri, 22 Oct 2021 02:20:47 GMT. Release file on server was last modified Tue, 28 Mar 2023 20:25:39 GMT.
teslamate_1 | 2023-11-20 01:02:07.177 [info] Tzdata has updated the release from 2021e to 2023c
teslamate_1 | 2023-11-20 01:02:58.412 [notice] :alarm_handler: {:set, {TeslaMate.Vehicles.Vehicle_1_api_error, :fuse_blown}}
teslamate_1 | 2023-11-20 01:05:15.714 [error] Postgrex.Protocol (#PID<0.2422.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.714 [error] Postgrex.Protocol (#PID<0.2432.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.714 [error] Postgrex.Protocol (#PID<0.2429.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.715 [error] Postgrex.Protocol (#PID<0.2425.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.717 [error] Postgrex.Protocol (#PID<0.2428.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.716 [error] Postgrex.Protocol (#PID<0.2430.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.715 [error] Postgrex.Protocol (#PID<0.2427.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.717 [error] Postgrex.Protocol (#PID<0.2431.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.716 [error] Postgrex.Protocol (#PID<0.2421.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:16.716 [error] Postgrex.Protocol (#PID<0.2426.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
teslamate_1 | 2023-11-20 01:05:17.205 [error] Postgrex.Protocol (#PID<0.2428.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.213 [error] Postgrex.Protocol (#PID<0.2421.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.215 [error] Postgrex.Protocol (#PID<0.2426.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.217 [error] Postgrex.Protocol (#PID<0.2430.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.222 [error] Postgrex.Protocol (#PID<0.2431.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.229 [error] Postgrex.Protocol (#PID<0.2427.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.233 [error] Postgrex.Protocol (#PID<0.2429.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.244 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.252 [error] Postgrex.Protocol (#PID<0.2422.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:17.254 [error] Postgrex.Protocol (#PID<0.2425.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:18.649 [error] Postgrex.Protocol (#PID<0.2426.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
teslamate_1 | 2023-11-20 01:05:18.929 [error] Postgrex.Protocol (#PID<0.2427.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.094 [error] Postgrex.Protocol (#PID<0.2431.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.245 [error] Postgrex.Protocol (#PID<0.2425.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.476 [error] Postgrex.Protocol (#PID<0.2429.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.526 [error] Postgrex.Protocol (#PID<0.2422.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.530 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.621 [error] Postgrex.Protocol (#PID<0.2428.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:19.728 [error] Postgrex.Protocol (#PID<0.2430.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:20.227 [error] Postgrex.Protocol (#PID<0.2421.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:21.189 [error] Postgrex.Protocol (#PID<0.2426.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:22.227 [error] Postgrex.Protocol (#PID<0.2422.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:22.355 [error] Postgrex.Protocol (#PID<0.2425.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:22.631 [error] Postgrex.Protocol (#PID<0.2431.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:23.036 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:23.552 [error] Postgrex.Protocol (#PID<0.2427.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:25.458 [error] Postgrex.Protocol (#PID<0.2429.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): non-existing domain - :nxdomain
teslamate_1 | 2023-11-20 01:05:26.826 [error] Postgrex.Protocol (#PID<0.2421.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:26.841 [error] Postgrex.Protocol (#PID<0.2426.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:27.611 [error] Postgrex.Protocol (#PID<0.2428.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:27.827 [error] Postgrex.Protocol (#PID<0.2432.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:28.698 [error] Postgrex.Protocol (#PID<0.2430.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:28.857 [error] Postgrex.Protocol (#PID<0.2427.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:29.074 [error] Postgrex.Protocol (#PID<0.2422.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
teslamate_1 | 2023-11-20 01:05:29.401 [error] Postgrex.Protocol (#PID<0.2425.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused

 

[init6]

@init6

Spoiler: log

pi@raspberrypi:~ $ docker-compose logs teslamate
Attaching to pi_teslamate_1
teslamate_1 | 2023-11-20 01:01:55.253 [info] Migrations already up
teslamate_1 | 2023-11-20 01:01:58.706 [info] System Info: Erlang/OTP 26 (emu)
teslamate_1 | 2023-11-20 01:01:58.707 [info] Version: 1.27.4
teslamate_1 | 2023-11-20 01:01:58.711 [warning]
teslamate_1 | ------------------------------------------------------------------------------
teslamate_1 | No ENCRYPTION_KEY was found to encrypt and securely store your API tokens.
teslamate_1 |
teslamate_1 | Therefore, the following randomly generated key will be used instead for this
teslamate_1 | session:
teslamate_1 |
teslamate_1 |
teslamate_1 | [CENSORED]
teslamate_1 |
teslamate_1 |
teslamate_1 | Create an environment variable named "ENCRYPTION_KEY" with the value set to
teslamate_1 | the key above (or choose your own) and pass it to the application from now on.
teslamate_1 |
teslamate_1 | OTHERWISE, A LOGIN WITH YOUR API TOKENS WILL BE REQUIRED AFTER EVERY RESTART!
teslamate_1 | ------------------------------------------------------------------------------
teslamate_1 |

Spoiler: log

Fix that for starters. Instructions above.

What do your database logs look like?

 

[RVTim]

As long as you can ssh or run the docker-compose commands then you'll be fine.
Just note there is a typo in the official doc for closing drives. There's a spurious ! between Teslamate.Repo.get and the opening bracket preceding Teslamate.Log.Drive.xxx

I ran it and took out the "!" but got the error "no configuration file provided: not found".

Here are 2 commands I ran. The first one I just ran "ls" hoping it would list my docker sessions running but instead it just listed the config file.


me@NAS~$ sudo docker-compose ls
Password:
NAME STATUS CONFIG FILES
docker running(4) docker-compose.yml


This one is where I tried to close the drive.

me@NAS:~$ sudo docker-compose exec teslamate bin/teslamate rpc \
> "TeslaMate.Repo.get(TeslaMate.Log.Drive, 1208) |> TeslaMate.Log.close_drive()"
no configuration file provided: not found

Really sorry to have to ask for tips. I'm sure this stuff is simpler than I think. I just never had to really play with docker. Everything I've ever installed
that runs on it I've been able to follow a guide for. This is a good chance for me to get into the weeds a little and understand more when I'm done.