fix: incorrect 0 values from charge_energy_used charges queries (#366)

This commit is contained in:
Lukáš Stankovič
2025-09-22 16:28:12 +02:00
committed by GitHub
parent 1c6906c077
commit 36f2fae429
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -106,7 +106,7 @@ func TeslaMateAPICarsChargesV1(c *gin.Context) {
end_date,
COALESCE(geofence.name, CONCAT_WS(', ', COALESCE(address.name, nullif(CONCAT_WS(' ', address.road, address.house_number), '')), address.city)) AS address,
COALESCE(charge_energy_added, 0) AS charge_energy_added,
COALESCE(charge_energy_used, 0) AS charge_energy_used,
COALESCE(GREATEST(charge_energy_used, charge_energy_added), 0) AS charge_energy_used,
COALESCE(cost, 0) AS cost,
start_ideal_range_km AS start_ideal_range,
end_ideal_range_km AS end_ideal_range,
+1 -1
View File
@@ -125,7 +125,7 @@ func TeslaMateAPICarsChargesDetailsV1(c *gin.Context) {
end_date,
COALESCE(geofence.name, CONCAT_WS(', ', COALESCE(address.name, nullif(CONCAT_WS(' ', address.road, address.house_number), '')), address.city)) AS address,
COALESCE(charging_processes.charge_energy_added, 0) AS charge_energy_added,
COALESCE(charge_energy_used, 0) AS charge_energy_used,
COALESCE(GREATEST(charge_energy_used, charging_processes.charge_energy_added), 0) AS charge_energy_used,
COALESCE(cost, 0) AS cost,
start_ideal_range_km AS start_ideal_range,
end_ideal_range_km AS end_ideal_range,