Closed sepahewe closed 3 years ago
Not sure I understand the value of this? If you want to display the cost in your UI, why not use the tibber sensor then? This value comes from the easee cloud, and it is a configuration value that I believe is only used for calculating a price in the charging reports that the cloud can generate. So changing this value will have no other effect than changing the price when the report is generated. It will not keep track of the cost retroactively I think...?
If that’s the case I agree there’s no value. I’ll close the issue.
First, thank you for a very solid integration, way above the average HACS integration.
Having "Cost per kwh" writable would allow me to feed this data from another source, such as tibber:sensor.electricityprice*, getting a more accurate representation of the current cost.