Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cheapest time slots but within certain hours #64

Open
richsimpson opened this issue Mar 10, 2021 · 1 comment
Open

Cheapest time slots but within certain hours #64

richsimpson opened this issue Mar 10, 2021 · 1 comment

Comments

@richsimpson
Copy link

Really like this, been using for a while for car charging electric vehicle. Wanted to do a best time slot for other items but not sure how or if possible.

Eg Tumble Dryer with run time of 2 hours, the cheapest slot between 8am or current time and 9pm. Tried adding a run before and run after but keep getting told to turn it on at 03.30 am, Mrs S wouldn't be impressed with that and don't want it to automate and be running when not around as a bit dangerous.

Any thoughts Mark?

@d1964b
Copy link

d1964b commented Mar 11, 2021

Hard to say what might be wrong without seeing the relevant section from your configuration.yaml file.

Having said that if the run_devices option isn't doing it for you , then you might consider a different integration like octoblock by badguy99. It's great at giving you a cheap timeslot when that time window has to be contiguous - such as might be used by a tumble dryer. I used to use it but switched to octopusagile because I was happy to have my active time slots fragmented across a time window. No reason why you can't use both integrations and choose what works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants