-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Calculate Charging Start and End #294
Comments
@jonasbkarlsson: Thanks in advance |
Are you using the easee chargers? If so I am using basic schedule and set that to the charger. That means if the car gets connected after the start hour it will still start charging. The start / stop is then handled by easee. And then I have an override automation for the manual buttons. |
@adegenkolbe, I have a plan to eventually change the time resolution to 15 minutes, instead of 60 minutes, but it will not happen soon. The basic scheduling is done by
|
Using 15 min intervals would be great even without the 15 min resolution in spot prices. Today the needed charge to reach my target SOC requires just over two hours. Since a third hour is required, the third cheapest hour is scheduled correctly. The problem is that the cheapest hour is also the last of the scheduled ones, and will not be fully utilized. A very minor inconvenience, but shorter scheduling intervals could help mitigate the problem. |
Hi,
first of all thanks for the great work.
Would it be possible to set the Start and End for charging more precisely?
At the moment the calculated start and end is the full hour. But when let’s say, i plug in the car at 11.30 and charging starts immediately because it is the cheapest hour, the start time is set to 11:00. It would be nicer to have the start time to now. Also the end time is set to the last hour in which charging will take place. This could also be calculate by the percentage charged per hour to have a more or less minute precise end time.
This would be great,because my wife is always interested in when the car is fully charhed😊
BR
Andy
The text was updated successfully, but these errors were encountered: