Fuel prices subscription - works in HOME, not via Bluetooth

[mvl]

I just signed up for PLUS fuel prices.

It works in HOME, letting me download updates whenever I want.

However updates don't work via Bluetooth. When I try to change fuel grade, it says "You need a subscription for this TomTom Service (your current subscription may have expired). Visit www,tomtom,com for more information.

I also noticed that under "My services", fuel prices isn't listed (don't know if it is supposed to be).

I have no problems with Weather or Traffic, so I'm assuming my phone connection's fine.

Any ideas? Was this bad provisioning on my account? Or is there a typical lag between subscription to service availability? (my traffic was instantaneous)

Or is this just another bug?

Go 720 app 8.351 / map NA_2GB 830 + full NA POI
+ map subscription + PLUS traffic + Fuel prices
HOME 2.6.3.1609 - WinXPproSP3

 

[canderson]

I have never been able to convince myself that even for common services that can be obtained by both DUN and Home methods (e.g., QuickFix and Mapshare), that the end point servers used by Services and Home are one in the same. If they're not, you could be right and not have been "enabled" on one of the two during provisioning. It's my sense (and it's ONLY that) that the Home server is the same one that is first updated after a phone or online subscription, and that the Services server is expected to remain sync'd to that one. Or I could be too tired to know what I'm talking about tonight!

Worth a call to tech support, though.

 

[mvl]

Worth a call to tech support, though.

Yeah - they're closed - I'll call tomorrow and post back the findings.

 

[sageuvagony]

When I hit "update" from within my tomtom device to update fuel prices, it says "you must be connected to TomTom Home" or something like that, so it looks like it doesn't even try to use a data connection.

 

[mvl]

Yeah - app 8.410 isn't supposed to support bluetooth - it's for the tomtom 140/340

 

[gatorguy]

Funny . . good recognition MVL

 

[dhn]

Wasn't it Willy Shakespeare (through Hamlet) who said "Hoisted on one's own petard"?

[May not be quite relevant here but I don't get that much chance to use the phrase in a gps forum .. ]

 

[mvl]

So I called Tomtom support and they recommended a factory reset. I'm very skeptical, but I'll try that when I get to the house and have a chance to back up.

 

[mvl]

I'll be dammed - Tomtom phone support was right - a factory reset did the job. I suspect it had something to do with me logging in again to Tomtom services.

I'm wondering if only a re-login to Tomtom services in preferences would have done the trick. Well, that's the great thing about backups. I'll try and post back in a few.

 

[mvl]

So I didn't need the factory reset after all. I restored my backup and got the prior "no subscription" message.

Then I went to preferences, my tomtom acount, and re-logged-in. After that the fuel showed up in "my services" and I could update again via bluetooth. So it looks like new bluetooth subscriptions need a re-login to re-query for the activated features.

 

[canderson]

So I didn't need the factory reset after all. I restored my backup and got the prior "no subscription" message.

Then I went to preferences, my tomtom acount, and re-logged-in. After that the fuel showed up in "my services" and I could update again via bluetooth. So it looks like new bluetooth subscriptions need a re-login to re-query for the activated features.

Now that's different. The only service I ever added was Traffic (DUN style). I had already logged in and set up the account and done the test with weather and quickfix to be sure I had the link working correctly. I subscribed to Traffic over the phone and never had to perform an additional "login" from the unit. Then again, this was quite some time ago, and anything could have changed since then.

Good to know, though. I just don't understand how/why that step was necessary. If your existing services are working, your unit is logging you in each time you fire up the unit over the DUN connection, so it knows who you are. Why the separate manual step to do it? Curious. Thanks for the info, as I doubt anyone else would have thought of that, either.