Axle grid event fight between Predbat and Cloud API over export SoC causing unnecessary writes to unsafe registers

[chibbert]

predbat_debug.yaml.txt

Describe the bug
There was an Axle grid event today 05/05/2026 from 07:30:00 - 08:30:00 today in my area.

I have predbat set up with the axle API.

Predbat and Axle had a little fight over the SoC and export end times during the event, warnings and errors also appeared in the predbat logs, and unsafe writes were made for the Export SoC due to predbat wanting 4% and Axle wanting 10%.

I only noticed as I've recently set up a notification for unsafe writes and I noticed they were increasing during the event (as defined here: https://github.com/britkat1980/giv_tcp/blob/b6a3ba85c5d81f0acaad0e574fccb902aa23b03c/GivTCP/GivLUT.py#L268 and https://github.com/britkat1980/giv_tcp/blob/b6a3ba85c5d81f0acaad0e574fccb902aa23b03c/GivTCP/givenergy_modbus_async/client/commands.py#L28)

The Discharge Slot 1 SoC is defined as an unsafe write according to the GivTCP code.

Timeline:
07:24:34 Axle set export slot 1 up via Givenergy cloud API to: 07:30 - 08:30 discharge to 10%
07:30:15 Predbat set export slot up via GivTP to: 07:30 - 08:31 discharge to 4%
07:44:18 Axle set export slot 1 up via Givenergy cloud API to: 07:30 - 08:30 discharge to 10%
07:45:24 Predbat set export slot up via GivTP to: 07:30 - 08:31 discharge to 4%
07:53:55 Axle set export slot 1 up via Givenergy cloud API to: 07:30 - 08:30 discharge to 10%
07:55:25 Predbat set export slot up via GivTP to: 07:30 - 08:31 discharge to 4%
08:04:37 Axle set export slot 1 up via Givenergy cloud API to: 07:30 - 08:30 discharge to 10%
08:05:25 Predbat set export slot up via GivTP to: 07:30 - 08:31 discharge to 4%

Expected behaviour
For predbat to not fight with the settings that axle is using, but would still like to have predbat as backup in case Axle fails to call Givenergy Cloud API. Perhaps predbat could determine

apps.yaml.txt

Predbat version

xxxx

Environment details

Predbat: v8.37.5

• Inverter and battery setup
  Givenergy Hybrid Gen3 5kW

• Standard HAOS installer or Docker
  Docker

• Anything else?

Screenshots

Logs showed errors:

Plan history showing predbat detected the axle event sucessfully:

Config all defaults apart from:

apps.yaml attached

Log file
Can you capture a log file from the time of the issue, debug mode is not normally required.

You can download the logfile from the WebUI on the Dash tab select predbat.log

Predbat debug yaml file
This is important for any plan related issues.

Once you have captured the issue go to the Web UI, in the Dash tab click on predbat_debug.yaml and wait 30 seconds for it to download. Select 'keep' if your Web Browser thinks the file is dangerous.

Rename the download file to predbat_debug.yaml.txt and upload it to GitHub. This will allow your plan to be reproduced and also stores all your settings for review.

[gcoan]

The cause of this is that Predbat and Axle have different ideas about what the forced export should be and so every time Predbat writes and Axle checks (about every 10 minutes), Axle changes the entries and then Predbat changes them back again.

The actual number of additional register writes this causes is absolutely tiny, nothing to worry about.

If you want Predbat to relinquish control to Axle during the event, set axle_control to true in apps.yaml https://springfall2008.github.io/batpred/components/#axle-energy-vpp-axle

The set export target errors are a separate matter. They're your inverter rejecting the command from Predbat. Sometimes it happens, you've had a few, but then 5 minutes later when Predbat next runs it has successfully set the export target.