close multiple drives at once

[totoantibes]

I have to regularly (and i mean daily) go on teslamate and look for missing drives in grafana, look at the missing ID number from the overlay url and then run the "close drive script" manually for the missing ID. is there by any chance a small script that could run a "for loop" to clean it up? i could cron the script and have a clean up state of trips.... It should not be that difficult but i am not sure what is the query needed to look for the missing trips...

this is what i run manually (as per the docs: https://docs.teslamate.org/docs/maintenance/manually_fixing_data
sudo docker-compose exec teslamate bin/teslamate rpc "TeslaMate.Repo.get!(TeslaMate.Log.Drive,1125) |> TeslaMate.Log.close_drive()"

[init6-git]

It's been a long time since I wrote a shell script, but just knocked this one up:

#!/bin/bash
echo "Looking for unclosed drives"
records=$(cat ./unclosed-drives.sql | docker exec -i CONTAINER_NAME psql -t --pset="footer=off" -U teslamate -d teslamate)

echo "Closing drives"

for x in $records; 

do docker-compose exec teslamate bin/teslamate rpc "TeslaMate.Repo.get(TeslaMate.Log.Drive, $x) |> TeslaMate.Log.close_drive()" ; 
        echo "drive $x closed"
done;

echo "All closed"

Requires a file called unclosed-drives.sql which contains:
select id from drives where end_date is null order by start_date;

I'm sure these should be put into one script, but I've done enough today :)

[chinedu40]

@totoantibes Thank you for mentioning this fix to the issue, it had been causing problems for me for over 2 years and changing the database timeout has fixed the issue for me.

@adriankumpf perhaps a change to the default database timeout should be considered and/or make this something you put in the wiki as a fix?

[aiden-cat]

For those curious, this can dump the outputs into the necessary file:

docker exec pi_database_1 psql -d teslamate -U teslamate -c "select id from drives where end_date is null order by start_date;" -e > unclosed-drives.sql

[dmachadol]

I created this script and it works perfectly:

• Searches for unclosed charges and drives records that are 2 days old or more (This prevents active charge/drive from closing)

• You can add it to the system cron or run it manually at your convenience.

#!/bin/bash
echo "Seeking for unclosed drives & charges..."

sql="select id from charging_processes where end_date is null and start_date <  now() + interval '-2 days' order by start_date;"
data=$(docker exec teslamate_database_1 bash -c "psql -d teslamate -U teslamate -t -c \"${sql}\"")
data=($data)

if [ "${data}" != "" ]; then
  for m in "${data[@]}"; do
    echo "Closing charge num: ${m}..."
    sudo docker exec  teslamate_teslamate_1 /opt/app/bin/teslamate rpc "TeslaMate.Repo.get(TeslaMate.Log.ChargingProcess,${m}) |> TeslaMate.Log.complete_charging_process()";
  done
fi

sql="select id from drives where end_date is null and start_date <  now() + interval '-2 days' order by start_date;"
data=$(docker exec teslamate_database_1 bash -c "psql -d teslamate -U teslamate -t -c \"${sql}\"")
data=($data)

if [ "${data}" != "" ]; then
  for m in "${data[@]}"; do
    echo "Closing drive num: ${m}..."
    sudo docker exec  teslamate_teslamate_1 /opt/app/bin/teslamate rpc "TeslaMate.Repo.get(TeslaMate.Log.Drive,${m}) |> TeslaMate.Log.close_drive()";
  done
fi


echo "Done."

[cwanja]

@dmachadol this worked perfectly with a minor modification. I had to update teslamate_database_1 and teslamate_teslamate_1 to teslamate-database-1 and teslamate-teslamate-1 respectively. Going to add this script to our documentation.

Just closed over 270 drives thanks to @jheredianet dashboard. PS Juan, can you make a PR to add the incomplete data dashboard? Alternative could be to add a panel to both Drive and Charge Stats with a count of incomplete objects. We can let a discussion in the PR take place. Tag me in the PR so I can track it please 😄 thanks!

[cwanja]

Docs update in PR #3877