Has anyone else just ran into a problem with the data uploaded to pvoutput? Just started today where the data has started acting strange when uploading and then stopped all together. I get an error in the iotawatt portal, seen here, and the data on pvoutput is also below showing the odd pattern and no longer uploading. I did change the api key but that didn’t change anything. From what I read about the 502 error, it seems like something in pvoutput’s end, but just want to see if I’m the only one.
This is the error in iotawatt
Has anyone else just ran into a problem with the data uploaded to pvoutput? Just started today where the data has started acting strange when uploading and then stopped all together. I get an error in the iotawatt portal, seen here, and the data on pvoutput is also below showing the odd pattern and no longer uploading. I did change the api key but that didn’t change anything. From what I read about the 502 error, it seems like something in pvoutput’s end, but just want to see if I’m the only one.
I’m seeing it on all of my development units and also on a couple of other units elsewhere. It seems to have started about 09:00 UTC this morning (Nov 6). I’m noticing that they all occasionally seem to get a spurt of updates through and are staying pretty near up to date.
So it seems to be a problem with the PVoutput service, which I believe is in Australia. It’s interesting that you seem to be in Massachusetts and all of the other systems I’m looking at are in New Hampshire. Perhaps it’s a communication issue. I’ve posted the problem on in the PVoutput forum.
But your problem appears unique in that you are only getting intermittent status uploads. All of the other units are uploading the backlog data seamlessly when they get the chance. Your site appears to only update a couple of times every half-hour or so. Are you uploading with an IoTaWatt? If so, can you post your PVoutput setup so I can try to figure out why you don’t get a seamless upload?
Im in agreement that it was on pvoutputs side as nothing changed in iotawatt. Last night I stopped tge uploader service in iotawatt. This morning I got the message my system was offline. I went and reenabled the upload service and got an error
Seems to be an IoTaWatt upload issue, as I noticed no data for a few hours today (as I’m using PVOutput in place of IoTaWatt’s graph for power monitoring), and the data from the SMA inverter uploaded fine at the same times IoTaWatt reported 0W.
That “config file not current” message is unrelated to this issue. It is simply saying that the new config that was sent is not based on the currently active config. Usually this occurs when an the app is run from different devices. Stopping and starting an uploader changes the config.
The problem seems to have been resolved about 0500 UTC today. All of the systems I was watching have uploaded their data seamlessly.
I don’t believe it had anything to do with IoTaWatt. There is a thread on the PVoutput forum where users with other uploaders were also experiencing problems.
My guess is that it had something to do with Cloudflare.
