Ah... Beta...
Saturday, 7 February 2015 00:34![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
dr_phil_physicsMs. Alexa Echo is feeling a bit under the weather.
We got our Amazon Echo on Tuesday and set it up quite easily at 10pm. Wednesday and Thursday I was home most of the day and had it playing my Amazon Music playlists, answering questions, doing math problems.
Friday, however, it's not handling my playlists correctly.
My guess is that someone did a code push to fix something else and there was a coding error or a corrupt server file or something.
Oh, it plays music just fine. Individual songs. But when I started one of my playlists, it didn't start with the first song. And then when I stopped and restarted it, it might play the same song over and over, or play with just the first couple of songs. Shuffle play was off. Telling Alexa to skip or play next track -- usually ended up replaying the current track.
Put in two error tickets. The second regarded the Echo App, both on the Kindle Fire HD and on the webpage for use on my laptop, isn't displaying the current track properly -- not getting the control keys. If you click on a song, it does give the control keys. But of course the app has just told Echo to play the one song.
Anyway, they've got on the Help tab of the Echo app a call feature, where you put in a phone number and they call you back, so you know it's them. Got almost an immediate callback and nearly zero wait for the next customer service person. We spent about 29 minutes trying different things.
It's actually an amusing process, since there's Echo, which you can give voice commands, the Echo remote, the Echo app and the guy on the phone. I tried very hard to refer to the program as Echo and not Alexa, because if you say Alexa followed by anything, Echo tries to parse it for a command. (grin) At one point I reread what was on the Home page, displaying what Echo thought I said, and read it verbatim, so Echo heard Alexa + command and executed it again. (grin)
To get link data back to the DSL provider, they needed me to do something. "Alexa temperature" works, because it also gives a little forecast, so it was on long enough to record.
Anyway, the problem has been turned over to the techies. As it should be.
Any other Echo users out there having trouble with playlists after Noon EST on Friday 6 February 2015?
I note that Amazon is telling Echo users that they have these nifty new Playlists just for the Grammies. Hmm... maybe I was right about the coding error.
Oh, and the Cool New Thing I learned yesterday is this: From the Echo remote only, hold the microphone key and say "Simon Says _______" and Alexa will say whatever you tell her to say. The guy who told me about this said it was really useful when he was writing and needed to tell one of his kids to go get him a fresh soda from the fridge. (evil-grin) No, I haven't tested having Alexa say naughty things. Yet. (double-evil-grin)
Dr. Phil
We got our Amazon Echo on Tuesday and set it up quite easily at 10pm. Wednesday and Thursday I was home most of the day and had it playing my Amazon Music playlists, answering questions, doing math problems.
Friday, however, it's not handling my playlists correctly.
My guess is that someone did a code push to fix something else and there was a coding error or a corrupt server file or something.
Oh, it plays music just fine. Individual songs. But when I started one of my playlists, it didn't start with the first song. And then when I stopped and restarted it, it might play the same song over and over, or play with just the first couple of songs. Shuffle play was off. Telling Alexa to skip or play next track -- usually ended up replaying the current track.
Put in two error tickets. The second regarded the Echo App, both on the Kindle Fire HD and on the webpage for use on my laptop, isn't displaying the current track properly -- not getting the control keys. If you click on a song, it does give the control keys. But of course the app has just told Echo to play the one song.
Anyway, they've got on the Help tab of the Echo app a call feature, where you put in a phone number and they call you back, so you know it's them. Got almost an immediate callback and nearly zero wait for the next customer service person. We spent about 29 minutes trying different things.
It's actually an amusing process, since there's Echo, which you can give voice commands, the Echo remote, the Echo app and the guy on the phone. I tried very hard to refer to the program as Echo and not Alexa, because if you say Alexa followed by anything, Echo tries to parse it for a command. (grin) At one point I reread what was on the Home page, displaying what Echo thought I said, and read it verbatim, so Echo heard Alexa + command and executed it again. (grin)
To get link data back to the DSL provider, they needed me to do something. "Alexa temperature" works, because it also gives a little forecast, so it was on long enough to record.
Anyway, the problem has been turned over to the techies. As it should be.
Any other Echo users out there having trouble with playlists after Noon EST on Friday 6 February 2015?
I note that Amazon is telling Echo users that they have these nifty new Playlists just for the Grammies. Hmm... maybe I was right about the coding error.
Oh, and the Cool New Thing I learned yesterday is this: From the Echo remote only, hold the microphone key and say "Simon Says _______" and Alexa will say whatever you tell her to say. The guy who told me about this said it was really useful when he was writing and needed to tell one of his kids to go get him a fresh soda from the fridge. (evil-grin) No, I haven't tested having Alexa say naughty things. Yet. (double-evil-grin)
Dr. Phil
Posted on Dreamwidth Crossposted on LiveJournal
