-
Notifications
You must be signed in to change notification settings - Fork 33
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
Sensors for pricing data #51
Comments
Just bumped pyeloverblik to version 0.3.0 that supports reading fees :-) |
Awesome! I can get cracking on this one then. |
runemoennike
pushed a commit
to runemoennike/homeassistant-eloverblik
that referenced
this issue
Oct 5, 2022
…ttributes for tariff sum for each hour of the day.
runemoennike
pushed a commit
to runemoennike/homeassistant-eloverblik
that referenced
this issue
Oct 7, 2022
runemoennike
pushed a commit
to runemoennike/homeassistant-eloverblik
that referenced
this issue
Oct 10, 2022
JonasPed
added a commit
that referenced
this issue
Oct 10, 2022
#51: Added sensor for sum of tariffs.
I think this one can be closed? |
Yep :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The price of electricity consists of the generation cost, the transport costs, and fees. The generation costs are not available from eloverblik, but can be pulled from Nordpool. However, the transport costs and fees are available from eloverblik, at least on their website, through the "prisdata" export.
Given that this data is also available in their API, it would be very neat to expose it as sensors in this plugin. That way, it can be combined with data from the "Nordpool" plugin to give a pretty accurate hourly price forecast per kWh. The transport costs have to be updated daily, as "peak hour" pricing is different in the summer and winter periods.
@JonasPed unless you have a burning desire to look at this, would you mind if I gave it a shot? I'd also need to add it to your pyeloverblik package. At least I didn't find any code relating to this price data there.
Edit: I've made a PR to pyeloverblik that fetches monthly consumption data, which can be used to implement this one pretty easily.
The text was updated successfully, but these errors were encountered: