Background update interval....

[GeeRee1]

New to the app, which seems fantastic!! Running watch iOS 6.2...with a MS, M3 and MY loaded. For each of the cars, the “background interval” seems to revert to 1 hr, no matter what its set to. Trying to increase the wake interval but seems always to be a “1 hr”. What am i doing wrong? I have Background Updates “on” and Allow Wake in background “off”.

Thanks

[Kemmey]

hey,

That's interesting - there was a bug in the 1.0.2 betas that the configured interval was not persisted properly, but it's not something that I've heard of since.

Could you verify a few things to get closer to the issue?

Try setting the interval to a different value than 1hr, then force quit the app by holding in the wide side button until you get the three sliders - then hold in the crown until the app quits with an animation. Then start up the app and check the interval setting - report back if it's reverted to 1hr or if it's kept.

If it's kept, then try changing vehicle and repeat the force quit procedure and check the value if it's been reset and report back.

If none of those reproduce the reset, then please try and backtrace your previous usage, if you can get it to reset by any specific action.

[Kemmey]

When we've resolved this, I would actually really like your feedback on how the app works and performs with three vehicles on the account. Let me know what issues you run into and what you'd like added or changed. The complications for instance will always reflect active vehicle.

[GeeRee1]

Will do in next day or so. Thanks.

On Wed, Aug 12, 2020 at 4:37 PM Kim Hansen notifications@github.com wrote:

When we've resolved this, I would actually really like your feedback on how the app works and performs with three vehicles on the account. Let me know what issues you run into and what you'd like added or changed. The complications for instance will always reflect active vehicle.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kemmey/Kemmey-TeslaWatch-Public/issues/91#issuecomment-673098181, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQSWNTXRIAMPFXWEPDN7I2DSAL4RVANCNFSM4P342ZLQ .

-- Sent from iPhoneX. Pardon any typos.

[GeeRee1]

Hi Well I tried the force quit, but now all three cars are reverting to 2hr 45 min. I changed one of the car’s interval to 4 hrs, and just went to another car, then back to the first and the interval wasn’t saved, but was 2 hr 45 min again.

I have the Background updates on, and Allow wakein backgrfound off.

If I make both toggles “on”, and change the interval, force quit, and come back into app,its still 2 45.

Weird. Maybe a bug with multiple cars?

Other than this issue, app seems to work well for 3 cars (we have a 3 and a new Y, and an older S which is going off to one of my [lucky] kids in a while). The car names are perhaps a bit long, so when in the main window a couple of the names flow onto another line, but that’s minor matter (screen shot attached).

Are you in Copenhagen? I saw a Tesla gallery there a couple of years ago!

On Wed, Aug 12, 2020 at 2:14 PM Kim Hansen notifications@github.com wrote:

hey,

That's interesting - there was a bug in the 1.0.2 betas that the configured interval was not persisted properly, but it's not something that I've heard of since.

Could you verify a few things to get closer to the issue?

Try setting the interval to a different value than 1hr, then force quit the app by holding in the wide side button until you get the three sliders

• then hold in the crown until the app quits with an animation. Then start up the app and check the interval setting - report back if it's reverted to 1hr or if it's kept.

If it's kept, then try changing vehicle and repeat the force quit procedure and check the value if it's been reset and report back.

If none of those reproduce the reset, then please try and backtrace your previous usage, if you can get it to reset by any specific action.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kemmey/Kemmey-TeslaWatch-Public/issues/91#issuecomment-673031673, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQSWNTXDBXDGC6EYAXSLBVTSALLZTANCNFSM4P342ZLQ .

-- Sent from iPhoneX. Pardon any typos.

[Kemmey]

Two things

1. Did you remember to tap the set button after changing the interval? So tap to show the slider, modify the slider, then tap the set button to store the value.

2. The configured value applies to all cars. You may change the active vehicle at any time, but the background update will ONLY update for the current active vehicle. And that's also what the complication will reflect.

I used to live in Copenhagen, but moved back to Jutland some years ago. Now I live near LEGO and LEGOLAND :-D

[GeeRee1]

Hi

1. My bad. No, I didn't realize that the “set” button needed to be

