wraithnot
Model 3 VIN #2942 Model S VIN #5785
That is not the behavior I want. It wish Tesla would keep things simple and implement scheduled self-consumption before jumping into estimating my needs tomorrow. My observations are that they are not taking local weather conditions into account (today and tomorrow) when deciding how much to discharge. My area is looking at 6 days of cloudy/rainy weather. I have seen the powerwall drain itself in similar situations. That is a bad move for someone on a demand plan.
In self-consumption mode, the batteries do not seriously begin to discharge until 4pm for cloudy days and 6:30pm for sunny days. With 6 days of clouds and rain, time based control could leave me without enough to traverse the demand period.
Got it. I have the same power company (PG&E) as the Tesla mothership so I'm not surprised that they configured things to work perfectly for my situation and not for people in other areas.
When I was trying to get my powerwall to behave, I came across this article Powerwall2 update – Time-of-Use enabled that includes a description of some custom code that a powerwall user wrote (BJReplay/PowerwallService) to get more control over how the powerwall functions. Parts of this may be specific to Australia and will probably require some customization to work in the US. But the description sounds kind of what I think you are trying to do:
"Broadly, the service sends your solar array details to an external solar-output estimation provider, who combines them with local weather forecasts, to return a tailored estimate of your future energy production to the service. You define your estimated usage and the amount of power your PW2 needs to retain, the TOU periods and tariffs you have and so on in a .config text file. Then, the service runs to calculate the amount it needs to save for the following day, taking in to account the estimated future solar generation, and it will use your Tesla cloud login to switch the PW2 modes from “self-powered” to “standby” or “backup” (charging)."