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

Add lastMeterProduction and lastMeterConsumption from Tibber Pulse #41

Open
tfriberg opened this issue Aug 17, 2022 · 7 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@tfriberg
Copy link

tfriberg commented Aug 17, 2022

Is your feature request related to a problem?
Eg. during power outages, or if the Pulse is down/need to be rebooted for any reason, the shorter term data (hour and accumulated) are lost so any calculations based on these gives faulty statistics.

Describe the solution you'd like
Being able to use lastMeterProduction and lastMeterConsumption as is available in the API, would give erroneous short term statistics but correct long term statistics.

Describe alternatives you've considered
I could use the Tibber Developer API to give me these, but the I would lose the MQTT setup and be reliable on Tibber.

Additional context
The net meter is an Landis+Gyr E360.

Power outage 20.00-21.00
image

Power outage around 04.00 and the Pulse was unavailable and needed rebooting (which I did in the morning).
image

@toreamun toreamun self-assigned this Aug 17, 2022
@toreamun toreamun added the enhancement New feature or request label Aug 17, 2022
@toreamun
Copy link
Owner

I think this can be done by adding two additional sensor. Then you can pick if you want current sensors or sensors with last registered state. I will have a look at it.

@tfriberg
Copy link
Author

tfriberg commented Aug 18, 2022

I think this can be done by adding two additional sensor. Then you can pick if you want current sensors or sensors with last registered state. I will have a look at it.

An observation I made was that the polling frequency via the Tibber devloper API of lastMeterProduction and lastMeterConsumption (at least consumption) felt erratic. When there was no grid draw (i.e. when the home used all the produced solar power and the surplus was sent to the grid), I interpreted it as that it the Pulse/the API didn't bother updating lastMeterConsumption.

So of there is a way to pull the production and consumption frequently (5, 15, 30 min or w/e) would be great!

@bjornta
Copy link

bjornta commented Oct 28, 2022

Would we be able to simulate Tibber's "sensor.accumulated_consumption_current_hour_xxxxx" in this case?

@matteskonto
Copy link

Since Tibber is receiving regular "lastMeterConsumption" (I get every 5-10 sec via Tibber API) shouldn't the hosted MQTT server also receive these updates as well?

Shouldn't everything that is pushed to Tibber cloud should also be pushed to the local MQTT server at the same rate?

@flopp999
Copy link

flopp999 commented Jan 2, 2023

I think last meters are now available? I helped a friend and he got them both.

@tfriberg
Copy link
Author

tfriberg commented Jan 2, 2023

image

I think last meters are now available? I helped a friend and he got them both.

These are the sensors I get with my existing installation. Also when adding integration again, I get the same sensors, and none I can identify as last meter.

@flopp999
Copy link

flopp999 commented Jan 2, 2023

This is what my friend get.
He has Kamstrup something...
Sweden
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants