See the comment above, Enphase will re-enable downloads after 2019-04-01 00:00 UTC
A request to Enphase has been made to increase the monthly quota for PVOutput, this may or may not be granted. In the meantime, polling rates to Enphase has been reduced to 20 to 40 minutes.
Thanks for the update. Do you expect the data to catch up after April 1, or should we expect to have to manually export from the Enphase site and backload here?
BLOKE, I am a little confused. At one time Enphase went to a storage timeline of more than 5 mintues for new systems in their storage area causing our PVO bell curves to look like steps for a given day, but I will say I was one of the early adopters and they allowed for 5 minute captures from my home to their site and reset storing it as such. Then you read their site via API to store in PVO. So up to this month what has changed specific to my system? And when you say change the reading interval from PVOUT into Enphase site are you saying to change the reading interval in LIVE SETTINGS STATUS INTERVAL from 5 which I have now to i.e. 15 or 20 for each system I may have setup to cut down on the number of reading calls you make to enphase? And if I did will you still be getting all the data of my stored 5 minute intervals from Enphase which I know they have though it would now be delayed in the new PVOUT interval setting of 15 to 20 minutes pickup? Or what am I missing? I dont care if it takes less calls further apart to get the data from enphase but by the end of any day I want to ensure that PVO gets all my 5 minute interval data from Enphase as the goal.
I guess it’s good that there’s enough new Enphase sign-ups for this to happen (that’d be me, sorry folks!)
It’s loading live data again now, however it only seems to have back-loaded the last 24 hours (ie from 10:10AM yesterday, Darwin time). I’m guessing that’s just a setting within the query, as the historical data is still there in Enlighten… Would it be possible to extend the backloading to also cover the whole previous day we’ve missed?
Mine still not working noticed other systems around me are.
Revoked and re added twice
Is there still a problem
Unfortunately a manual backload is required, only the last 24hrs will be retrieved.
There are no settings to change.
Data is still in 5-minute intervals, the retrieval from Enphase has decreased from every 15-minutes to every 20-minutes.
This allows us to stay under the monthly request limit for all systems.
Looks like an authorization issue as Enphase is reporting -
Thanks done it again and now works. Cut and pasted it on the iphone at work so maybe it picked up something
OK BB, I left alone. Now I understand its your execution of the API limitaiton they are making it on. My systems started auto collecting again for 4/1 through the typical PVOUT api retrieval. Thanks for clarifying.
Okay thanks. For others if you want instructions on how to do this, check out an older post of mine: Backloading Enphase data from within the last week
My Enphase is now working again on PVOutput. It also backloaded the entire day of 31 March but not 30 March or the half day missing from noon on the 29th.
I’ll look into backloading the data from the Enlighten site manually.
If anyone would like to use it, I’ve got a simple Excel application that will download your data from Enphase for a specific date and then upload it to PVOutput. Here’s a link to the file -> Update_PVOutput.
It is a macro enabled spreadsheet but nothing is hidden. Enter your Enphase and PVOutput data on the Parameters sheet along with a date you want to update, click the Get Enphase Data button to download from Enphase and then click the Upload to PVOutput button to upload. The downloaded data is stored on the Enphase sheet so you can validate it before you upload if you want to.
Edit: I think I may need to change the sharing option on this file. I can’t do that until I get home. Should be fixed by 5pm PDT.
Edit 2: Link sharing updated. Anyone with the link should be able to view/download the file now.
HI, trying to use your enphase to PVOutput Excel application but cannot find the Enphase Data API key.
Is this an API key you have created for the app or do we have to create our own API key? (Unable to find a PVOutput Updates project API Key at https://developer.enphase.com/admin/applications/)
This should be your pvoutput system API key. Login to your pvoutput.org account. At the very top list of menu options, select “Settings”. Scroll down to the bottom. Enable API Access, generate a new API key if needed. Plug this key into his spreadsheet. Keep this API key private.
It looks to me that you also need to create an Enphase developer account. Use the Watts plan (free). Create an application to get an Enphase API key. I’m on a Mac which does not support VBA, so I cannot test his macros.
Sorry about that, @billz is correct, you need to create an Enphase api key for this to work. Login in to (or create) a developer account at https://developer.enphase.com/login and then create a new application, you can name it whatever you want, and use the API key for that application.
@pjschaffer Originally created an Enphase developer account (Watts plan) and got an Enphase API key, and populated all the required cells, but when I click “Get Enphase Data” it gives a "run-time error ‘6’ ".
When I click on debug it highlights this line " UnixStart = Unix_dt(U_Year, U_Month, U_Day, 0, 0, 0) - TimeOffset * 60 * 60 'parameters are Year, Month, Day, Hour(24 hour format), Minute, second "
Is this complaining that the Date format being received from Enphase is not in the correct format? (i.e. does Enphase use a different format for different localities, e.g. Australia UTC +11?) Thanks
Not sure if this is the problem, but normally ( by default ) when numeric data are entered into Excel they are RIGHT aligned - like in the the attached graphic.
Your screenshot shows that the data are LEFT aligned. Either the cells have been formatted to be that way OR Excel thinks that you have entered TEXT rather than NUMBERS. If the data are being treated as TEXT it would cause the function to fail.
Sounded like a valid explanation,but unfortunately aligning right and formatting cells as numbers made no difference. Thanks for your input, it made logical sense to me.
Wondering if it doesn’t like a + value for UTC?