Problem:
Configure predbat to handle Axle events and saving sessions.
Axle publish an event. Octopus then publish a saving session event which overlaps the Axle event.
Regardless of issues around terms and conditions this could actually cause a problem if Octopus and Axle both claim money for the same thing.
Currently there's no way to opt out of saving sessions (you have to opt-in). However we can opt-out of the Axle event.
Proposed solution:
Assuming that Axle publishes events before Octopus publishes saving sessions (which is what seems to happen),
In the event there are overlapping Axle and saving session events, don't auto opt-in to the saving session.
If Axle provide an API to opt-in/out in future use that appropriately.
Current solution:
Disable saving sessions completely (comment out line).
Problem:
Configure predbat to handle Axle events and saving sessions.
Axle publish an event. Octopus then publish a saving session event which overlaps the Axle event.
Regardless of issues around terms and conditions this could actually cause a problem if Octopus and Axle both claim money for the same thing.
Currently there's no way to opt out of saving sessions (you have to opt-in). However we can opt-out of the Axle event.
Proposed solution:
Assuming that Axle publishes events before Octopus publishes saving sessions (which is what seems to happen),
In the event there are overlapping Axle and saving session events, don't auto opt-in to the saving session.
If Axle provide an API to opt-in/out in future use that appropriately.
Current solution:
Disable saving sessions completely (comment out line).