I have this
The first one is input helper with manualle entered data
The second one is generated by HA, i.e. in my energy dashboard settings for gas_usage I use a fixed price so the one you see shows ‘today’ costs which are 0 as I did not enter anything today
From what i can see you seem to use a separate entity for the price not? Maybe that could be an issue??? But on the other hand it worked in SQLite
yes, its really strange, look at this:
This is all based on 
WHen i select this entity as a total cost tracker it shows up this:
- name: "Daily Energy Cost3"
device_class: monetary
unit_of_measurement: EUR
state_class: total
state: >
{{ (states('sensor.p1_gas_consumed_cumulative')|float(0))}}
Also wrong calculation because the price is 0.85.
WHen i select this, this is my manual gasprice in a input device :
- name: "Daily Energy Cost2"
device_class: gas
unit_of_measurement: m³
state_class: total_increasing
state: >
{{ (states('input_number.gasprice')|float(0))}}
i get this
If i select this entity:
- name: "GasTestCostCalculatorTotal"
device_class: monetary
unit_of_measurement: EUR
state_class: total_increasing
state: >
{{ (states('sensor.gas_helper_test')|float()) + (states('sensor.today_gas_total_cost')|float())}}
i get this
Now when choosing: 
template:
- sensor:
- name: Today GAS Total Cost
device_class: monetary
state_class: measurement
unit_of_measurement: EUR/m³
state: >
{{ (states('input_number.gasprice')|float(0))}}
When selecting this helper as an cost device
also nothing
If it weren’t so sad … I would be LOL, I hope someone picks up on your github ticket
I will enter new values today…fingers crossed
haha true, this is so annoying, getting crazy of it.
But i found out something else.
I did create another entity that collecs the data of my gas-usage.
So when i selected that entity, and selected the my entity with colletcing the total cost it works.
There is a stupid thing happening, check this out.
i made this entity some hours ago:
- name: "Gas Usage Graph Total"
state: >
{{ (states('sensor.p1_gas_consumed_cumulative')|float(0))}}
unit_of_measurement: m³
device_class: gas
state_class: total_increasing
but it did somehow autocreate this entity, i did not make that one
Could that be the problem whats going on?? HA create a random new device based on the selected entity in the dashboard…
Story continues, my zigbee device transmitting from the elec meter had a connection issue for more than 1 day. Repaired yesterday…history of costs (!) all gone, I did not change the device and my consumption is still OK…yippie 
So here is what I did …awaiting the next issue
0. made sure elect costs are no longer calculated (setting in Energy dashboard)
EDIT: why I needed to do this was because data from the original sensor.linky_base_cost ended up in sensor.linky_base_cost_2 and bits and pieces in _3 … _5…a total mess
Thanks for your info.
I think i got it working, i will also wait again from now on 30 minutes, as my new device what i created had + instead of * so if that works, i need to try how i can import the old data into this new device. but lets wait.
I also will report at 12:00 and see if it did calculate, but i think its correct.
I’m using a total cost device, using this template
So this (device) entity is called sensor.calculategaspricetest, this calculated the value i use in my helper
this is the template from the helper.
- sensor:
- name: Today GAS Total Cost
device_class: monetary
state_class: measurement
unit_of_measurement: EUR/m³
state: >
{{ (states('input_number.gasprice')|float(0))}}
this is the helper
this is the total entity calculated with the template from above and the helper
- name: "GasTestCostCalculatorTotal"
device_class: monetary
unit_of_measurement: EUR
state_class: total_increasing
state: >
{{ (states('sensor.gas_helper_test')|float()) * (states('sensor.today_gas_total_cost')|float())}}
SO the above one creates the total EUR what i use in the energy dashboard, and like now it looks ok.
Fingers crossed.
I used:
insert into statistics (created,start,state,sum,metadata_id) select created, start, 0, sum*0.175, [costsensor] where metadata_id = [consumptionsensor]Yes it works, calculation is correct now, using a TOTAL entity with the cost.
Thanks for the code, but i want to import all old costs, what where recorded in my database into this new one because my old costs are changed daily, but i want to import till yesterday and not today.
How can i do that ?
My new device ID is 135
my old device ID is 29
add a where-clause to exclude today
insert into statistics (created,start,state,sum,metadata_id) select created, start, 0, sum, [NEWcostsensor] from statistics where metadata_id = [OLDcostsensor] and start < '2022-12-01'
Note that if the newcostsensor already has values before today then it will throw an error as duplicates are not allowed
In the meantime…costs screwed up again, since I did not add anything to short_term, this started from scratch and now overwrites the statistics value…
Try it like i did, it works.
ANd thanks for the code, i will try it when i do test a new migration and see if it gets corrected.
But i did find out HASS calculation does not work as expected.
I show u why:
This is my utility meter helper:
It reads the data from this entity:
See the difference…
The source is reporting: 0.68425
and the utility meter is reporting: 0.68935
Mine works too but I have just screwed up too much with removing data. I mended the last short_term record to show the correct ‘total’ and now it shows fine again…not 100% confident after last nights reset of course 
… in other words, I know how to construct the right values now but I am totally in the dark as to when a reset takes place and why for pete’s sake it created 4 cost sensors since yesterday wihtout taking the correct values.
Yes its weird, it just auto creates costs sensors, if u delete one of them the data is gone forever…
So you think the problem is in the short_term ?
That is my current guesswork, possibly the reset screws up short_term and then HA thinks…oh…let’s create a new one…
Well lets try it, i will do the migration again, it takes arround 40 minutes and
i will try to correct the short_term and see if it get fixed.
If not, then ill do start with adding the new cost TOTAL entity what i created yesterday, and see if it calculates right.
If that does, i will use your code to import the old data into the today created one.
Because a total entity should behave like a total, and no calculation is done in the EnergyDB… so it should work normal, but what i dont know is if i can import the data from the (entity containing a fixed price) to a total entity… thats the question.
I opened a case with HA now but it is too hard for me to create a replication of it, asking for insight in how this works which may then explain the mismatches…still, this seems very much a bug but we need to know the cause to tackle it
Well, with my issue i can replicate the issue, by just using the migration script.
This only causes that the cost sensor getting messed up, while the rest works perfect with no issue…
