You can use history stats to get the total “on” time of the plug from and to specific dates and then use a template sensor to multiply the value of history state sensor with the power consumption of your device
That’s what I’m trying to do right now.
Do you know how I can make “current year” and “current month” periods?! Current week is described, but I’m really bad with this templating stuff…
This should theoretically give me the current month, right?!
start: '{{ as_timestamp( now().replace(hour=0).replace(minute=0).replace(second=0) ) - now().weekday() * 86400 - now().week() * 254800 }}'
end: '{{ now() }}'
…assuming now().week() * 254800 is correct for “week of the month” … which it appears to not be 
EDIT: I believe I have found the solution… it’s
start: '{{ now().replace(day=1).replace(hour=0).replace(minute=0).replace(second=0) }}'
end: '{{ now() }}'
Interestingly, the history stats sensor does work, but only seems to go back like 2 days (estimated by the values it provides)
Right now the current day shows 2.03 (which is definitely correct) but current month and current year both show 5.09 - that’s incorrect, because that heater runs aproximately 2-3h a day right now 
EDIT: don’t use this - go down to the solution
Ok, for anyone also looking for a solution, I solved it like this now 
You need a History Stat Sensor to determine the runtime of a device (switch-on-time):
- platform: history_stats
name: 'bedroom heater runtime today'
entity_id: switch.osram_plug_01
state: 'on'
type: time
start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
end: '{{ now() }}'
and also a Template Sensor to calculate the theoretical power comsumption:
- platform: template
sensors:
bedroom_heater_power_consumption_today:
friendly_name: "Bedroom Heater Power Comsumption Today"
unit_of_measurement: 'kWh'
value_template: '{{ (states("sensor.bedroom_heater_runtime_today")|float * 1.50 )| round(2) }}'
# replace with the kW of your device here ^^^^^^
Honestly, I have no Idea what the |float stands for, but it won’t work without it
| round(2) is the decimal places you want the value to be rounded to
Two questions remain:
- for now only the last two days are recorded (I want to calculate the yearly power consumption though) - I’ll have to wait if this is only the case because the sensor is new and doesn’t have more data to work with for now…
- what happens when the plug is on for more than 24h in sum - will it still count in hours (25-9999999) or will it toggle to days, weeks, months, years, decades, etc
I think the problem with this solution is that you’ll only get as many days as you have in your database. I think my last comment is a better way.
I was actually pretty sure this is what I did
But now I see what you mean… and true that would make a big difference.
But how would I get a current_power reading?!
Say the device uses 1.5 kw. Set up a template sensor that had the value 1.5 kw when the switch is on and 0kw when the switch is off. I am in my phone posting this so can’t play about and produce the template right now, but it should be simple enough.
Then integrate that sensor using the power integration sensor.
1 Like
well that would be a LOT more straight forward and simple … if I get the template right 
I’ll give it a try
I got It to work! 
For the fake power meter I use:
- platform: template
sensors:
bedroom_heater_power:
friendly_name: "Bedroom Heater Power"
unit_of_measurement: 'kW'
value_template: >
{% if is_state('switch.your_power_plug', 'on') %}
1.50 # <- replace with the kW of your device
{% else %}
0
{% endif %}
And this for the integration sensor:
- platform: integration
source: sensor.bedroom_heater_power
name: Bedroom Heater Power Consumption
round: 2
Thanks for the solution @nickrout !
3 Likes
For some weird reason the integration sensor also counts when the plug is off…
The template sensor bedroom_heater_power does give out the right value - when the plug is on it reports 1.50, if it’s off, 0.
But EVERY TIME I toggle the plug, the intergation sensor adds power as if the plug was on all the time.
so:
plug on for 10min results in +0,25kWh (correct)
BUT
plug off for 10min also results in +0,25kWh on the integration sensor…
I have linked the integration sensor with a Utility Meter like this:
bedroom_heater_utility_meter:
source: sensor.bedroom_heater_power_consumption
cycle: daily
The readings here are exactly the same (wrong) as on the integration sensor
What could cause this!?
I already thought about making the sensor “update” the number every 5sec or so - maybe that’s what’s wrong (because an acutal power meter would do that, right?!)
But I can’t figure out how
I guess the problem must be here somewhere
- platform: template
sensors:
bedroom_heater_power:
friendly_name: "Bedroom Heater Power"
unit_of_measurement: 'kW'
value_template: >
{% if is_state('switch.your_power_plug', 'on') %}
1.50 # <- replace with the kW of your device
{% else %}
0
{% endif %}
It seems to be completely irrelevant what value I put instead of 0 … the integration sensor always uses the 1.50
Even though the bedroom_heater_power sensor does report the correct value. 0 when off and 1.50 when on. It’s really strange…
The only thing I can think of, is that looking at the code for the integration sensor (here) is that the sensor’s last_updated attribute plays heavily into the calculation, which makes sense for most use cases.
Maybe something about that template sensor isn’t changing the value open enough, or atleast updating the last_updated attribute often enough, for it to correctly get calculated for integration.
The only idea i can think of to test this is to manually call the sensor entity to update every few minutes.
There’s an example automation to call a template sensor to update it’s value in the documentation here (essentially calling the homeassistant.update_entity service on that sensor every 5 minutes with a time pattern).
You can give that a shot and see if it helps any, of i’m just completely off in the woods with what’s causing this issue.
I tried that automation, but it doesn’t seem to do anything. The sensor only updates when I toggle the switch.
- id: 'bedroom heater power refresh '
alias: bedroom_heater_power_refresh
trigger:
- platform: time_pattern
seconds: '/5'
action:
- service: homeassistant.update_entity
entity_id: sensor.bedroom_heater_power
I assume that the obvious stuff like checking that the automation is enabled, and that the last triggered time makes sense is something you did, and it’s just that it didn’t fix the problem.
Maybe it’s something to do with the 0 not being interpreted as a number, but as a string? Not sure why this would happen, since it clearly accepts the 1.5. The only difference is that one has a decimal place in it. It would be too silly to suggest that “0.0” might work instead of just “0”, right?
Yeah - I checked all that.
I also tried to use 0.01 Instead of 0 - this is when I realized, that the second value seems to make no difference…
But I seem to have screwed up somewhere else … now random lights go on when I reload automations or restart HA (actually completely random) … also I can’t seem to make my automations set temperatures on my generic_thermostats any more… I’ll have to look into that 
I restored an older Snapshot and HA seems to work correctly again
But the issue with the power meter remains. Every time I toggle the switch, the intergation sensor adds the kWh for the last period (no matter if the switch was on or off - it always adds “hours*kw”)
Can I change this template sensor
- platform: template
sensors:
bedroom_heater_power:
friendly_name: "Bedroom Heater Power"
unit_of_measurement: 'kW'
value_template: >
{% if is_state('switch.your_power_plug', 'on') %}
1.50 # <- replace with the kW of your device
{% else %}
0
{% endif %}
so it updates the value every 5 seconds, without using an automation?
Alternatively it would probably also work if the value loops between something like 1.49 and 1.51 every few seconds indefinitely, as long as the switch is on … (and 0 and 0.01 when it’s off - not ideal, but as long as it gets the job done)
ok, I believe I have figured out how to do this - my solution is probably incredibly scruffy, but at least it seems to get the job done.
First I made a template sensor that will output the kW of the device (in my case a heater with 1kW rating)
- platform: template
sensors:
sz_h_current_power_draw:
friendly_name: "Schlafzimmer Heizung momentaner Stromverbrauch"
unit_of_measurement: 'kW'
value_template: >
{% if is_state('switch.osram_smartplug_01_switch', 'on') %}
{{ states.input_number.sz_h_on.state }}
{% else %}
{{ (states.input_number.sz_h_off.state)|float / 2 }}
{% endif %}
as you can see I use input numbers:
sz_h_on:
name: sz_h_on
min: 0
max: 3
step: 1
sz_h_off:
name: sz_h_off
min: 0
max: 0.001
step: 0.001
The reason is, that only when the value changes, the following integration sensor
- platform: integration
source: sensor.sz_h_current_power_draw
name: sz_h_power_draw
round: 5
updates. (without that it will allways assume the used energy is the average between on and off - the last two values it knows. so no matter if you turn the switch on or off, it will return the same kWh used)
To prevent this, we need 4 automations:
- id: 'sz heater power refresh_1'
alias: sz_heater_power_refresh_1
trigger:
- platform: state
entity_id: switch.osram_smartplug_01_switch
to: 'on'
action:
- service: automation.turn_off
entity_id: automation.sz_heater_power_refresh_off
- service: automation.turn_on
entity_id: automation.sz_heater_power_refresh_on
- id: 'sz heater power refresh_0'
alias: sz_heater_power_refresh_0
trigger:
- platform: state
entity_id: switch.osram_smartplug_01_switch
to: 'off'
action:
- service: automation.turn_off
entity_id: automation.sz_heater_power_refresh_on
- service: automation.turn_on
entity_id: automation.sz_heater_power_refresh_off
- id: 'sz heater power refresh on '
alias: sz_heater_power_refresh_on
trigger:
- platform: time_pattern
seconds: '/10'
action:
- service: input_number.set_value
data_template:
entity_id: input_number.sz_h_on
value: "0.99"
- delay: 00:00:04
- service: input_number.set_value
data_template:
entity_id: input_number.sz_h_on
value: "1.01"
- id: 'sz heater power refresh off '
alias: sz_heater_power_refresh_off
trigger:
- platform: time_pattern
seconds: '/10'
action:
- service: input_number.set_value
data_template:
entity_id: input_number.sz_h_off
value: "0.001"
- delay: 00:00:04
- service: input_number.set_value
data_template:
entity_id: input_number.sz_h_off
value: "0"
The first two are here to trigger the last two according to the power state of the switch.
The last two automations change the input_numbers that are tied to the power sensor minimally, so that the integration sensor gets regular readings it can work with.
Basically, the automations loop every 5sec between 0.99 and 1.01kW if the device is on (which results in 1kW in average) and between 0 and 0.001kW when it’s off (unfortunately 0.001 is the lowest number the input_number supports, which results in 0.5W as the lowest power consumption (the plug uses 0.1-0.3 when in standby) - as you can see, I divided the sz_heater_power_refresh_off value in the template sensor by 2, which results in 0.25W standby power consumption )
Like I said - it works, but I’m sure there is a much simlper way to do that. Probably a script or something, but I have no idea how to approach that…
It seems that I’ve managed to find a very simple solution - only “downside” is that it works with Node Red.
Basically Node Red calculates the kWh by looking at the duration of the last state (on or off) of a switch, sends this value via MQTT to a sensor in Home Assistant, which gets read by the Utility Meter and added up.
First you need to make a flow like that :
Here’s the flow to copy:
[
{
"id": "82770b78.c61bb8",
"type": "server-state-changed",
"z": "3c74f436.9e051c",
"name": "XYZ ON",
"server": "938bbb0d.d39038",
"version": 1,
"exposeToHomeAssistant": false,
"haConfig": [
{
"property": "name",
"value": ""
},
{
"property": "icon",
"value": ""
}
],
"entityidfilter": "switch.xyz",
"entityidfiltertype": "exact",
"outputinitially": false,
"state_type": "str",
"haltifstate": "",
"halt_if_type": "str",
"halt_if_compare": "is",
"outputs": 1,
"output_only_on_state_change": true,
"x": 100,
"y": 1500,
"wires": [
[
"451731a4.89d82"
]
]
},
{
"id": "2ef96586.96ce9a",
"type": "interval-length",
"z": "3c74f436.9e051c",
"format": "mills",
"bytopic": false,
"minimum": "",
"maximum": "",
"window": "",
"timeout": false,
"msgTimeout": "",
"minimumunit": "msecs",
"maximumunit": "msecs",
"windowunit": "msecs",
"msgTimeoutUnit": "msecs",
"reset": false,
"startup": false,
"msgField": "payload",
"timestampField": "timestamp",
"repeatTimeout": false,
"name": "",
"x": 480,
"y": 1500,
"wires": [
[
"3b31d530.44a95a",
"afc1d974.630488"
],
[]
]
},
{
"id": "3b31d530.44a95a",
"type": "api-current-state",
"z": "3c74f436.9e051c",
"name": "OFF",
"server": "938bbb0d.d39038",
"version": 1,
"outputs": 2,
"halt_if": "off",
"halt_if_type": "str",
"halt_if_compare": "is",
"override_topic": false,
"entity_id": "switch.xyz",
"state_type": "str",
"state_location": "",
"override_payload": "none",
"entity_location": "",
"override_data": "none",
"blockInputOverrides": false,
"x": 670,
"y": 1440,
"wires": [
[
"caf894a8.d73fb8",
"bbd5ce79.d3dfe"
],
[]
]
},
{
"id": "afc1d974.630488",
"type": "api-current-state",
"z": "3c74f436.9e051c",
"name": "ON",
"server": "938bbb0d.d39038",
"version": 1,
"outputs": 2,
"halt_if": "on",
"halt_if_type": "str",
"halt_if_compare": "is",
"override_topic": false,
"entity_id": "switch.xyz",
"state_type": "str",
"state_location": "",
"override_payload": "none",
"entity_location": "",
"override_data": "none",
"blockInputOverrides": false,
"x": 670,
"y": 1560,
"wires": [
[
"ce50d3fe.fae1c",
"579fecb9.d13fd4"
],
[]
]
},
{
"id": "451731a4.89d82",
"type": "switch",
"z": "3c74f436.9e051c",
"name": "",
"property": "payload",
"propertyType": "msg",
"rules": [
{
"t": "eq",
"v": "on",
"vt": "str"
},
{
"t": "eq",
"v": "off",
"vt": "str"
},
{
"t": "eq",
"v": "unavailable",
"vt": "str"
}
],
"checkall": "true",
"repair": false,
"outputs": 3,
"x": 310,
"y": 1500,
"wires": [
[
"2ef96586.96ce9a"
],
[
"2ef96586.96ce9a"
],
[]
]
},
{
"id": "d3430473.57f0a8",
"type": "function",
"z": "3c74f436.9e051c",
"name": "kWh",
"func": "\nmsg.payload = (msg.payload[1] * 0.00000027777778) * (msg.payload[0] / 1000);\n\nreturn msg;\n",
"outputs": 1,
"noerr": 0,
"initialize": "",
"finalize": "",
"x": 1430,
"y": 1440,
"wires": [
[
"683e95e4.7b8e0c",
"fe4ed983.e12f48"
]
]
},
{
"id": "4deac3b8.2f902c",
"type": "join",
"z": "3c74f436.9e051c",
"name": "",
"mode": "custom",
"build": "array",
"property": "payload",
"propertyType": "msg",
"key": "topic",
"joiner": "\\n",
"joinerType": "str",
"accumulate": false,
"timeout": "",
"count": "2",
"reduceRight": false,
"reduceExp": "",
"reduceInit": "",
"reduceInitType": "",
"reduceFixup": "",
"x": 1270,
"y": 1440,
"wires": [
[
"d3430473.57f0a8"
]
]
},
{
"id": "caf894a8.d73fb8",
"type": "api-current-state",
"z": "3c74f436.9e051c",
"name": "XYZ Watt",
"server": "938bbb0d.d39038",
"version": 1,
"outputs": 1,
"halt_if": "",
"halt_if_type": "str",
"halt_if_compare": "is",
"override_topic": false,
"entity_id": "input_number.xyz_watt",
"state_type": "num",
"state_location": "payload",
"override_payload": "msg",
"entity_location": "data",
"override_data": "msg",
"blockInputOverrides": false,
"x": 1060,
"y": 1400,
"wires": [
[
"4deac3b8.2f902c"
]
]
},
{
"id": "bbd5ce79.d3dfe",
"type": "delay",
"z": "3c74f436.9e051c",
"name": "",
"pauseType": "delay",
"timeout": "5",
"timeoutUnits": "milliseconds",
"rate": "1",
"nbRateUnits": "1",
"rateUnits": "second",
"randomFirst": "1",
"randomLast": "5",
"randomUnits": "seconds",
"drop": false,
"x": 1050,
"y": 1460,
"wires": [
[
"4deac3b8.2f902c"
]
]
},
{
"id": "f46f070a.905bb8",
"type": "function",
"z": "3c74f436.9e051c",
"name": "kWh",
"func": "\nmsg.payload = (msg.payload[1] * 0.00000027777778) * (msg.payload[0] / 1000);\n\nreturn msg;\n",
"outputs": 1,
"noerr": 0,
"initialize": "",
"finalize": "",
"x": 1430,
"y": 1560,
"wires": [
[
"683e95e4.7b8e0c",
"82898f2c.ddf6d"
]
]
},
{
"id": "c55b5515.fe1ba8",
"type": "join",
"z": "3c74f436.9e051c",
"name": "",
"mode": "custom",
"build": "array",
"property": "payload",
"propertyType": "msg",
"key": "topic",
"joiner": "\\n",
"joinerType": "str",
"accumulate": false,
"timeout": "",
"count": "2",
"reduceRight": false,
"reduceExp": "",
"reduceInit": "",
"reduceInitType": "",
"reduceFixup": "",
"x": 1270,
"y": 1560,
"wires": [
[
"f46f070a.905bb8"
]
]
},
{
"id": "ce50d3fe.fae1c",
"type": "api-current-state",
"z": "3c74f436.9e051c",
"name": "Switch standby Watt",
"server": "938bbb0d.d39038",
"version": 1,
"outputs": 1,
"halt_if": "",
"halt_if_type": "str",
"halt_if_compare": "is",
"override_topic": false,
"entity_id": "input_number.switch_standby_watt",
"state_type": "num",
"state_location": "payload",
"override_payload": "msg",
"entity_location": "data",
"override_data": "msg",
"blockInputOverrides": false,
"x": 1040,
"y": 1540,
"wires": [
[
"c55b5515.fe1ba8"
]
]
},
{
"id": "579fecb9.d13fd4",
"type": "delay",
"z": "3c74f436.9e051c",
"name": "",
"pauseType": "delay",
"timeout": "5",
"timeoutUnits": "milliseconds",
"rate": "1",
"nbRateUnits": "1",
"rateUnits": "second",
"randomFirst": "1",
"randomLast": "5",
"randomUnits": "seconds",
"drop": false,
"x": 1050,
"y": 1600,
"wires": [
[
"c55b5515.fe1ba8"
]
]
},
{
"id": "683e95e4.7b8e0c",
"type": "mqtt out",
"z": "3c74f436.9e051c",
"name": "",
"topic": "power_consumption/kWh/xyz",
"qos": "0",
"retain": "true",
"broker": "bda1e0cb.3e2458",
"x": 1840,
"y": 1500,
"wires": []
},
{
"id": "fe4ed983.e12f48",
"type": "delay",
"z": "3c74f436.9e051c",
"name": "",
"pauseType": "delay",
"timeout": "50",
"timeoutUnits": "milliseconds",
"rate": "1",
"nbRateUnits": "1",
"rateUnits": "second",
"randomFirst": "1",
"randomLast": "5",
"randomUnits": "seconds",
"drop": false,
"x": 1590,
"y": 1400,
"wires": [
[
"eaf71cf9.23401"
]
]
},
{
"id": "eaf71cf9.23401",
"type": "change",
"z": "3c74f436.9e051c",
"name": "back to zero",
"rules": [
{
"t": "set",
"p": "payload",
"pt": "msg",
"to": "0",
"tot": "num"
}
],
"action": "",
"property": "",
"from": "",
"to": "",
"reg": false,
"x": 1790,
"y": 1400,
"wires": [
[
"683e95e4.7b8e0c"
]
]
},
{
"id": "82898f2c.ddf6d",
"type": "delay",
"z": "3c74f436.9e051c",
"name": "",
"pauseType": "delay",
"timeout": "50",
"timeoutUnits": "milliseconds",
"rate": "1",
"nbRateUnits": "1",
"rateUnits": "second",
"randomFirst": "1",
"randomLast": "5",
"randomUnits": "seconds",
"drop": false,
"x": 1590,
"y": 1600,
"wires": [
[
"fb35bf26.9afc1"
]
]
},
{
"id": "fb35bf26.9afc1",
"type": "change",
"z": "3c74f436.9e051c",
"name": "back to zero",
"rules": [
{
"t": "set",
"p": "payload",
"pt": "msg",
"to": "0",
"tot": "num"
}
],
"action": "",
"property": "",
"from": "",
"to": "",
"reg": false,
"x": 1790,
"y": 1600,
"wires": [
[
"683e95e4.7b8e0c"
]
]
},
{
"id": "d70f995d.901bc8",
"type": "comment",
"z": "3c74f436.9e051c",
"name": "Theoretical Power Consumption",
"info": "",
"x": 170,
"y": 1340,
"wires": []
},
{
"id": "938bbb0d.d39038",
"type": "server",
"z": "",
"name": "Home Assistant"
},
{
"id": "bda1e0cb.3e2458",
"type": "mqtt-broker",
"z": "",
"name": "[email protected]",
"broker": "10.127.20.238",
"port": "1883",
"clientid": "",
"usetls": false,
"compatmode": true,
"keepalive": "60",
"cleansession": true,
"birthTopic": "",
"birthQos": "0",
"birthPayload": "",
"closeTopic": "",
"closeQos": "0",
"closePayload": "",
"willTopic": "",
"willQos": "0",
"willPayload": ""
}
]
EDIT: You have to insert an rbe node between the switch and the interval length, so if the switch goes to unavailable and back to the previous state, it is not taken into the calculation
The reason I set the kWh back to zero imediately in the flow is because the utility meter only adds positive changes from a sensor. So only this way the difference from the last value to the current is the actual consumption
Now you need a MQTT sensor to recieve the values:
- platform: mqtt
name: "XYZ Power Consumption"
state_topic: "power_consumption/kWh/xyz"
unit_of_measurement: 'kWh'
icon: 'mdi:flash'
and of course a Utility Meter:
xyz_month_energy_draw:
source: sensor.xyz_power_consumption
cycle: monthly
The input numbers are not a necessity - I just like to be able to quickly change them (don’t even know why, because they shouldn’t ever change anyway)
One for the standby consumption of the switch
switch_standby_watt:
name: 'Switch Standby Watt'
min: 0
max: 10
step: 0.01
mode: box
and one for the wattage of the device
xyz_watt:
name: 'XYZ Watt'
min: 0
max: 3600
step: 1
mode: box
If you don’t use the input numbers, you can simply remove the part of the flow between OFF/ON and the functions, and in the function instead of
msg.payload = (msg.payload[1] * 0.00000027777778) * (msg.payload[0] / 1000);
you use:
msg.payload = (msg.payload * 0.00000027777778) * ( [INSERT POWER CONSUMPTION IN WATT] * 1000);
The biggest issue right now it, that “unavailable” status is being ignored - this doen’t matter as long as they are powered and just lose connection for a moment - just think about it, if you want to unplug them for some time the easiest workaround would be to treat OFF an UNAVAILABLE the same way and assume both are 0 consumption … I don’t like this solution so I’ll look into it furthrer
Hope some of you like this
2 Likes
Any ideas how you use the integration sensor twice?
sensor:
- platform: integration
source: sensor.current_power
name: energy_spent
unit_prefix: k
round: 2
I have two plugs i’d like to measure the kWh, i can get one working with:
sensor:
- platform: integration
source: sensor.outdoor_tree_lights_mss310_power_sensor_w_0
name: energy_spent
unit_prefix: k
round: 2
But once i had the second source, neither sensor then works:
sensor:
- platform: integration
source: sensor.outdoor_tree_lights_mss310_power_sensor_w_0
name: energy_spent
unit_prefix: k
round: 2
- platform: integration
source: sensor.smart_plug_2_mss310_power_sensor_w_0
name: Server_Rack_Plug_Power_Total
unit_prefix: k
round: 2
Do i need to keep them separate, and use sensor twice?
everyone still trying to do that - there’s a custom component in HACS called “Powercalc” - it works flawlessly and is very simple to use … I found out about it a month ago and it now calculates pretty much every lamps and switches theoretical power consumption in my house.
5 Likes