Solax and WW not allowing overnight charge on API with Octopus Intelligent

DanHolmes · 2025-10-14T07:07:33+00:00

The API seems to not be allowing the Solax system to charge using Octopus intelligent. I have set a manual period of discharge not allowed overnight to allo...

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.

mjhemworth

Regarding this issue, I have reported it to Solax.
They checked my firmware and updated it. The nature of the problem changed slightly:

- once the min SoC level is reached and WW attempts to set a charge window, the following message is logged:
"Failed to set inverter schedule for agile log"
I don't believe this message was appearing before
HOWEVER, I am now able to wake it up by setting a WW forced charge from the Home Screen, whereas before this was not possible. I tested this over three days and the behaviour is consistent for both points

Conclusion
Is there any difference in how WW sets the charge instruction between standard agile charge slots and forced charge instructions that could justify why one works and the other doesn't?

admin

mjhemworth That’s interesting, uses the same connector class.

admin

mjhemworth Failed to set inverter schedule for agile log

Were you referring to the entry on Dec 4th at 22:30?

Looks like that failed on settings amps, register 54. However, we normally do not fail on this when SoC is 10%. Yours was set to 11% - probably as part of you experimenting. If you keep this set back to default to 10%, our instruction should not fail on this specific instruction anymore.

Also - Solax Cloud do not have an official API, and it looks like part of it has deliberately been obfuscated by them, so unless they actually provide a public API endpoint to allow inverter control, we're not divulging any information that aids them in shutting this down...

mjhemworth

After informing Solax that the problem was not resolved through the firmware upgrade, they requested the following information:

Hi dear customer,

_Thank you for the updating.

May I know what API instruction it is from WW to inverter, pls? May I know how it replied from our Solaxcloud, pls?

Does it say succeed when you send instruction, pls?_

mjhemworth

Could you please provide me with the information Solax are requesting?

mjhemworth

I am glad to say that after changing to min SoC=10%, and having tested it for a couple of days, it is now working.

Conclusion

Firmware needs to be up-to-date
min SoC needs to be at 10%

Thanks for your help

« Previous Page