KWh in EURO but with

so i verified the KWh of the shellyplug and the output of that integral-riemann helper…
defenitvly THAT helper produces wrong values!

I made another Test-Intergral Helper:
Input is Load_power of house (~2000W)


Have a look at the timestamps!
Here is it ok.

But this here stucks at 0.29KWh but the raum_1_import_power sensor gives 1000W
Screenshot (142)

That is wrong.

Diagramm:
can you create a Screenshot from this „helper“ (0 or 1)
and for the same time the „Raum 1 Import energy“
and also the power sensor you use for this (Raum 1 Import power)

Your Last screenshot from „Raum 1 Import energy“
Looks like your trigger for starting is not permanently set to the value = 1

I have tested this again especially for you
It looks plausible to me for the time being
Helper is a numeric one for me, 0 or 1

i just saw that the cost still counts even importing power is off.
Reason was the change from float to boolen…

This is right:

{% if is_state('binary_sensor.importing_power', 'on') %}
{{ states('sensor.shellyplusplugs_c82e18086ea4_switch_0_power')|float(0) |round(0)}}
{% else %}
0
{% endif %}

Could it be that the integral takes some hours to measure correctly?
Now it shows 0.99€ instead of 0.29€ but over night the heaters were off.

Nope

I would just start from scratch

With new sensor names (you can leave the old ones for now)

I would do the € converter later, that shouldn’t be a problem.

Start with the power sensor and diagram, if it fits then the energy sensor, if plausible then the € sensor

€ Sensor as Template Helper
my Energy Sensor is in Wh, so i need also /1000

{{ (states('sensor.wolfram_energy')|float(0) *0.455 /1000) |round(2) }}

Overview to validate Data:

it seems to work now right! I dont know why the KWh stuck yesterday evening…
Screenshot (144)

i also put some utlitymeters for daily,weekly,monthly and yearly on.
So we have a overview of the power and cost for each room.

Is there a possibility to set the values persistent to 0 ?
If i use set state it will be overridenn after a while…

BTW: i want to thank you very much for your help!!!)

This is how my Dashboard on a Tablet looks like:

The easiest way is to delete the sensor and delete the statistics. Then create the sensor again.

If this happens frequently, I would also add an “offset” sensor (numerical).

Helfe gerne :grinning: Gruß