Echo (Alexa) User Forums

Using outside the US

0 Members and 4 Guests are viewing this topic.

Re: Using outside the US
« Reply #75 on: August 25, 2016, 02:25:30 am »
Is anybody having problems setting the default music player in Settings > Music & Media > "Choose default music services".  I get a response of 'Could not retrieve music settings. Please try again later'

I am trying to set Spotify as the default so I don't have to ask Alexa to 'play on spotify'

Cheers
I wanna do that too

Sent from my SM-G928F using Tapatalk


Re: Using outside the US
« Reply #76 on: September 01, 2016, 03:58:04 pm »
I'm having some success meddling with the address, country and timezone.

Hey, wanted to let you know I just moved to the Netherlands, and this post worked great for me!  As long as you get the data right, city, state, zip, in the exact right format, it works, weather and time and everything works perfectly.  It took a little meddling, but my json looked like this... with some specifics stripped of course... so hopefully this helps someone else out there.

Code: [Select]
{
"deviceAccountId": "ACCOUNTIDHERE",
"deviceAddress": null,
"deviceAddressModel": {
"city": "Den Haag",
"countryCode": "NL",
"county": "South Holland",
"district": null,
"houseNumber": "1234",
"label": "StreetName 1234, 1234AB Den Haag, Netherlands",
"postalCode": "1234 AB",
"state": null,
"street": "StreetName"
},
"deviceSerialNumber": "DEVICESERIAL",
"deviceType": "DEVICETYPE",
"distanceUnits": "IMPERIAL",
"firstRunCompleted": true,
"notificationEarconEnabled": true,
"postalCode": "1234 AB",
"responseStyle": "CONCISE",
"searchCustomerId": "CUSTOMERIDHERE",
"temperatureScale": "FAHRENHEIT",
"timeZoneId": "Europe/Amsterdam",
"voiceCastEnabled": null,
"autocastToThisClient": false,
"isSaveInFlight": true
}

Re: Using outside the US
« Reply #77 on: September 01, 2016, 04:49:13 pm »
I'm having some success meddling with the address, country and timezone.

Hey, wanted to let you know I just moved to the Netherlands, and this post worked great for me!  As long as you get the data right, city, state, zip, in the exact right format, it works, weather and time and everything works perfectly.  It took a little meddling, but my json looked like this... with some specifics stripped of course... so hopefully this helps someone else out there.

Code: [Select]
{
"deviceAccountId": "ACCOUNTIDHERE",
"deviceAddress": null,
"deviceAddressModel": {
"city": "Den Haag",
"countryCode": "NL",
"county": "South Holland",
"district": null,
"houseNumber": "1234",
"label": "StreetName 1234, 1234AB Den Haag, Netherlands",
"postalCode": "1234 AB",
"state": null,
"street": "StreetName"
},
"deviceSerialNumber": "DEVICESERIAL",
"deviceType": "DEVICETYPE",
"distanceUnits": "IMPERIAL",
"firstRunCompleted": true,
"notificationEarconEnabled": true,
"postalCode": "1234 AB",
"responseStyle": "CONCISE",
"searchCustomerId": "CUSTOMERIDHERE",
"temperatureScale": "FAHRENHEIT",
"timeZoneId": "Europe/Amsterdam",
"voiceCastEnabled": null,
"autocastToThisClient": false,
"isSaveInFlight": true
}
Why Fahrenheit?  :)

Cheers,
Alex


Re: Using outside the US
« Reply #78 on: September 02, 2016, 01:53:18 pm »
Why Fahrenheit?  :)

Cheers,
Alex

Because that's how God measures the temperature.  8)

Re: Using outside the US
« Reply #79 on: September 02, 2016, 02:37:35 pm »
Why Fahrenheit?  :)

Cheers,
Alex

Because that's how God measures the temperature.  8)
You wish [emoji12]

Cheers,
Alex


Re: Using outside the US
« Reply #80 on: September 02, 2016, 02:56:55 pm »
Why Fahrenheit?  :)

Cheers,
Alex

Because that's how God measures the temperature.  8)
You wish [emoji12]

Cheers,
Alex

He also refers to soccer as "soccer" (not "football"), carries a 9mm (not a .45) and never....EVER...puts beans in chili.

I think that about covers it.  ;)

