Looking at the log I see that Peter's was stuck "on" from the 16th until this morning, while Jimbo's was stuck from 2/18-2/20. The coincidence makes me think that maybe something was just up with Entune during this time, but I'll dig into the way RavCharge determines whether the climate's on or off to see if there's a way I can pull in data from some other fields to get a more intelligent assessment of whether the climate's actually on. Thanks for letting me know! I almost never use remote climate so if something funny's going on with Entune it's unlikely I'd notice it myself.
By the way, even if RavCharge reports "success" right away, it still will have sent the command to the Entune server (equivalent to pushing the start climate button in the Entune app - which I just checked and saw hasn't changed since April 2014) - the only difference is it won't keep "pushing the button" automatically every 2 minutes (up to 5 times) if it doesn't detect that the climate started.
So it's quite possible that you might've gotten the false "success" from RavCharge and then went into the Entune app to try again, only to have the command that's already in the system from RavCharge eventually click on, giving you the mistaken impression that it was Entune that "fixed" it.
RavCharge.com | 2012 Classic Silver | 2018 Model 3 LR | Clipper Creek CS-60 | 40 amp openEVSE | 3.84kw PV