-
Notifications
You must be signed in to change notification settings - Fork 20
Description
I’ve noticed that a switch will be triggered even if the savings are very small (like yesterday the difference was only 3p). Sometimes this will actually result in more expense as the hour between 11pm and midnight is likely to be more expensive on the go tariff than agile for example.
Switching from agile to go for the subsequent day also makes it harder to automate higher usage during the cheaper periods, in the event that a switch back to agile happens (as it often does).
I appreciate that’s quite a hard problem to solve but I’d like a threshold to be added as an option, where you could specify the savings needed in order to trigger a switch. I’d probably set it to 20p or something and that would prevent unnecessary switches taking place.
What do you think?