I have read many of the posts here around the Energy Dashboard and the Utility Meter but have not seen my issue raised. For me the Utility Meter is reporting data a factor of 10 too high.
I am confident of the power (W) figure from my current sensor as shown in this chart. It uses an update interval of 60 sec from platform: atm90e32
It shows that my energy consumption (area under the curve) should be under 600 Wh for any one hour running time. Instead the Utility meter gives a number that is too high by a factor of 10.
Here is my config.yaml
utility_meter:
liv_aircond_energy:
source: sensor.esp32_6channel_6c_ct2_watts_2
cycle: hourly
and here is my customize.yaml
sensor.liv_aircond_energy:
unit_of_measurement: Wh
friendly_name: LivingRm AirCond Energy
device_class: energy
state_class: total_increasing
last_reset: '1970-01-01T00:00:00+00:00'
Is there a Utility Meter parameter for setting the integration interval to account for the steep spike when the air cond starts?
The other concern is that the Energy Dashboard reports kWh rather than Wh. Is this a bug that it ignores the entity config or have I missed something?
What is the best way around these issues? Should I use the Riemann Integration instead? Use a template sensor to apply a divide by 10 multiplier?