Add lastMeterProduction and lastMeterConsumption from Tibber Pulse

[tfriberg]

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

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

[toreamun]

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]

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]

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