Re: Using outside the US
« Reply #81 on: September 03, 2016, 12:14:39 am »
Hello everyone!

Just wanna say mine works here in Manila after the doing the request maker but no weather update though which is not a biggie.

I did notice that after the update, asking who our current president is it gave me the previous president as the answer. Prior to the update it was giving me the correct answer.

Any ideas on why is it's giving me a wrong answer?

Thanks and more power!

Re: Using outside the US
« Reply #82 on: September 03, 2016, 06:17:44 am »
Hi fallen angel have you any idea how I change the destination route info from killometre to miles?


Sent from my iPhone using Tapatalk

Re: Using outside the US
« Reply #83 on: September 03, 2016, 12:39:55 pm »
Hi fallen angel have you any idea how I change the destination route info from killometre to miles?


Sent from my iPhone using Tapatalk
Yep - in your Alexa App -> Strings -> Select your device..

Cheers,
Alex


Re: Using outside the US
« Reply #84 on: September 03, 2016, 01:01:52 pm »
Hi fallen angel have you any idea how I change the destination route info from killometre to miles?


Sent from my iPhone using Tapatalk
Yep - in your Alexa App -> Strings -> Select your device..

Cheers,
Alex


Thanks Alex I've still not getting miles just km


Sent from my iPhone using Tapatalk

Re: Using outside the US
« Reply #85 on: September 03, 2016, 01:21:51 pm »
Hi fallen angel have you any idea how I change the destination route info from killometre to miles?


Sent from my iPhone using Tapatalk
Yep - in your Alexa App -> Strings -> Select your device..

Cheers,
Alex


Thanks Alex I've still not getting miles just km


Sent from my iPhone using Tapatalk
That box has to be off not on for miles but also means temperatures in F, you can't have them mixed :)

Cheers,
Alex
« Last Edit: September 03, 2016, 01:23:44 pm by TheFallenAngel »

Re: Using outside the US
« Reply #86 on: September 10, 2016, 05:07:22 pm »
For those in the UK - do you have your echo associated with your UK Amazon accounts or have you set up an Amazon.com account?

Maff

Re: Using outside the US
« Reply #87 on: September 11, 2016, 05:52:47 pm »
I use my UK account, but it's possible a long time ago I enabled this account to also work on US site. I'm really hoping after the Echo is launched in the UK next week, that it will be an easy transition to a UK setup, and having my echo understand its in the UK with no odd issues. On the other hand I suspect, like Google & Siri that Echo that echo will now have a British accent if used in the UK.. I think I'm going to miss the American voice! And I really hope they don't make Echo male in the UK, which Apple did with Siri.

Re: Using outside the US
« Reply #88 on: September 15, 2016, 10:19:04 am »
As mentioned in another thread, I just changed my address to UK in settings and it took it OK.

Re: Using outside the US
« Reply #89 on: September 15, 2016, 06:27:00 pm »
Is this method still working for people?  I'm not seeing any PUT requests from when I update my address.
From Nigeria.
I think Request Maker is very buggy.
I am going crazy trying to find the PUT request. Changed address multiple times. Initially thought new intercepted data is on the top of the list when you click the envelope. Scrolling down, I saw some past PUT requests but when I changed those to Africa/Lagos, I got the 400 bad request error. Probably the url expired or something. 
Anyway, I will keep trying to get the XHR PUT to show again when I click the envelope after changing the address.

PS: I closed chrome, restarted PC. Even tried to find other addons on mozilla and chrome to do the same thing.


UPDATE: Don't know what I did but XHR PUT eventually showed in request maker. I think I put an invalid address and the error display came up saying put a valid one, then I put a US one. So if you can't find XHR PUT, put a weird address like CZ or TH and save. Then put a US address.
Anyway, Alexa knows my time now. Not sure Weather and others will work because Amazon will probably get done with the rest of the free world before adding Nigeria. No idea how the address system for my country is setup by Amazon (if the state name is spelt out fully or coded etc). I tried street name spelt fully and short code, tried google maps name for my street too (it can be different sometimes). The label updated itself correctly though.

Anyway, I'm glad Alexa has the correct time anyway and I can use timers and alarms properly now.
Thanks OP and everyone else that's contributed.
« Last Edit: September 15, 2016, 07:20:49 pm by ngwarrior »