Fetch and store historic consumption data.
home-assistant:dev
← home-assistant:tibber_ext_stats
opened 08:27AM - 18 Dec 21 UTC
Signed-off-by: Daniel Hjelseth Høyer <[email protected] >
<!--
You are amaz… ing! Thanks for contributing to our project!
Please, DO NOT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Tibber, add external statistics
Tibber customers without a real-time meter get the hourly consumption for the previous day once a day.
Sometimes these values are temporary and will then be updated later.
The first time we fetch 5 years of day.
The next time we update the last 30 days of data.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
(Next step is to also add cost)
Leatherface
(Andreas Fornberg)
December 19, 2021, 2:47pm
24
Tested a little and seems to work fine so far.
Would also be nice with an option to add additional costs like taxes.
For example additional 33 öre/kwh in taxes here in north Sweden.
Leatherface
(Andreas Fornberg)
January 9, 2022, 9:37pm
25
For now i created addtional sensors for that but that doesn’t work for energy dashboard.
elspot_kwh_skatt:
friendly_name: "Elspot inkl. skatt (kWh)"
unit_of_measurement: SEK/kWh
device_class: energy
icon_template: mdi:currency-usd
value_template: "{{ (0.33 + float(states.sensor.electricity_price_xxx.state)) | round(3) }}"
elspot_manad_kwh:
friendly_name: "Månadens kostnad per kWh"
unit_of_measurement: SEK/kWh
device_class: energy
icon_template: mdi:currency-usd
value_template: "{{ ((0.33 * float(states.sensor.monthly_net_consumption_xxx.state) + float(states.sensor.monthly_cost_xxx.state)) / float(states.sensor.monthly_net_consumption_xxx.state)) | round(2) }}"
elforbrukning_manad_totalt:
friendly_name: "Månadens kostnad inkl. skatt"
unit_of_measurement: SEK
device_class: energy
icon_template: mdi:cash
value_template: "{{ (0.33 * float(states.sensor.monthly_net_consumption_xxx.state) + float(states.sensor.monthly_cost_xxx.state)) | round(2) }}"
Leatherface
(Andreas Fornberg)
April 13, 2022, 9:22pm
26
Asked earlier but would it be possible to add an sensor for other things that is not monitored.
If you add all indivudal devices to sources you can get the costs for each device.
The idea is that it checks for current total before adding tibberdata something like:
Tibber consumption - Total consumption of all other sources = Other sources consumption.
Instead of adding normal tibber consumption sensor you could add that other sources sensor instead and get correct total consumption.