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

Documentation updates, energy dashboard and cost tracker #1136

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

gcoan
Copy link
Contributor

@gcoan gcoan commented Dec 23, 2024

Simplified energy dashboard setup to use total sensors instead of today sensors and added details of setup for grid return (electricity export).

Added example entities to be used for electricity import and export to the cost tracker documentation.

_docs/setup/energy_dashboard.md Outdated Show resolved Hide resolved
_docs/setup/energy_dashboard.md Outdated Show resolved Hide resolved
@@ -21,6 +21,8 @@ This is the meter whose tariff will determine the rate the entity consumption is
### Entity

This is the entity whose consumption should be tracked and the cost calculated against. This entity should be reporting in `kwh`.
For example, `sensor.octopus_energy_electricity_{{METER_SERIAL_NUMBER}}_{{MPAN_NUMBER}}_current_accumulative_consumption` for grid import today reported with an Octopus Home Mini,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: I'm not a fan of this as it's main purpose is for tracking entities provided outside of the integration, and this example would cause confusion when compared to the cost sensors provided by the integration (as one includes standing charge and one doesn't).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was asked by a user on the GivEnergy customer forum for how to create a HA dashboard sensor that would replicate what they saw on their Octopus account bill. The cost tracker seemed the best way of doing this to me to create a 'monthly sensor' as they have an OHM and the meter readings would therefore be the same as is used for their bill.

Couldn't do it with a utility meter as there isn't a suitable entity to sum, and would have the need to get the reset point right which the cost tracker does quite easily.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's probably best to move this to the FAQ section instead then, as if they come to the cost tracker page, they're probably already thinking about what they want to do. The FAQ entry should also point at #849, as if that gets more requests, I'll take a look at it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes something in the FAQ's about how to use cost trackers to recreate the Octopus bill would be a good idea.
I personally use the Energy dashboard as you already mention, but the OP wanted a dashboard sensor

_docs/setup/energy_dashboard.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants