miimura said:
I decided to follow this idea. I set my car's timer for Sunday 5pm departure only. I set RavCharge to start at 1:10am every day. The car put up a warning that it's not set to charge every day. We'll see how it goes.
I'm flattered by your faith in RavCharge, but I wouldn't really advise this. If you just leave the car's timer set for every day, but with a time sufficiently late as to ensure it won't kick in before you want even if you're charging from 0%, then you'd get the same result. But you'd have the added redundancy of the car's timer kicking in (most of the time) even if the RavCharge or Entune servers go down, or if your car's not getting a cell signal, or whatever else.
EDIT: Another reason I'd advise against this approach is that some days you might stay out late and come home and plug in after RavCharge's start time. In that case you'd have to remember to choose "Charge immediately" when you turn off your car, or else you'll wake up empty. If you left the car's timer on, you should still get a charge, even if it starts later than you want. This scenario is the reason for my 20 minute later backup charge attempt, but of course that can only do so much.
miimura said:
BTW, what does RavCharge do when it's time for a timer event and the car is not plugged in? Does it know that and skip the event? I'm just wondering about the extraneous Entune e-mails mentioned above.
I addressed that question
here. Unlike the car's built-in timer, the information that RavCharge has about whether the car is plugged in is only as good as the last update. I could set RavCharge to do a status update some time before a scheduled charge, but then there'd be some risk of the car getting plugged in between the status update and the timer event, or the status update not completing and a charge being skipped because of incorrect information about plug status.
Since my #1 goal is 100% activation of scheduled charges, for now RavCharge just goes ahead and sends the command (and sends it a lot), regardless of what information it has about the car being plugged in or not. So you probably would get a number of nuisance emails from Entune if you didn't plug in and had a timer set. If you want to avoid this you could just go to RavCharge on your phone and turn the timer off for the day. Changing the timer settings via RavCharge is much less painful than having to go out to your car and deal with its terrible interface.
Now that I think about this last part, maybe a cool feature would be a "skip the next charge" button that turns the timer off for a night but then automatically turns it back on so you don't have to remember to...
EDIT: Now that I think about this some more, maybe the risk isn't really that high, and it'd be nice to avoid hammering Entune with charge start requests when people are intentionally unplugged (not to mention avoiding all those "charge failure" emails). I'm working on implementing a "Plug check" option for the charge timers now.
If you choose this option, RavCharge will do a status update immediately before sending a charge start command. If the update fails, it'll go ahead and try to start charging anyway. If the update succeeds, it'll only send the charge start command if it has confirmed that you're plugged in and not already charging. Due to the time required for a status update to go through, charges will probably start a few minutes after the time you specify if you select this option. I'll test it on my car tonight and probably make it live tomorrow.