-
Notifications
You must be signed in to change notification settings - Fork 10
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
Comments
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 So of there is a way to pull the production and consumption frequently (5, 15, 30 min or w/e) would be great! |
Would we be able to simulate Tibber's "sensor.accumulated_consumption_current_hour_xxxxx" in this case? |
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? |
I think last meters are now available? I helped a friend and he got them both. |
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
andlastMeterConsumption
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
Power outage around 04.00 and the Pulse was unavailable and needed rebooting (which I did in the morning).
The text was updated successfully, but these errors were encountered: