Is there an existing issue for this?
What happened?
charge_energy_added is published via MQTT, but it would be useful to also publish charge_energy_used so that this data could be passed on to integrate with energy monitoring systems as in the homeassistant energy dashboard. I believe charge_energy_used would just need to be added to teslamate/mqtt/pubsub/vehicle_subscriber.ex
Expected Behavior
Report both the energy added to the battery and the energy consumed for that addition.
Can the issue reliably be reproduced?
Yes
Steps To Reproduce the issue
Enhancement
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker (https://docs.teslamate.org/docs/installation/docker/)
Version
v2.1.1
PostgreSQL version
v17.6-1
Are you running latest major supported PostgreSQL version?
Are you using a reverse Proxy for TeslaMate?
Yes (specify in next field)
Details about your reverse Proxy if applicable
N/A
Is there an existing issue for this?
What happened?
charge_energy_added is published via MQTT, but it would be useful to also publish charge_energy_used so that this data could be passed on to integrate with energy monitoring systems as in the homeassistant energy dashboard. I believe charge_energy_used would just need to be added to teslamate/mqtt/pubsub/vehicle_subscriber.ex
Expected Behavior
Report both the energy added to the battery and the energy consumed for that addition.
Can the issue reliably be reproduced?
Yes
Steps To Reproduce the issue
Enhancement
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker (https://docs.teslamate.org/docs/installation/docker/)
Version
v2.1.1
PostgreSQL version
v17.6-1
Are you running latest major supported PostgreSQL version?
Are you using a reverse Proxy for TeslaMate?
Yes (specify in next field)
Details about your reverse Proxy if applicable
N/A