admin mjhemworth and simply set the forced discharge time (which will inevitably be at 00:00), to some time in the future I presume you mean forced charge time? Not discharge time? mjhemworth So if the inverter was set to 10%, a preset value in WW at 12% would probably keep it responsive. This simply moves the problem where the Solax system will go idle at whichever min SOC that's been specified. Solax goes idle at min SOC.
mjhemworth Yes, I meant charge, not discharge. Ideally Solax would fix the problem, though realistically not sure that will happen anytime soon, so if a work around could be achieved through WW, that would be wonderful
admin mjhemworth Are you saying that simply putting any charge from grid From Time in the future would make it come out of idle mode? Or setting the From Time to basically the current time would trigger it? Perhaps we need that to be the first instruction we set...
mjhemworth That's not what I'm saying. The facts as I observe them are: Once the real SoC on the battery reaches the min SoC set on the inverter, the system appears to become non-responsive to charge instructions sent through API. In this unresponsive state, I don't think WW are able to change neither the start or end time for forced charging. To get out of this state there are three ways: PV panels increase the charge of battery > min SoC setting min SoC setting is lowered on the inverter to become less that the real SoC on the battery. set a new charge period on the inverter, eg, set an end time on the inverter in the future. I have managed to do this though the Solax cloud app, but not through WW. Why, I don't understand, because I assume solax cloud app also communicates through API.
