-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New alert: PVAC_a041_virtual_clamper_triggered #128
Comments
Interesting. It looks like we have had https://github.com/jasonacox/pypowerwall?tab=readme-ov-file#pvac---photovoltaic-ac---solar-inverter But not this one, so I will add it. Can you describe yours system? Also, do you see any odd power metrics happening at the time of the alert? |
System:
As to odd metrics: Yes. The 3-panel string is dodgy right now. Sometimes the MCI works properly, sometimes it shuts down the string entirely for no apparent reason, and sometimes it does what I call "grey but producing" meaning in Tesla One the string is greyed out but power is still being reported on it. When that happens I get:
Presumably (not a Tesla engineer and not privy to extra info): Power is still being shoved through the string even though the MCI should be open, but because it's not, it means control of the MCI on string B has been lost; ergo, "unsafe." I have noticed if I go into Tesla One and "disable" and "enable" the inverter again, sometimes the strings will come back in a better state, it is during this cycling that I saw the alert in the issue title. So I suspect it's a startup alert related to initialization of the system, something that doesn't last long. HOWEVER, it might not be normal, as I also saw |
One more note: When I set the timestamp to Tesla (they usually require that you send your installer a timestamp and the error codes your seeing, and it has to be a very sunny day at close to solar noon for them to even look at your case), they said MCIs getting into this state may be related to a "surge" of some sort. They didn't elaborate. The techs are scheduled to come out sometime within the next month or two. They are slow :/ |
Do you have the Dashboard graphing your alerts? I noticed that for my system, the "PVS_a027_Mci*PvVoltage" alerts happen at sundown right before "PVS_a059_MciOpen". The "PVAC_a014_PVS_disabled_relay " alert happens at sunrise. Here is my system and alerts over time: |
@jasonacox See discussion here: https://gist.github.com/jasonacox/91479957d0605248d7eadb919585616c#gistcomment-5364463 Without an intelligent way to query BOTH inverters, I'll only ever at best see half the picture, I'm blocked. I've gone to war trying to figure out the proper settings to make this query mechanism possible, but alas, no dice. |
Ah, thanks for the reminder. Understood... If it were me, I believe I would set up the Dashboard for at least the problematic string inverter. I have a few RPIs around so I would probably set up a dashboard for each inverter (I suppose two VMs would also work). With some customization, the two pypowerwall containers could be set up to write to the same InfluxDB, or use Grafana to pull from two sources to provide a combined view. Ideally there is some networking wizardry that would allow it to work on the same host, but it is beyond my skill or ability to test. |
@jasonacox You're clearly a manager :). I will eventually give up/in on that and follow that approach, but for now I want my cake and eat it, too! |
Ha! That usually requires two cakes. 😜 |
I solved it; though, it only works on Linux; the scripts are below. Regardless, this issue was about logging the new error code, and I still don't have the proxy working to be able to do that just yet. We can follow up on the rest here: #119 You can resolve this issue. Bash Version
Python Version
|
Saw this in my monitoring of my system, not sure what it means or where it comes from though.
The text was updated successfully, but these errors were encountered: