Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support weekly and monthly cost sensor breakdowns #714

Closed
2 tasks done
BottlecapDave opened this issue Jan 20, 2024 · 7 comments
Closed
2 tasks done

Support weekly and monthly cost sensor breakdowns #714

BottlecapDave opened this issue Jan 20, 2024 · 7 comments
Assignees
Labels
enhancement New feature or request external contributions welcome The feature has been accepted and the criteria has been defined

Comments

@BottlecapDave
Copy link
Owner

BottlecapDave commented Jan 20, 2024

Describe the feature

The cost sensor should be expanded to support weekly and monthly breakdowns in addition to the current daily breakdowns.

These weekly and monthly breakdowns should have peak/off peak variations

Expected behaviour

The following sensors should be available

  • sensor.octopus_energy_cost_tracker_{{COST_TRACKER_NAME}}_week
  • sensor.octopus_energy_cost_tracker_{{COST_TRACKER_NAME}}_week_peak
  • sensor.octopus_energy_cost_tracker_{{COST_TRACKER_NAME}}_week_off_peak
  • sensor.octopus_energy_cost_tracker_{{COST_TRACKER_NAME}}_month
  • sensor.octopus_energy_cost_tracker_{{COST_TRACKER_NAME}}_month_peak
  • sensor.octopus_energy_cost_tracker_{{COST_TRACKER_NAME}}_month_off_peak

The day that represents the start of the week should be configurable.

The start day for the month (1-28) should be configurable and effect the month based sensors.

Use Case

I want to be able to see what my sensors cost me on a daily or monthly basis.

Confirmation

  • By submitting this feature request, you agree that you have read the documentation and confirmed it does not already exist
  • I am willing/able to help contribute to the solution of this feature
@BottlecapDave BottlecapDave added the enhancement New feature or request label Jan 20, 2024
@BottlecapDave BottlecapDave self-assigned this Jan 20, 2024
@Psai
Copy link

Psai commented Jan 20, 2024

Would/should this also include export meters?

@BottlecapDave
Copy link
Owner Author

Export meters should already be supported (if they're coming through your account), as these are sensors for tracking costs of other entities within HA (e.g. television if you have a sensor reporting it's kwh usage).

@RexNoctis
Copy link

Just a small suggestion/request, would it also be possible to also make the start date of the month configurable? It would be nice to see costs based on the billing period?

@BottlecapDave BottlecapDave added the external contributions welcome The feature has been accepted and the criteria has been defined label Feb 1, 2024
@alfwro13
Copy link

alfwro13 commented Feb 7, 2024

You can already do the same thing with Energy Meter (HACS integration) https://github.com/zeronounours/HA-custom-component-energy-meter

@BottlecapDave
Copy link
Owner Author

Thank you for raising this as a potential solution. The cost trackers were introduced as I wanted a solution that would adapt automatically when a persons tariff changed and would cope with tariffs with varying rates (like agile). My main issue with the integration you linked is that It's not configurable via the UI - More users who are using HA and this integration are more comfortable with a UI and don't want to be diving into yaml to configure entities. It's crazy a simple accumulation sensor that resets on a schedule isn't available natively in HA.

@Meatballs1
Copy link
Contributor

I just feed my cost tracker into utility meter helpers with a monthly schedule and that seems to do this unless I'm missing something.

@BottlecapDave
Copy link
Owner Author

This is now available as part of v10.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request external contributions welcome The feature has been accepted and the criteria has been defined
Projects
None yet
Development

No branches or pull requests

5 participants