Mid day point release update (22.9.2)

[Mahkus]

System was drawing from the grid today around 11:30am unexpectedly. App showed 0% for solar and Powerwalls but showed drawing from the grid, went to garage and saw one Powerwall light was off. Uh oh! I went to look at the others and by the time I turned around it was on again. App then showed no draw from grid and everything zero'd out. Gave it five minutes and went back and heard the low hum of the cooling fans in the battery and inverters, app showing correct values again!

Looks like it updated from 22.9.1 to 22.9.2. Not sure what the point release update is for (don't see anything different), but gee I wish they didn't roll these out at noon during peak production! 45 minute reboot cycle midday probably cost me around 10%
of my daily production.

 

[no2gates]

My thinking is that it makes more sense to do it during the peak of production so that if you're not grid tied, or the grid power goes out, you're not without power during the upgrade.

 

[skepticcyclist]

The same thing happened to me last month. But you weren't really drawing from the grid. The gateway just wasn't able to collect data during that time. I know this because I have a mixed Enphase and Tesla system. My enphase IQ still showed solar production going to the house and grid during this time.

I made a similar post when it happened to me

 

[jgleigh]

Mine updated at 1am, so there's not a consistent time.

 

[Mahkus]

The same thing happened to me last month. But you weren't really drawing from the grid. The gateway just wasn't able to collect data during that time. I know this because I have a mixed Enphase and Tesla system. My enphase IQ still showed solar production going to the house and grid during this time.

I made a similar post when it happened to me

Unfortunately I was drawing from the grid. Not much, but you can see here the blue (draw) vs green when it finished updating.

 

[slcasner]

My system had a 10:45AM upgrade from 22.9.1 to 22.9.1.1 -- no idea how that is different from 22.9.2. Once again it caused my monitoring to stop, perhaps because reauthentication was needed.