You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When entering a cost per kWh in the charge-cost page, I need to use 4 decimal places as my supplier charges in fractions of cents. For example, if I enter 0.1446, it responds with: Please enter a valid value. The two nearest valid values are 0.14 and 0.15.
Expected behavior
I should be able to precisely enter my charge cost rates.
How to reproduce it (as minimally and precisely as possible):
Go to a charge session
Click on "cost" to set the cost
Set the drop-down to per-kwh and enter the cost to more than 2 decimal places
See error
Relevant entries from the logs
Screenshots
Environment
TeslaMate version: 1.21.6
Type of installation: Docker
OS TeslaMate is installed on: Ubuntu
User OS & Browser: Ubuntu / Chrome
Others:
The text was updated successfully, but these errors were encountered:
Ok I see where the problem is - you can set this to 4 places on the geofence page, but not when you click through from the charges cost link in the Grafana dashboard.
When responding to #4454, I remembered that this ticket existed and wanted to ask if this is something that can be reconsidered.
Some charging providers have minute-based prices that have three decimals. These prices are valid throughout Austria, and sometimes, even in other countries. An example of such a provider is WienEnergie, the Energy Provider for the city of Vienna:
Describe the bug
When entering a cost per kWh in the charge-cost page, I need to use 4 decimal places as my supplier charges in fractions of cents. For example, if I enter 0.1446, it responds with:
Please enter a valid value. The two nearest valid values are 0.14 and 0.15.
Expected behavior
I should be able to precisely enter my charge cost rates.
How to reproduce it (as minimally and precisely as possible):
Relevant entries from the logs
Screenshots

Environment
The text was updated successfully, but these errors were encountered: