Got my inverter temperature and Wunderground outside temperature up and running. Sensij- Your extended data outside temperature looks like its in Celsius. I found on the pvoutput forum that if you add this code into the extended data rule it will convert it and display it as Fahrenheit. v7 = v7 * 1.8 + 32. Thanks again for your help.
I also just ordered the Efergy online hub and am going to add consumption data as soon as I get it.
pvoutput.JPG
pvoutput2.JPG
-
-
Yes... just add it there. If you also want temperature from the inverter, you'll need to use the "Temperature to" field to send the wunderground station data to v7-v12. You'll also need to scroll down and set up the extended data fields.
The extended data is visible when you choose the rightmost box in the daily charts. See the screenshots below (i've deleted my API keys from the images).
pvo-1.JPG
pvo-2.JPG
pvo-3.JPG
Leave a comment:
-
I actually have a wunderground weather station online. That would be awesome to be able to add that as well. The PVoutput help section is not very helpful in explaining the v7-v12 data fields. Do I input my wunderground station there?
I also see the wunderground station box under automatic uploads. Can I just add it on that?Leave a comment:
-
-
PVOutput can integrate a variety of sources of consumption data, so that net consumption (as seen by the meter) and true consumption (including self-consumption from the PV system) can be recorded. SolarEdge can do this, but only if you use the Wattnode power meter wired in directly to the inverter.
PVOutput allows easy comparison to other systems in your area. Especially if there is one with similar azimuth and tilt, it can be a nice quick reference to verify your system is performing as it should. The ability to creates "Teams" is a nice extension of this... there are over 100 systems in San Diego part of the same team, so to the extent that nearby systems have the same weather (not a perfect assumption), you can see the differences in production due to the differences in array orientation, shade, equipment selection, etc.Leave a comment:
-
You won't exceed the API limit if you are only running one system. At a 5 minute polling rate, 300 API calls would cover 25 hours... more than you need for one day of data.
But, yes, if you set the Solaredge polling interval to 15 min, and the status interval to 5 min, SolarEdge will be providing three data points each time it is polled, and PVOutput will display those points in 5 min increments.
I lot of what I wrote earlier in the thread is out of date, there have been changes in how PVOutput handles temp and voltage. Wunderground temp and Inverter temp are both supported now, if one of them is piped to the extended data fields (V7-V12).Leave a comment:
-
quick question if I may rabbit trail from the conversation; What features does PVOutput provide that Solar Edge monitoring doesn't provide ?Leave a comment:
-
I just set my system up on pvoutput. I donated to have the 5 minute update and inverter temperature data. I dont want to exceed the solaredge api request limit. I have the live settings set to 5 mins and the solar edge poll interval set to 15 mins. My data is showing up at 5 mins intervals even though I have the solaredge poll set to 15 mins. Does it take the data every 15 mins and then update it in 5 min intervals?Leave a comment:
-
-
There is no built-in way to get both temperatures to show up for a single system. If you have an always-on computer or a Raspberry Pi, it isn't too hard to build your own uploader that could take one of the temperatures and upload it to an extended data field. An easier workaround is to just create a 2nd system, using Wunderground temp for one and inverter temp for the other. If you want to put the same SolarEdge data on both systems you'll need to have a 10 min poll interval to be sure that you don't violate the 300 API calls/day limit (you can still keep the status interval at 5 min).Leave a comment:
-
Sensij, do you know if it's possible to get weather temperature and inverter temperature to show up on the same system?
When I first set up my system, enabling both caused one to overwrite the other.Leave a comment:
-
Yes, it works for me. 403 error usually means the API key has a typo. If you have the API key correct but the wrong site id, you would get an "XML Parsing Error" - Not Authorized.Leave a comment:
-
A question on this. I just received an API key from my installer, but it doesn't seem to be working.
Is the Site ID the "Id" value shown in the "site summary" box on the right of the dashboard when I log in on the SolarEdge monitoring portal? Mine is 6 digits. I'm testing the key using the URL provided by pvoutput, that site ID, and the API key provided by my installer (32 ASCII characters).
https://monitoringapi.solaredge.com/equipment/<Site Id>/list?api_key=<API Key>
I'm getting a 403 forbidden error when I test that, though. Does this test URL work for others?
Thanks!Leave a comment:
-
You're welcome!
The 15 min polling interval is mostly inertia from when 15 min status interval was required, which was the only configuration allowed up until a couple weeks ago. 10 min polling would result in 24 * 6 = 144 API requests, which still gives you some room for other requests if you are looking at other things occasionally (inverter temp, for instance). 10 min should be fine.
A month ago, SolarEdge needed to be primary, having it secondary was not supported. I have not done any testing with Wattvision primary and SolarEdge secondary, so I can't say how it would differ from the SolarEdge primary / Wattvision secondary configuration I posted.
The weather always ties to the Primary, and should not be affected by whether you choose to have SolarEdge or Wattvision in that slot. You can, if you'd like, create a 2nd "test" system with the alternate configuration, and compare them. If you do, the polling interval will need to be 15 min, so that 24* 4 = 96 API calls go to each system and you stay below the 200 max.Leave a comment:
Leave a comment: