Add a minimum points per unit threshold to Saving Sessions Joiner blueprint

[iPeel]

Describe the feature

It seems the saving sessions events seems to be working again this year. Given some of the low offers of points per kWh it would be useful if users could set a minimum points per unit so that they only automatically join events that are worth it for them.

The blueprint is a really easy way of enabling session joining but the user cannot set a minimum points per unit they are prepared to accept to join an event. It would be great if the blueprint could optionally accept a minimum points per unit threshold so that events are only joined where the points offered per unit meets or exceeds this value.

Expected behaviour

Add a separate input variable to the blueprint that accepts an integer points per kwh, named something like "minimum_points_per_unit".

If a saving sessions event is announced where the octopoints_per_kwh attribute is lower than the set value then the event is ignored and the saving session is not opted in.

If the octopoints_per_kwh attribute is equal to or greater than the set value then the event is opted into.

If the variable is not set i.e. empty then the event is joined always regardless of the octopoints_per_kwh attribute value.

Use Case

Use case: User wants to only join events when ther octopints per unit is 400 points or more.

1. User imports the blueprint and sets the saving sessions event entity and sets the minimum_points_per_unit to 400.
2. Event is announced with an ocopoints per unit of 450 > session is joined. Event is announced with octopoints per unit of 300, session is NOT joined.

Use case: User wants to join events regardless of points per unit offered.

1. User imports the blueprint and sets the saving sessions event entity and leaves the minimum_points_per_unit blank.
2. 2. Event is announced with an ocopoints per unit of 450 > session is joined. Event is announced with octopoints per unit of 300, session is joined.

Confirmation

• By submitting this feature request, you agree that you have read the documentation and confirmed it does not already exist
• I am willing/able to help contribute to the solution of this feature

[gcoan]

Question whether this is really worthwhile adding as an enhancement. If you join a saving session and then don’t participate, there’s no side effect to this.

You could put the logic of whether to participate in the saving session (e.g. do a force export, turn appliances off) or not in your saving session automation as the number of points per kwh is in the event details.

[BottlecapDave]

Hello and thank you for raising this enhancement. I'm not sure when I'll get round to it, but as there's work arounds and no penalties for joining but not participating, it will probably be lower on my list.

In addition to what you've suggested, I think there should also be a secondary configurable set of actions for the not joined scenario. This is because, while this is a nice addition, I can see people raising issues that saving sessions weren't joined when they forgot they set a minimum points or didn't realise the session didn't meet the minimum points