New in 1.30 with "-bash: !: event not found" when trying to Manually fixing data

[GtHbbrr]

I noticed the list of incomplete drives:
From here you can check if you have incomplete data of Drives (drives without ending date) If so, you may follow the official guide by Manually fixing data

On following the instruction for manually fixing data with replacing the 9999 for severakl of the incomplete drives I get this response:
docker compose exec teslamate bin/teslamate rpc \ "TeslaMate.Repo.get!(TeslaMate.Log.Drive, 5029) |> TeslaMate.Log.close_drive()"

-bash: !: event not found

[djpalmis]

#2524 still this issue claims victims

[GtHbbrr]

Is there more information available on this command to manually fix drives/charges? I can not find any feed back in the logs

[GtHbbrr]

Closing automatically is always ok for drives that started say more than 1 day ago. No single drive in any ev will last longer than 24 hours

[GtHbbrr]

Is it not the intention of the teslamate settings page to ask the user questions on startup?

[GtHbbrr]

On investigating further following the previous issue #2524 I managed to resolve using the "close multiple drives at once"-script in issue #2364. This script as proposed by init6-git and further developed by aiden-cat, dmachadol and cwanja.

Also cwanja did propose a pull request in PR #3877 but this was denied citing:

• The docu is not idemponent
• the script use sudo docker ...
• the bash style is not system neutral
• mentioning a single person for credit

What is idemponent?

[GtHbbrr]

I suggest adding a reference to issue #2364 in the documentation for Manually fixing data

[JakobLichterfeld]

Closing automatically is always ok for drives that started say more than 1 day ago. No single drive in any ev will last longer than 24 hours

That's technically not correct.

[JakobLichterfeld]

What is idemponent?

"In computing, an idempotent operation is one that has no additional effect if it is called more than once with the same input parameters."

[JakobLichterfeld]

I managed to resolve using the "close multiple drives at once"-script in issue

Glad you solved your issue. It proves that you do have an issue with your shell and your event name as provided as answer multiple times before.