Repeated Notifications on Companion App

[nickjossy]

I'm getting repeated notifications on all my devices with the Companion App installed on:

Predbat: Joined Octopus saving event Tue 07/10............

I don't sign up to these and i've not configured the relevant sensors in Predbat:

Octopus saving session points to the saving session Sensor in the Octopus plugin, when enabled saving sessions will be at the assumed

Rate is read automatically from the add-in and converted to pence using the conversion rate below (default is 8)

#octopus_saving_session: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_saving_session(s|))'
#octopus_saving_session_octopoints_per_penny: 8

[gcoan]

Curious.

Can you please supply your full logfile and debug or apps.yaml

What version of predbat?

[nickjossy]

Seems to be trying to join the savings session for some reason. It's running in read-only mode as well.

2025-10-07 16:10:38.536227: Warn: Octopus API: Errors in request (https://api.octopus.energy/v1/graphql/): [{'message': 'Account ineligible to join Saving Sessions event.', 'locations': [{'line': 2, 'column': 2}], 'path': ['joinSavingSessionsEvent'], 'extensions': {'errorType': 'VALIDATION', 'errorCode': 'KT-GB-5117', 'errorDescription': 'Account does not meet all criteria required to join Saving Sessions event.', 'reason': 'Account must join the Saving Sessions campaign to take part in the event.'}}]
2025-10-07 16:15:01.496596: Warn: Octopus API direct tariff gas not available, using zero
2025-10-07 16:15:07.125824: Info: record_status Read-Only
2025-10-07 16:15:39.696880: Warn: Octopus API: Errors in request (https://api.octopus.energy/v1/graphql/): [{'message': 'Account ineligible to join Saving Sessions event.', 'locations': [{'line': 2, 'column': 2}], 'path': ['joinSavingSessionsEvent'], 'extensions': {'errorType': 'VALIDATION', 'errorCode': 'KT-GB-5117', 'errorDescription': 'Account does not meet all criteria required to join Saving Sessions event.', 'reason': 'Account must join the Saving Sessions campaign to take part in the event.'}}]
2025-10-07 16:20:01.169789: Warn: Octopus API direct tariff gas not available, using zero
2025-10-07 16:20:24.830166: Info: record_status Read-Only
2025-10-07 16:20:42.453357: Warn: Octopus API: Errors in request (https://api.octopus.energy/v1/graphql/): [{'message': 'Account ineligible to join Saving Sessions event.', 'locations': [{'line': 2, 'column': 2}], 'path': ['joinSavingSessionsEvent'], 'extensions': {'errorType': 'VALIDATION', 'errorCode': 'KT-GB-5117', 'errorDescription': 'Account does not meet all criteria required to join Saving Sessions event.', 'reason': 'Account must join the Saving Sessions campaign to take part in the event.'}}]

apps.txt

[gcoan]

Looking at your apps.yaml, two things:

1. some of your YAML isn't formatted correctly, sub items must be indented two spaces,

e.g.

  export_limit:
   - 7000

possibly won't work

2. you are using the Octopus direct integration method from predbat

per the documentation https://springfall2008.github.io/batpred/energy-rates/#octopus-energy-direct

it will auto enrol you in the saving session

the auto enrol then fails because you have not joined the Octopus Octopoints scheme.

Predbat then retries this.

If you join the Octopoints scheme these notifications and errors should stop.

The fact that you are in Monitor mode doesn't really make a difference, predbat is not controlling your inverter, it's joining you in the saving session. Whether you actually save electricity or export or do nothing is then a separate thing. Joining you to the saving session if you then don't participate won't penalise you

[nickjossy]

Thanks for highlight the YAML formatting. I'll check it all out.

The documentations says "Saving sessions are also supported, including auto-enrol." I didn't read this as saying it will always auto-enrol. After all, Octopus don't auto-enrol everybody. I've opted in now, but will have to wait till the next session to know if that solves the problem. The notifications were saying that "Predbat: Joined Octopus Saving Session....", when it didn't really as the call failed. So ideally it should only put out that message if it successfully joined.

I would also argue that read-only means don't change anything on my behalf. It was the switch.predbat_set_read_only that I've set and not the Predbat Mode.

[gcoan]

I've updated the documentation to make it clearer that as part of the Octopus Direct integration Predbat will auto enrol you to the saving sessions and you must have joined Octoplus beforehand.

I agree the error handling on the failure to enrol to the saving session shouldn't have sent the 'you have enrolled message', that is a bug, although a fairly edge case for most people.

The read-only switch, could be argued either way. I see your point, but conversely the documentation for read-only talks about not making changes to the inverter settings https://springfall2008.github.io/batpred/customisation/#predbat-mode and enrolling to a saving session isn't an inverter change. Again for most people a fairly edge case.

Thanks for raising, suggest we leave this open so these points are noted and on the backlog

[AlexCPU]

I saw this too (just installed predbat recently), what I did notice, was that whilst I've signed up for octopoints, and joined saving sessions from previous years, I hadn't signed up to this years program. I got the notifications every 5 minutes, as soon as I logged in to Octopus and actually signed up, they stopped on the next re-plan.

So from a documentation point of view, you need to be signed up to Octopoints AND Saving Sessions.

[gcoan]

So from a documentation point of view, you need to be signed up to Octopoints AND Saving Sessions.

thanks I will make that point in the documentation