Backup SOC Write failed
So I may start slow I have series of questions, but this one I can't seem to find a good answer for.

I am getting a write failed error when trying to change some of the quick settings. Same in IOS App and Webclient
writefailed.png
So my reading states most of the time that is a poor wifi connection to the datalogger. But the wifi router is very close (less than 10m) and this is the state of the datalogger in the web client
datalogger.png
Green, 3 out of 4 bars and saving mode schedules and other tasks does not fail.

What am I doing wrong?
Thanks in advance - be gentle
K
Re: Backup SOC Write failed
Is the mode scheduler active? If so, then some of the settings cannot be changed, and you get a very misleading error message.

Will did a video a day or two ago on youtube (channel name iameccles) showing how to temporarily turn off the mode scheduler without having to delete the slots.
Re: Backup SOC Write failed
Will give that a try. I saw the video on pausing, I haven't watched. Its not obvious that mode scheduler can't be on while you make changes.

TY.
Re: Backup SOC Write failed
So I tried that.
Moved the Work Mode to Self Use.

I can't write for Backup SOC %
But I could write for Import from grid W

So I got half of the job done.

Separate question. I have been bouncing between the web interface and the IOS app, and they don't seem to be 'well sync'd' which is weird. ie I could see a mode schedule on the web interface, but not on my IOS app

Should I just be using one? Why wouldn't the two by pulling from the same dataset?
Re: Backup SOC Write failed
Hi,

It's worth having a look at the mobile App help forum, especially about the new update.

Personally I was having a similar thing with not being able to change the reserve SOC away from 80%, which I think was an old value in my APP variables from before the update.

I could dropped out of a schedule, change it to 10%, but as soon as I enabled a schedule in the APP, the reserve SOC went back to 80%. This doesn't happen on the desktop (for me).

I've deleted the APP and gone over to just the desktop for now.

Regards.
Re: Backup SOC Write failed
Wraith wrote: Tue Feb 10, 2026 4:21 am Separate question. I have been bouncing between the web interface and the IOS app, and they don't seem to be 'well sync'd' which is weird. ie I could see a mode schedule on the web interface, but not on my IOS app

Should I just be using one? Why wouldn't the two by pulling from the same dataset?
A long time ago, my system was going loopy. It turns out, me using the Android version and my son the Apple version of Fox Cloud 2.0 App, were having a fight.

I would set a schedule, saved and working... my son would open the app, and settings were getting scrambled... values would charge, or worse it was changing work modes into Force Charge during peak.

So for now at least, use one system, and try in a few weeks the other to check.
Re: Backup SOC Write failed
my son would open the app, and settings were getting scrambled...
I don't know how relevant it is, but there is a 'multi-device' setting in the user options on the app, off by default, which I think prevents two devices simultaneously trying to change settings. Not sure though.
Re: Backup SOC Write failed
WyndStryke wrote: Tue Feb 10, 2026 10:33 am
my son would open the app, and settings were getting scrambled...
I don't know how relevant it is, but there is a 'multi-device' setting in the user options on the app, off by default, which I think prevents two devices simultaneously trying to change settings. Not sure though.
Yeah know that setting, though this wasn't used at the time by me and my son.
It could 100% help others for sure, I now use Home Assistant for controls, so only use the App for viewing.

I did wait a month for Apple and Android version to update a few months back, and upon testing this was working again fine for us both (prior to the HA integration) So it could be wait a month and test, or set the multi-device setting as you recommend.
Re: Backup SOC Write failed
WyndStryke wrote: Tue Feb 10, 2026 10:33 am
my son would open the app, and settings were getting scrambled...
I don't know how relevant it is, but there is a 'multi-device' setting in the user options on the app, off by default, which I think prevents two devices simultaneously trying to change settings. Not sure though.
This is definitely on. ie if I have the app logged in and I go to the web interface, it logs the app out. So its not the two doing things at the same time, they are genuinely not aligned in terms of capability.

So for now, I've stuck with the mobile app, as it seems to be more consistent, but has a few less options, which I hope will eventually show up.

Still get write failed in certain screens, so for now I'll pause and try again at a later date.
Re: Backup SOC Write failed
Unfortunately the labels are reversed on the new app, Backup SoC is actually System minSoC and vice versa, if you want to change the (what was Backup Reserve) for now change the System MinSoC setting.
Post Reply