Dynamic Energy Cost

arva · October 22, 2024, 6:19am

i reccomend to just change the entity id back to what it was. So all your other stuff that used Nordpoo works as well. This Nordpool naming is pretty bad to be honest.

Rams · October 23, 2024, 7:43am

I follow this threat.
Last august I’ve also created a feature request:

github.com/martinarva/dynamic_energy_cost

Update the "Energy Usage Sesor Entity ID"

opened 08:53AM - 27 Aug 24 UTC

MrRamsus

enhancement

**Is your feature request related to a problem? Please describe.** A clear and …concise description of what the problem is. Ex. I'm always frustrated when [...] It would be nice if I'm able to edit the "Energy Usage Sensor Entity ID (kWh)" (or other values) for the Dynamic Energy Cost. This would be handy for the situation that the Entity has been changed, or you have a new electricity entity. **Describe the solution you'd like** A clear and concise description of what you want to happen. A way to edit the values (GUI or manual) **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. Remove and add the entity again. But history data is removed **Additional context** Add any other context or screenshots about the feature request here.

In my specific case, my Vehicle charger was defect and it was switched. My entity has been changed in HA and the Entity ID in the app couldn’t be changed. I’ve configured it again, but my history has been lost now.

I hope there should be a nice feature available to have a way to change the value without loosing history.

christbj · October 23, 2024, 8:00am

How to keep history when replacing a device has been discussed before and there are suggested sullitions for this. I have not tried them myself, but i would create a new backup before testing this. Take a look at this thread: Replace entities and keep history (BREAKING CHANGE starting HA Core 2023.4) - #4 by e-raser

phsdv · October 25, 2024, 1:36pm

The entity changed the name because the source and the integration that uses this source gave it a new name. It is not possible for me to change the entity id back.

arva · October 26, 2024, 5:50pm

Hi All!

I’m sorry I haven’t maintained the integration for a while. Unfortunately can’t promise to have time in the near future as well.

Few recommendations so you aren’t so dependable of the integration logic:

If you have enegy (kwh) sensor, use this. Only if you don’t have, use power (W) sensor. Reason is that the energy calculations are more precice
Make a sensor with my integration and make unlimited amount of HAUtility Meter sensors for different periods you would like (all time, hourly, daily, two days, whatever you like).

I have seen all the ideas and request here and github, but just don’t have what it takes to implement these.

i’m really thrilled that so many people found something, I thought was only my need , so useful. Now I feel a bit bad letting you all down not maintaining what I started. If anybody is interested in contributing and doing what needs to be done, I would gladly give all permissions in github to continue what i started. I mean, this is what opensource sould be in my view.

In my opinion this functionality is something that would be nice to see in Home Assistant core. It would make so much sense to have a cost/profit side in the energy management.

JukeboxBill · October 28, 2024, 10:44am

Maybe you found a solution already, but for showing previous data I use the history-explorer-card integration:
https://github.com/SpangleLabs/history-explorer-card

Vallekano · November 28, 2024, 2:34pm

I had the same situation and I just found it. The config is in /config/.storage/core.config_entries

If you search for “electricity_price_sensor” you will find your configs with your current sensor for pricing. I replaced it with new one and restarted HA and it looks ok…

ScubaDam · January 19, 2025, 11:08pm

Hi everyone, I’ve setup about 27 devices (Meross Plugs) and I noticed the costs going up very quickly. Is that because Meross consumption uses Wh and this integration only works with devices using kWh? If so is there anyway to use energy consumption Devices that statistically use Wh?

ScubaDam · January 20, 2025, 12:28pm

Just for anyone else that had this problem. I think I solved it.
In dev tools -Statistics. I went into each sensor’s settings and changed the unit from Wh to kWH. The statistics list still says Wh even after a reboot, however if you go back into the sensor’s settings, you will see it has changed to kWH and the graph for the daily costs for each device is now working correctly!

Also I built an automation to zero the daily cost for all 27 devices which works a dream thanks to the service mentioned above and ChatGPT making all the typing out of 27 entities a doddle!

MrNorth45 · February 24, 2025, 7:10am

I like this integration but sadly it is producing lots of errors, and the cost is not updating as it should:

