- General
-
Questions
SMS 'tesla did not go to sleep' followed by 'tesla has gone to sleep'
So after resetting my tesla password etc, I finally get the car to sleep :-)
However what is strange is that I always get the following sequence of text messages (example time stamp in the front)
- 8:14am 'Tesla trying to sleep. To resume polling replay to this test with "yes"'
- 8:29am 'Tesla did not go to sleep. Polling has been resumed'
- 8:30am 'Tesla has gone to sleep'
this matches with what I see in the raw data: (shortened)
|
4/10/2019 8:32:14 AM |
asleep |
|
|
04/10/2019 8:31:13 AM |
asleep |
|
|
04/10/2019 8:30:19 AM |
asleep |
Idling->Sleeping - Text Alert Sent |
|
04/10/2019 8:29:16 AM |
online |
Vehicle Did Not Fall Asleep - Text Alert Sent |
|
04/10/2019 8:28:17 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:27:17 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:26:17 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:25:18 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:24:17 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:23:16 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:22:13 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:21:15 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:20:16 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:19:17 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:18:11 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:17:12 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:16:10 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:15:12 AM |
online |
Trying To Sleep - No Vehicle State |
|
04/10/2019 8:14:13 AM |
online |
TeslaFi Sleep Mode Sleep Attempt - Text |
So is it normal that it first tell me it couldn't go to sleep and then it tells me it did?
Also, by looking the the raw data, I can assume it is sleeping - right?
Customer support service by UserEcho
Same thing is happening for me.