tapped. When I do, it retains the setting and sets it for all the vehicles. So that’s resolved.

2. To my mind, its fine that the configured value applies to all cars, but

I didnt’ understand what you meant by “ the background update will ONLY update for the current active vehicle.” So if car #1 is set to update say every 2 hrs, car #2 (and #3) will or will not update every 2 hrs? If not, when will they update? Or no update until they become the “current active vehicle.”?

So that raises an interesting question - if my wife also downloads the app and sets car #2 to be active and update every two hours on her watch, what will happen to car #1 on my watch? And for the car?

Haha, its complicated having more than one Tesla.

Thanks for the quick feedback and tips to get this working.

I’ll not mention to Grandson that you’re near Legoland....he’s 8 and buildS Lego projects all the time. A budding Tesla engineer perhaps.

Best, GR

On Thu, Aug 13, 2020 at 3:58 PM Kim Hansen notifications@github.com wrote:

Two things

1.

Did you remember to tap the set button after changing the interval? So tap to show the slider, modify the slider, then tap the set button to store the value.

2.

The configured value applies to all cars. You may change the active vehicle at any time, but the background update will ONLY update for the current active vehicle. And that's also what the complication will reflect.

I used to live in Copenhagen, but moved back to Jutland some years ago. Now I live near LEGO and LEGOLAND :-D

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kemmey/Kemmey-TeslaWatch-Public/issues/91#issuecomment-673680535, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQSWNTV7WOASSK37S7IGK23SARAUZANCNFSM4P342ZLQ .

-- Sent from iPhoneX. Pardon any typos.

[Kemmey]

It's a bit complicated, but not too much - what it really comes down to is that the app doesn't try to be all that intelligent about it, so you just have to take everything literal.

So the active vehicle, is the one showing on the main screen of the app. When enabling background updates, only the at any time active vehicle will ever be updated from the background - or even from when the app is active. To update any other vehicles, you have to enter the vehicle chooser and once you do, all other cars will be initially woken up and refreshed for an overview.

So if you have to watches, and have one vehicle active on one watch and another active on another watch, then each watch will wake their respective active vehicle according to the configured background update and wake settings. There is no communication or intelligence between separate installs of the app logged into the same account.

[Kemmey]

oh - and I'm 40 and build lego sets all the time :-D

[GeeRee1]

Thanks...I think that answers the multi-car issues...I’ll keep an eye out for issues or suggestions for next version. Best,

On Fri, Aug 14, 2020 at 4:34 PM Kim Hansen notifications@github.com wrote:

It's a bit complicated, but not too much - what it really comes down to is that the app doesn't try to be all that intelligent about it, so you just have to take everything literal.

So the active vehicle, is the one showing on the main screen of the app. When enabling background updates, only the at any time active vehicle will ever be updated from the background - or even from when the app is active. To update any other vehicles, you have to enter the vehicle chooser and once you do, all other cars will be initially woken up and refreshed for an overview.

So if you have to watches, and have one vehicle active on one watch and another active on another watch, then each watch will wake their respective active vehicle according to the configured background update and wake settings. There is no communication or intelligence between separate installs of the app logged into the same account.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kemmey/Kemmey-TeslaWatch-Public/issues/91#issuecomment-674261461, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQSWNTQANYMEIFZR7GKLS5LSAWNVRANCNFSM4P342ZLQ .

-- Sent from iPhoneX. Pardon any typos.

[GeeRee1]

Hi from New York, I wrote this blog that just went up on the Tesla Owners Club of New York, a group that has about 1000 members. Thought you'd be interested, and hope it results in some downloads for the app. Best regards, GR

https://www.tocnys.org/blog/9400919

On Wed, Aug 12, 2020 at 4:37 PM Kim Hansen notifications@github.com wrote:

When we've resolved this, I would actually really like your feedback on how the app works and performs with three vehicles on the account. Let me know what issues you run into and what you'd like added or changed. The complications for instance will always reflect active vehicle.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kemmey/Kemmey-TeslaWatch-Public/issues/91#issuecomment-673098181, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQSWNTXRIAMPFXWEPDN7I2DSAL4RVANCNFSM4P342ZLQ .