2025-02-24 08:05:21.055 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:21.056 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:21.056 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:21.057 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:21.057 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.570 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.571 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.572 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.572 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.573 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.573 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.588 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.589 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.590 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.590 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.591 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'float'
2025-02-24 08:05:23.591 ERROR (MainThread) [custom_components.dynamic_energy_cost.sensor] Failed to update energy costs due to an error: unsupported operand type(s) for +: 'decimal.Decimal' and 'floa

Any idea what the problem is? I just added the sensors (kWH) and set the price to my nordpool integration.

pman100 · February 25, 2025, 12:55am

Have the same problem. No solution yet. I will share what i find

pman100 · February 26, 2025, 12:43pm

Hi, I finally made it work. I am not a pyton expert in any way but i looked in the file sensor.py and on line 383 the error msg is from. What I did was looking for mistakes on the try code above and could not find any wrong. What i think was the nutcracker suspecting hidden unwanted characters. I realigned line 353 so that 352 and 353 is aligned (I think it was a pipe character at line 353 that should not be there) and also I remove all trailing characters and spaces on line 354 after cost_increment. Don’t think the last did anything but any way hope it is some help for you

wilcovlier · March 1, 2025, 11:54am

Hi, running into the same issue.
Am using the ENTSO-e integration to determine the hour prices from my energy supplier. Have tried both the kWh as the W sensors.
Have been trying to realign line 353 as you indicated (removing and adding all spaces upfront) but all my attemps had no success.
Could you share in more detail what you have changed?
Looking at the error, it seems more like a type cast error, but am also no Python expert.

figgins · March 5, 2025, 8:09am

Just discovered this integration, thanks a lot it saved me a big headache!

Is it not possible to edit the devices? I have created a template sensor to add transmission fees to the price and want to use the new sensor in my existing cost calculations, charts, and automations. I can’t see a way to edit the DEC devices or sensors to use the new price though, and that means I have to create new sensors and edit all my work

dgrnbrg · March 14, 2025, 9:31pm

To address this, just don’t give your tariff units of $/kWh. When it has the currency unit, HomeAssistant provides the integration a Decimal for monetary calculation accuracy, which unfortunately the integration doesn’t handle. You can also expose your tariff in a template sensor so that you can leave the units blank and have the integration work.

cykelers · March 22, 2025, 10:42pm

I cant seem to get this working. I have a sensor that is tracking my electricity costs in plain units now. I removed the $/kwh. My cost sensors aren’t accumulating data. I see them spiking when charging, but they all just report zero.
I am feeding it eat “wall_connector_session_energy” from my powerwall that is delivering energy in kwh.
any ideas where to look?
thanks!

bvweerd · March 24, 2025, 12:28pm

For the ones interested: I made the dynamic pricing with Home Assistant’s native functionality: Energy-Contract-Calculator/Dynamic Contract at main · bvweerd/Energy-Contract-Calculator · GitHub

DevBre · April 10, 2025, 5:05pm

English, Swedish, German and Dutch translation are completed.
You can now add languages through GitLocalize for the translations, click on BDVGitHub/dynamic_energy_cost | GitLocalize if you want to contribute to a translation.

wokkpash · April 13, 2025, 11:59am

Hi everyone, I’ve been looking for a functionality like this for quite a while. Great work you did! I got it to work some time ago, added an energy meter and the my hourly price and everything worked like a charm!
Recently I allowed somebody to charge their EV at my house. They asked me for the price and I thought: “great possibility to use the dynamic energy cost plugin”. By looking at the values and doing a quick calculation I realized the cost calculation is not correct for me. I did a spreadsheet calculation for today and can now see, that the values of the plugin are consistently higher than the spreadsheet data.
Can anyone help me to look at the values in the variables that are used by the Dynamic Energy Cost plugin?
Thank you very much!
Matthias

wokkpash · April 14, 2025, 3:57am

Hello alltogether, looking at the variable (…hourly_energy_cost) I found some odd behaviour: The value rises during each hour, is being reset to zero at the full hour. but the next second it jumps up to around 4ct. and increases then steadily towards the end of the hour.
Is anyone else experiencing the same? Who can point me to the area in the code, where the reset is taking place?
Cheers Matthias