Ah I see! Thx!
Thanks for the adjustments. However, it does not update the “Energy consumption”.
I use the “daily yield” of the homewizardP1 meter for this.
See picture.
So, today, I finally found time to actually update the flow.
Is this a normal thing to expect now?
Not sure why that ‘Actual’ value fluctuates between a few K and 0.
It looks simular to what I have. So I guess it is normal. It can take a day to get the average values right. Are you using the special triggercard or are you triggering on a time card?
Looks good. The kWh used (today) is a mystery for me still. I dont know what it is for and how it shows on pvoutput.org
You could try leaving it out of the flow
I have a ‘Power by the Hour’ on my P1 meter, and take the ‘kwh this day’ value, which represents the actual kwh my house has used.
so far it is clear. What is not clear to me is what PVOutput does with that value 
1 Like
I guess it will behave after a while. I use the same flow as you do.
No clue where averages of 7000W+ come from though 
My all time max output was 5800W 
The Average figure varies because the Energy is being incremented in 300/300/400Wh lumps rather than “smoothly”. You will note that Average is zero when Energy is unchanged from the previous data submission. I had a similar experience - but even more exaggerated - my inverter only reports Energy in 1kWh lumps - so I would see lots of rows with Average = 0. Then suddenly one row with Average = 12000W. Uploads are at 5 minute intervals; there are 12 intervals in an hour so a 5 minute jump of 1kWh is an Average power of 12000W.
To smooth things out, I have reverse-engineered my very lumpy Energy readings into a smoother curve by accumulating the Power over time. I use a virtual device and upload the data using its capability values. If I compare lumpy and smooth Energy the two curves look very similar. And now my data in PVOutput is nice and smooth…
Nice simple app that supports the PV Output site - thanks Robin G. I, too, would advocate for the ability to upload Export values, alongside Import that I note is available from the API document. Agree that separating the “simple” use case from the more complex on separate flow cards is a good way to proceed.
