Open bs-github opened 1 year ago
Presumably the reason is that the was ESP restarted during a charging session.
As this is only an assumption, the reproducer would be to restart the ESP deliberately during a charging session and investigate.
The tracked values should not be harmed by a restart.
"ac011k_hardware/meter": { "energy_rel": 143.998, "energy_rel_raw": 10.263, "energy_rel_delta": 133.735, "energy_abs": 206.825, "energy_abs_raw": 10.263, "energy_abs_delta": 196.562 }, "charge_tracker/last_charges": [ { "timestamp_minutes": 27935256, "charge_duration": 6301, "user_id": 0, "energy_charged": 9.286999 }, { "timestamp_minutes": 27936748, "charge_duration": 65614, "user_id": 0, "energy_charged": 6.735001 }, { "timestamp_minutes": 27941344, "charge_duration": 51021, "user_id": 0, "energy_charged": 64.466 }, { "timestamp_minutes": 27951021, "charge_duration": 22972, "user_id": 0, "energy_charged": 33.76999 }, { "timestamp_minutes": 27952544, "charge_duration": 0, "user_id": 0, "energy_charged": -186.907 } ], "charge_tracker/current_charge": { "user_id": 0, "meter_start": 204.064, "evse_uptime_start": 4988, "timestamp_minutes": 27952740, "authorization_type": 0, "authorization_info": null }, "charge_tracker/state": { "tracked_charges": 5, "first_charge_timestamp": 27935256 },
The MQTT settings where altered just before the wrongfully tracked charge session. That leads to the assumption that the ESP restarted (as all config changes lead to a suggested restart in the UI).
I have a similar problem: I need to restart my ESP a lot because of #55 and this leads to negative charges:
There is a negative value for the charged energy tracked
Presumably the reason is that the was ESP restarted during a charging session.
To Reproduce
As this is only an assumption, the reproducer would be to restart the ESP deliberately during a charging session and investigate.
Expected behaviour
The tracked values should not be harmed by a restart.
Debug Log
Versions:
Additional context
The MQTT settings where altered just before the wrongfully tracked charge session. That leads to the assumption that the ESP restarted (as all config changes lead to a suggested restart in the UI).