Inverter ignoring the charge up to limit

I have a gen 2 hybrid inverter and a 9.5 kw battery. Since updating the firmware to D0.909-A0.909 the invertor ignores the charge up to limit and uses the grid to try and charge up to 100%
Has anybody else noticed this behaviour?

Do you have any settings in the web portal.
I found app and portal sometimes conflicted and did funny things.
I disabled controls on the app and only use it for monitoring when out.

Finally after trying GE portal, Octo R&D, I went to Home Assistant as it sits on home network and not subject to vagaries of GE severs, Octo servers and the internet and can pretty much setup whatever you want it to do.

Thanks for replying Steve. The settings are confirmed in the web portal. I recently changed the timing to a single hour as it originally was set over the Octopus cheap period from 11.30 to 5.30. The invertor ignored the 33% charge limit and charged the battery to 100% then did not allow it to discharge to cover the home requirements. I did not have this problem before the latest firmware upgrade.

Not noticed that, but after every firmware update I've done recently, it's ignored my charge rate.

Changing the value slightly and saving it always corrects that behaviour.

I think a reset to defaults can be a good idea after a firmware update, then re-set any details such as timed charge etc.

TX200
Thanks, I will give that a try and see what happens tonight

After reading the register on the web portal inverter settings it confirmed that the charge up to limit had been turned off - even though both the app and the dashboard were reporting it as turned on!
Why is the Givenergy control software so difficult and counter intuitive to use effectively?
Thanks for everyone’s input

DJB because one team built the web portal and a different team built the app I hear. Hence different naming conventions across both.

Oh and the settings get stored in different registers in the inverter as and when firmware updates arrive and bring new features/retire other features.

Hopefully with Paul on board, test quality will improve!

As for design differences like naming conventions, guess someone higher up needs to get the two teams to agree!