It would help me out if you could send me some information to help me fix this. If you're willing, go to the Overview Tab and press the Details button. Copy the text from the window that pops up and send it to me at joe AT visibletesla DOT com.
Feel free to edit out your VIN and the UID's at the very end. Be sure to include the line that begins with "Low level information"
Thanks,
Joe
Email with the details has been sent. Very glad to hear that you're still working on fixing things. For some reason I mistakenly thought that you were finished updating VT for the time-being.
I'll actually describe something else going on that may be of interest to you. Or perhaps there's a simple explanation that I'm missing, since I am new to VT.
I've been playing around a bit with the geofencing notifications. I'm noticing that the notifications are usually being sent 10-15 minutes after the condition is being met. At first I thought it could just be delays in the emailing system, so I customized the messages with the {{TIME}} function, so the messages now arrive with the timestamp of when they were generated. And they are being generated late some of the time, but not all of the time.
I understand that some notifications and actions can take place with a delay, if the car has been sleeping. But I don't think this could be an issue related to the car sleeping because some of the time when the notifications have been sent with a delay, the car has been awake for quite some time. As an example, this morning my wife preheated the car, using the iPhone app for about 15-20 minutes, before leaving for work. Yet the geofenced notification came with a time-stamp 15 or 20 minutes after she had actually left for work.
This isn't a big deal. I just thought I'd let you know about it to see if you or someone else might be able to enlighten me as to what might be going on.
Interestingly, other notifications not involving a geofenced area seem to be coming when they should be. I set an unplugged notification for 9:55 PM, and left the car unplugged, to test it. I received that notification right at 9:55 PM.
Thanks!
Edit: I went and re-read the part of the manual that deals with sleep mode. I'm now wondering if the following could be coming into play:
- Even while the app is sleeping, it checks the car periodically to see if it is awake. This check will not wake up a sleeping car. If it is awake, VisibleTesla will collect some data but then remember not to bother the car again for 30 minutes. That's enough time for it to go to sleep if it wants. If, after collecting this data, the app notices that not only is the car awake, but it is moving or charging, it won't wait another 30 minutes to check back in. It will continue to speak to the car regularly until motion or charging stop.
Edit Number 2: The more I think about this, the more I think my issue was tied to the bullet point above. I have now scheduled VT to enter and exit sleep mode, such that it should be in "always awake" mode whenever the car can't be sleeping anyway. Assuming I have done this correctly, I'm guessing this will resolve the issue I was seeing.
Is it safe to assume that the scheduler commands of "Sleep" and "Awake" override the menu option inactivity mode commands when they trigger? So I should leave the menu option inactivity mode set to "Allow Sleeping" and my scheduled "Awake" command will then override the menu option inactivity mode setting when it triggers, and then the "Sleep" command will put VT back into sleep mode when it triggers?
Thanks!
Edit Number 3: If the answer to my question, "Is it safe to assume..." above is "yes", then am I also correct that the scheduler times won't operate unless that time is reached? In other words, my setting all this up today, and quitting and restarting the app, did not actually take the app out of sleep mode, because I have it set to switch to awake mode at 4:55 AM, and I set all this up well after that, so the app never saw 4:55 AM, so never switched modes. In other words, the app does not check what mode it is supposed to be in, based on the time, when it starts. Is this right?
If all of my assumptions above are correct, then VT is probably functioning for me as it should be, though I'm not certain of that yet, as I missed geofenced notifications and trip-recording this afternoon too. I think these were missed because of the 30 minute issue with VT not checking the car, in case the car wanted to go to sleep. However, if my having scheduled the awake time, and restarted VT should have put VT into awake mode, then something else is going on.