[Feature Request] More detailed Geo-Fence cost entry

[jxt1009]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

There's at least two situations that I've encountered where the Geo Fencing cost entry is missing some details that impact cost calculations.

1. Flat fees
   
   

2. Station Time Rate (aka "Parking Fees")
   

Expected Behavior

I should be able to provide a detailed breakdown of a stations' costs and use those values to get an accurate price across different visits.
Note: I'm interested in contributing to the project, I might open a PR if I can get things set up

Steps To Reproduce

No response

Relevant log output

.

Screenshots

Additional data

No response

Type of installation

Docker

Version

v1.32.0

[JakobLichterfeld]

Thanks for your idea.

Indeed, there are several charging stations with different pricing structures, such as blocking fee, unlocking fee, etc. To be 100% accurate, I only use the geo-fence price presets for free stations and enter all other values manually, atm.

Note: I'm interested in contributing to the project, I might open a PR if I can get things set up

Every PR is highly welcome!

We do have some basic instructions here: https://docs.teslamate.org/docs/development/
If you do use nix, setting up the dev env is a single command.

[AkshayRao27]

Another (possibly related) extension for your idea -
Out here in Vienna, every charging station has a day tariff & a night tariff:

It's also very common to have different per-minute prices depending on the charging power:

In fact, this is also the case with almost all Superchargers in Austria:

For the past two years, I've been entering the cost for every charging session manually because (AFAIK) there's no way for me to set this sort of calculation up in Teslamate. I have no idea if it's possible (or realistic) to implement this level of logic into Teslamate.

[tpd-opitz]

Here ist one more situation to consider: dynamic power rates (Like Tibber, Tado or alike)

My preferred solution would be to have the current price being pushed by an external application (homeassistant, openWB, ...) when the next price activates to a MQTT topic shown in the geo location view assigned to the new entry dynamic in the costs dropdown menu so that Teslamate can pick the current price from it:

This way the external app ist responsible for getting the price info and updating the value in Teslamate. Teslamate would not need to distinguish between "real" dynamic cost providers and rule based pricing...

maybe Telsamate can calculate an average to be used if the last update is older than 24h.