My solar system has degenerated into a complete farce - six or more breaker trips a day, unreliable export which stops for no apparent reason and virtually zero alarms on the system. I am slowly concluding that either last software updates to the latest build are a complete POS, or I have major hardware faults. The system is only six months old and worked flawlessly until a couple of weeks ago.
I am addressing the failure with the installer so rather than go through the whole sorry situation here, the only thing I would like a view on is why I can no longer schedule import from Octopus overnight. Nothing has changed on the App settings but I get a 'write error' if I try and load the schedule (again for the nth time). On the web portal I get a 44098 Write Error message so now the system can no longer be forced to import. Its a POS.
For whatever reason, the system no longer seems to have a functioning operating system as the inverter stops working without any alarms and wont handle PV or battery inputs. it just sits there like a dumb rock, until a complete and total shutdown/restart
Does Fox kit do this regularly or am I just unlucky ?
Something very wrong there, it sounds like your inverter has either a hardware issue or the firmware is mis-matched, can you post what your Master, Slave, ARM(Manager) versions are ? and i’ll check the latest firmware.
44098 usually happens when the comms is flaky to the datalogger or the manager has crashed (which sounds probable if you are having to restart a lot)
If you have been using the Fox Agile integration where you enter your Octopus API on the Fox cloud etc... that has been known to fight against any settings you make - if you have used that delete your octopus api key from their cloud to eliminate it.
44098 usually happens when the comms is flaky to the datalogger or the manager has crashed (which sounds probable if you are having to restart a lot)
If you have been using the Fox Agile integration where you enter your Octopus API on the Fox cloud etc... that has been known to fight against any settings you make - if you have used that delete your octopus api key from their cloud to eliminate it.
Software updates - Master and ARM now the most recent versions after a previous posting, and assistance from folks here
Slave however is at 1.02
"If you have been using the Fox Agile integration" - I have not. Just the App recharge timer and Mode Scheduler setup that hadnt been changed in any way for months.
My installer (good chap) had a look at the system even though its a Bank Holiday weekend and couldnt figure anything obvious out but we did find out by luck that when he remotely tried to set the charge times, the breaker literally tripped as soon as he tried to set it, and got the error.
It certainly seems like a hardware fault exacerbated by the latest system updates as its been a POS since the system was updated.
Slave however is at 1.02
"If you have been using the Fox Agile integration" - I have not. Just the App recharge timer and Mode Scheduler setup that hadnt been changed in any way for months.
My installer (good chap) had a look at the system even though its a Bank Holiday weekend and couldnt figure anything obvious out but we did find out by luck that when he remotely tried to set the charge times, the breaker literally tripped as soon as he tried to set it, and got the error.
It certainly seems like a hardware fault exacerbated by the latest system updates as its been a POS since the system was updated.
I'm experiencing something similar or the same - just posted here:
Same text:
Same text:
Interestingly, it seems if i reboot the inverter the issue goes away partially - I can set ForceDischarge and ForceCharge via app again. Until I try via the API again - then it stops working both in app and via API?I've been using Force Charge and Force Discharge for the past few weeks - configured via the app - with no issues. Tweaking as needed to manage my battery level.
Today I was working on having these changed via an API call (via homeassistant) and couldn't get the commands to work - consistently getting error 44098 write failure
I did manage to get entries with workmode SelfUse and FeedIn to save but not ForceCharge or ForceDischarge.
But now, I can't even manage to re-configure them in the app as I have been doing for weeks - same "write failure" error.
Anyone else experienced similar or know how to troubleshoot/resolve?
Inverter: KH10 version 1.41. Have been on this version for a while
Update - My issue was using "v0" of the API instead of "v1", which seemed to get things in to a broken state. My issue seems to be resolved now.
Glad you’ve fixed it, looks like Tony nailed it ! - the v0 calls have now been deprecated by Fox in favour of the v1 for setting schedules and getting real time data.