Correcting cost at a geofence

[srivaths]

The cost of charging at one of my geofences had not been set. When I set it I was asked if I wanted to retroactively set the cost of all charges at that location (several hundred instances). I agreed since that is what I wanted.

It was only then that I noticed that I had a typo in the cost I had specified. However when you change the charging cost at a geofence that previously had a cost value you are not prompted for retroactive changes.

Is there a way to easily apply a cost change retroactively?

(I am aware that I can go into the Charges dashboard and apply it for each charging event. However there are about 500 instances and this would be very time consuming).

[cwanja]

Could you delete the geofence, set it back up, then reset the charging cost?

[srivaths]

@cwanja Paydirt!

0. Backup the data
1. update charging_processes set cost = NULL where geofence_id = '1'
2. Pull up Geofence and set the correct cost/kWh. Press Save.
3. You are prompted asking whether the cost should be applied retroactively. Accept
4. Pull up Charges dashboard.
5. Yay!!

[cwanja]

Awesome, glad it worked!

[hadfiiw]

Sorry to bring this topic back up but does anybody have the steps to connect to the proper Docker container? For us Docker-impaired individuals. :-P

[cwanja]

@hadfiiw - you should be able to use docker-compose exec database psql teslamate teslamate. The password (teslamate) might be different and database could be db depending on your YML file.

See more here https://docs.teslamate.org/docs/maintenance/manually_fixing_data

[hadfiiw]

Thanks @cwanja that worked perfectly!

For reference, here is what I ran...

sudo docker-compose exec database psql teslamate teslamate

which changed to a "teslamate=#" prompt. Then (using geofence 4 per the geofence's URL)...

teslamate=# select from charging_processes where geofence_id = '4';
--
(88 rows)

teslamate=# update charging_processes set cost = NULL where geofence_id = '4';
UPDATE 88
teslamate=# 

[scottrbaxter]

teslamate=# select from charging_processes where geofence_id = '4';
--
(88 rows)

teslamate=# update charging_processes set cost = NULL where geofence_id = '4';
UPDATE 88
teslamate=#

this worked perfectly for me to retroactively set charging costs - i initially entered a decimal point incorrectly. thanks!

curious, year over year we've had a change in electricity pricing. i'd like to go back and set all records for 2023 and 2024 to be the value charged per kwh on our utility bill. since we can't set the grafana Cost/kWh value directly, could someone point me to the best way to set this value for earlier dates in the postres db?

[cwanja]

'Ol ChatGPT to the rescue.

SELECT *
FROM your_table
WHERE your_date_column BETWEEN '2023-01-01' AND CURRENT_DATE;