You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by blacknell February 18, 2025
In the energy dashboard I've added the Current Accumulative Consumption Electricity (XXX) sensor as my kWh sensor. For cost I add Current Accumulative Cost Electricity (XXX) which is the total reported cost by Octopus.
However, this cost sensor includes the standing charge which doesn't make sense given I'm using the 7p tariff for almost everything and how this forms a significant distortion
If I use the current rate for tracking costs it doesn't seem to work. The cost is always showing zero. Part of the problem is I dont really now how HA tracks and stores this in long term statistics. It would need to do the calculation every time slot and store. I'm not convinced it does.
So have I got this right? And if so, shouldn't we have an entity that shows the net price (as we have in the attribute against the cumulative. I could create a template sensor to do this but this just feels all wrong
The text was updated successfully, but these errors were encountered:
Discussed in #1230
Originally posted by blacknell February 18, 2025
In the energy dashboard I've added the Current Accumulative Consumption Electricity (XXX) sensor as my kWh sensor. For cost I add Current Accumulative Cost Electricity (XXX) which is the total reported cost by Octopus.
However, this cost sensor includes the standing charge which doesn't make sense given I'm using the 7p tariff for almost everything and how this forms a significant distortion
If I use the current rate for tracking costs it doesn't seem to work. The cost is always showing zero. Part of the problem is I dont really now how HA tracks and stores this in long term statistics. It would need to do the calculation every time slot and store. I'm not convinced it does.
So have I got this right? And if so, shouldn't we have an entity that shows the net price (as we have in the attribute against the cumulative. I could create a template sensor to do this but this just feels all wrong
The text was updated successfully, but these errors were encountered: