That issue isn't specific to the app, it is more to do with keeping an API system that is accessible as it is used by lots of third party "apps" such as VisibleTesla, Eve, EVMote, Teslalog, Remote S, etc
If you have not, ensure you have Remote S installed in the Apple Watch dock, as up to 10 apps installed there operate much faster. As you say, Remote S works even better as a result of the watchOS 3 update, but I suspect we're always going to have a bit of a delay given MS still has to be communicated to (watch->phone->Tesla and back
). Allen's upthread post 9 days ago said the next iteration would be optimized for watchOS 3, so I suspect it's just a matter of time until he gets it done and through Apple's approval process.
I think that's a great idea for an enhancement... even bettter in the short space, perhaps display three things next to one another: Locked/Unlocked Icon -- Plugged-in or Not Icon -- Charge%
Didn't know that this was what people wanted, but yes, I could display that somewhere. Not exactly sure where, though. The screen is already really packed with data displays. Perhaps, I could introduce a data dump where you can press a button to email the entire Tesla log to yourself for record keeping or debugging or firmware checking etc.
I would ask one of the people who hacked the Center Console about this. They have more information about this subject matter than I do.
A release for Watch OS 3 is not a matter of "if", but "when". The next update to Remote S will be for Watch OS 3. There were several delays to development: 1) My car accident took 2+ months for me to get my car back (I got my car back three weeks ago, but I've also been out of town since two weeks ago, so I don't have access to my car again). 2) I was waiting for Watch OS 3 and iOS 10 to come out. 3) It's going to take some time for porting from Watch OS 1 to 3 and doing testing.
Priority is to port Watch OS 1 to OS 3 first and fix Homelink/Summon. And then I can work on additional features from there. Watch complication was a common request, so I'll give it a try and see if it makes sense to add it (i.e. the information isn't too outdated to be sensible to display on the complication.)
Yes, Remote S only updates the app when it's in the foreground because apps can't run in the background. But if you enable Background App Refresh for the app, it can possibly update the app whenever Apple thinks that you might want it to update (i.e. it updates based on how frequently and when you open Remote S in the past). Remote S also currently shares information between the iPhone and Watch so that if one updates, the other gets updated as well.
I've got 'EV Watch' installed since it does provide a complication showing charge %.
And the information doesn't get outdated if you don't open the app for a while?
I would hope not, as every time I turn my wrist and my watch face displays -- dozens or a hundred or more times per day, my watch would talk to my iPhone to Tesla to my MS and back. For me, that's too much battery usage at multiple points. What other complications seem to do, is update at some regular schedule in the background (that I don't quite understand), so they can be out of sync perhaps slightly (like temperature, my calendar and reminders, etc) by a few seconds, but catch up fairy quickly if I'm staring at my watch long enough. If I want complete info, I touch the complication and the whole app (like Remote S) appears on my watch face... and if I have the app installed in the dock (new feature in watchOS 3), it is more likely to be current and displays faster when I do decide to pull it up.
NVM figured it out, had to log out on my iPhone and log back in and change the option on the login screen to enable this feature on my watch
IIRC from previous discussions upthread, the net is these sort of things require a server-based solution that stays in more continuous contact with your vehicle, not the essentially standalone implementations we have running on our iPhone and Apple Watch today which come alive when you use them. I'll let Allen provide the detail again when he checks in here. Some of the continuous monitor tools others use may offer ways to accomplish what you're looking for.
The other thing this would be useful for is seeing what version you have after an update. It seems to me that the updates come down overnight. My usual process is to drive to work and then kick off the update once I am at work. But I don't know what version I got unless I take the time to go to my car and it might be nice to know if you get a major update, like 8.0, rather than a minor bug fix only update. When my car gets 8.0 I may want to go down to check it out.
