-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Spikes like Gamestop? [spike in PV production]
- Thread starter Wannaretire
- Start date
In isolation, I might have said that spike is due to a cloud-edge effect, where the edge of a cloud acts like a lens, creating a temporary, dramatic spike. But, based on the nearby production curve, I am guessing there was no cloud. The dip to me looks like what you might see if you had a brief fault knocking your system off line for a few minutes.
Did you happen to see this unfold real-time? That is, did you happen to see the spike in the graph before the dip appeared? As strange as it would be, one other possibility is this is just a data issue and Tesla somehow recorded that production data to the wrong time. It seems like the magnitude of the spike roughly matches the dip, and it would explain numbers that seem well beyond the capacity of your inverter.
Did you happen to see this unfold real-time? That is, did you happen to see the spike in the graph before the dip appeared? As strange as it would be, one other possibility is this is just a data issue and Tesla somehow recorded that production data to the wrong time. It seems like the magnitude of the spike roughly matches the dip, and it would explain numbers that seem well beyond the capacity of your inverter.
Thanks. Didn't see this real time.
I'll see if it happens again soon and post here. Cheers
If you can, log into your inverter and compare it's production logs with the ones in the app. I've seen this sort of thing before but I feel like it's just a reporting issue with Tesla. That's just a hunch though.
charlesj
Active Member
That is interesting, yes. And, it seems as though it is happening at the same time with latter image magnitude a bit less.
it seems like it pretty much has to be a bug in the app - while having the production drop to zero at the same time could be some other issue causing a fault, the spike really has no other explanation. Since I think you said the spike is right at 10:00 AM, it may be that somehow that one reading later on is somehow losing/mis-reading the minutes data and placing it at 10:00. If you think about it tomorrow, check the app soon after this spike should happen and then around when the dip happens to try and confirm whether the spike appears immediately or only after the dip.
