The model 3 goes to sleep (and wakes up to charge) just fine when connected to the tesla wall connector (and did during that time as well).
Yes, but what I am saying is that it's not the HPWC that decided not to charge in that scenario, but the car (presumably because you have a charge timer set). Yes, if you tell the car to wake up at 1:30am to start charging, it will wake up at 1:30am to start charging, and it will do this properly with any 3rd party EVSE as well.
The thread you pointed to was referring to a case of the car going to sleep because the EVSE it was connected to was not allowing it to charge, so it just gave up and went to sleep. It did not know that at 1:30am the EVSE was suddenly going to allow it to charge. I do hope it's clear that these are two different things.
My point is, people with a third party wall connector experienced this issue, while people with tesla wall connectors did not
The reason HPWCs did not have this "issue" is because they don't have the functionality to spontaneously power up at a later time. As you went on to say, it's the smart feature of the JuiceBox that was tripping up the car, but even then it's not a protocol issue. J1772 does not provide a protocol whereby the EVSE commands the car to begin charging. The EVSE simply either puts a signal on the pilot line indicating how much power is available, or it doesn't (indicating that the charging station is down or un-powered). If the EVSE has a smart feature that "wakes up" charging station at a certain time, all it would do is present a square wave on the pilot line indicating it is ready to provide a charge (and the maximum charge rate). It's then up to the car to acknowledge and then request the EVSE power up and provide the charge. It doesn't really have anything to do with whether the car has the ability to do timed charging, it's all about whether the car is monitoring the J1772 pilot line so it can respond to it. In the case of the Model 3, apparently when the car goes to sleep, it doesn't bother monitoring that line so it doesn't wake up to initiate the charge.
I was just attempting to point out (to the OP) that third party wall connectors had some issues starting charges, and one of the ways that the manufacturers worked around that was to keep the car charging (which in this OPs case would skew time connected charging metrics).
Thats all I am saying.
Yes, I follow. But I don't think that's what's happening in Murray's case. I think he plugs the car in and it charges immediately, but at the conclusion of the charge instead of the car going back to
Vehicle Connected state, it goes back to
Ready to Charge/Charging state (which actually makes sense if it is still drawing power to run the cooling system, or charge the 12V battery or run additional systems).
If it IS the case of the Chargepoint unit doing the JuiceBox workaround thing, technically the car is still charging anyway (just slower), so technically Murray should count that time as active charging time anyway. Which is why I suggested that looking at the kWh consumed might be more meaningful than just looking at how many minutes the car was actively charging.
Either way, I think this too could be addressed with a Tesla software update that puts the car back into
Vehicle Connected state once it completely terminates drawing power from the EVSE. But I imagine this would be an extremely low priority, so I wouldn't hold my breath.