KH7 Scheduler settings changing themselves

[MaterialBarracuda48]

Hello all,

I would just like to say that I have had a similar issue to user: aaronuu from their post viewtopic.php?t=2232 I have started a new thread as I didn't want to hijack their thread, and I also don't use Modbus myself.


I am using Octopus Go tariff, so it's usually a very simple program to schedule. Set a charge at 00:30 until 05:30, and I had it hold SoC at 100% during this time, after this it would be in Feedin mode until 23:59. It was working fine until the 22nd October (no changes made by me) I then noticed that around 17:00 it decided to charge the battery to 100%

The last few days it has been doing the same each day, it would randomly begin charging battery or otherwise getting screwed up scheduling. Yesterday I powered the system down fully, and restarted it.


As Octopus gave us a nice bonus 3hrs of free electric today (25th Oct) I set a new schedule up to take advantage of this session.

This is how I had set it the previous night (I had to recreate for screenshot)

I then checked this in the morning, to see that it had set every entry to force charge

After I had programmed it back to correct settings, upon checking it just over an hour later, it had charged battery back to 100% and modified values again

I have reached out to my installer to see if they can apply firmware updates, but they have not yet got back to me.
I can only assume this is being pushed from the cloud into my inverter and for reasons unknown to me, it is getting scrambled.

[Will]

Just to confirm you're not using the FOX API key with other automation platform like Energy stats or home assistant?

[MaterialBarracuda48]

Hi Will,

Thank you for replying.

The only API key I have used it the Octopus one, where I input this into Fox when I was on Agile tariff.
I don't recall ever making or seeing my Fox API key.

ETA: I have just logged into Fox to view my API key, it is blank... so I guess I never made one in the past.

[Will]

next thing is to double-check the inverters date/time is correct.

[MaterialBarracuda48]

Sorry for the delay,

The date and time are spot on.


Attached is screenshot from API screen, I presume this means I never have asked for one as it is not seen partially?

[MaterialBarracuda48]

Sunday 26th October update.

I had set the scheduler to Octopus Go tariff yesterday evening, and shortly after midnight I had to set the 00:30 - 05:29 Charge window again, as it had swapped to discharge.

When I woke up and checked scheduler again in the morning, it had set itself Force Discharge in slots 2 & 3 of the scheduler as seen here

I then decided to try and remove the schedules via the foxesscloud website to see if this could make a difference (as I usually set via phone app.) I am trying this way to see if there is some bug in the phone app (for me) or maybe it "sticks" better if I set via the cloud website.

It kind of worked, as when I first checked on the phone afterwards, it had set the 3x schedule entries, but with some odd settings. At first when I looked on the phone, it had all 3x schedules set with FD SOC as 20%, and FD Pwr as 100.0 W.
I corrected these values, to what I think should be correct, and have this now saved.

EDIT: I left the phone app for about 1hr, and when I checked, it had swapped the 00:30 - 05:29 Charge to Discharge again.


Firmwares currently loaded on KH7

Master : 1.39
Slave : 1.01
Manager : 1.40

Datalogger W6: 1.04

[MaterialBarracuda48]

I had a call today from the installer, they are going to install some firmware updates and see if this sorts out the messed up schedules.

I will update the post once this is done with new version numbers and hopefully it fixes it.

[MaterialBarracuda48]

Firmwares previously loaded on KH7

Master : 1.39
Slave : 1.01
Manager : 1.40

Datalogger W6: 1.04


Firmwares currently loaded on KH7

Master : 1.52
Slave : 1.01
Manager : 1.52

Datalogger W6: 1.04

[MaterialBarracuda48]

It was stable for a few hours today, I opened the scheduler several times and it was fine.
I checked it this evening whilst cooking, and it was pulling power from the grid, as it had swapped the 3rd schedule from feed-in to force charge.

Have to see what the installer/fox support have to say about this.

[MaterialBarracuda48]

I do have a possible very thin work in progress theory.

Me and my son both login to the Fox cloud app on our phone, and though he doesn't muck about with any settings, he likes to see data basically. Well the theory is that as he has an iPhone and he is also a small version bump ahead of my Android version. This version change might not actually cause the issue, but it could also be him just logging in is breaking settings.

It does feel far fetched, but I have changed the login password, just in case he forgets and checks. Overnight it kept all the settings, but if it is going to scramble the schedules, it would do this by this evening for sure.


Yes a very thin theory, but I will change a single variable and eliminate all possibilities no matter how far fetched.

[chubber]

Sorry if this has been suggested before but if schedules keep changing is it because the Octopus Agile API is messing things around. You mention that you have added this previously.

You may need to remove the Octopus API key to disable it completely

[MaterialBarracuda48]

Sorry if this has been suggested before but if schedules keep changing is it because the Octopus Agile API is messing things around. You mention that you have added this previously.

You may need to remove the Octopus API key to disable it completely

Many thanks for you reply,

It won't let you remove the Octopus key sadly, if you erase the values it then checks the blank entries and moans it is not within parameters (or some such wording) so the API key remains. I could regenerate the key on the Octopus side and that should sort it that way.

Currently I am trying one change at a time, so that will be task for tomorrow.


So far, touch wood the scheduler has remained intact, but if it bugs out, it is usually later in the evening.


Also on a background information, I joined Octopus Go on the 10th October, the scheduler was perfect when it ran on the 11th. It broke around 17:00 on the 22nd, when it began a charging session. The Apple version of Fox Cloud had an update on the 19th, but it may not have been upgraded on my son's phone until 22nd perhaps.

If it is a red herring, it shall be coated in flour and fried up later for sure.