4/18/16 Connection Issues

[jerlands]

Unable to retrieve logs and Echo commands unreliable

 

 

 

Jon...

 

 

back up it seems...

 

 

Jon...

Edited April 18, 2016 by jerlands

[Michel Kohanim]

Hi Jon,

 

Can you please check your error log?

 

All systems have been 100% up and we have had no resource usage above the ordinary.

 

With kind regards,

Michel

[jerlands]

Hi Jon,

 

Can you please check your error log?

 

All systems have been 100% up and we have had no resource usage above the ordinary.

 

With kind regards,

Michel

 

Nothing shows in the error log during this period.

2016/04/18 03:22:22 System -100    [DHCP] state=RENEW  <<-- last event

 

And the event log looks like normal activity..

 

38 3 52 1 ST 0 2016/04/18 12:20:02 System 5

14 2C 31 2 ST 255 2016/04/18 12:22:49 System 5

2E 75 F9 1 ST 0 2016/04/18 12:40:59 System 5

2E 75 F9 1 ST 255 2016/04/18 12:41:10 System 5

 

Echo gave several responses "that command doesn't work" but the commands processed

 

 

Jon...

[Michel Kohanim]

Hi Jon,

 

Thanks so very much. I checked the portal logs and everything is looking fantastic. This said, I must admit that recently I have been plagued with Echo being unreliable and do strange things:

1. Two Dots work perfectly every time

2. The Echo, on the other hand, is now responding with "Turned on x" instead of "Ok". And, in some cases, and for the same device, it keeps saying "I cannot find x in Michel's profile" or "that command does not work with x" or a simple beep (as if it didn't understand it even though the app says it did). Note that this behavior is very much like the Skill's behavior and not connected home

 

Something very strange is going on. Hopefully we'll hear back from Amazon soon.

 

With kind regards,

Michel

Michel

[jerlands]

Hi Jon,

 

Thanks so very much. I checked the portal logs and everything is looking fantastic. This said, I must admit that recently I have been plagued with Echo being unreliable and do strange things:

1. Two Dots work perfectly every time

2. The Echo, on the other hand, is now responding with "Turned on x" instead of "Ok". And, in some cases, and for the same device, it keeps saying "I cannot find x in Michel's profile" or "that command does not work with x" or a simple beep (as if it didn't understand it even though the app says it did). Note that this behavior is very much like the Skill's behavior and not connected home

 

Something very strange is going on. Hopefully we'll hear back from Amazon soon.

 

With kind regards,

Michel

Michel

 

Thanks!

 

 

Jon...

[Xathros]

Hi Jon,

 

Thanks so very much. I checked the portal logs and everything is looking fantastic. This said, I must admit that recently I have been plagued with Echo being unreliable and do strange things:

1. Two Dots work perfectly every time

2. The Echo, on the other hand, is now responding with "Turned on x" instead of "Ok". And, in some cases, and for the same device, it keeps saying "I cannot find x in Michel's profile" or "that command does not work with x" or a simple beep (as if it didn't understand it even though the app says it did). Note that this behavior is very much like the Skill's behavior and not connected home

 

Something very strange is going on. Hopefully we'll hear back from Amazon soon.

 

With kind regards,

Michel

Michel

Hi Michel-

 

I'd be interested to know what the software version reports on your Echo.  As of right now, mine is still at 3032.

 

 

-Xathros

[Michel Kohanim]

Hi Xathros,

 

Echo: 3202

Dots: 3202

 

They are all 3202 ... quite strange to say the least!

 

With kind regards,

Michel

[jerlands]

Hi Michel-

 

I'd be interested to know what the software version reports on your Echo.  As of right now, mine is still at 3032.

 

 

-Xathros

 

Have you tried rebooting (unplugging power?)

 

 

Jon...

[Xathros]

Have you tried rebooting (unplugging power?)

 

 

Jon...

No, but based on Michel's reply, I don't think it matters now...  All of these changes must be at the mothership rather then in the devices.

 

-Xathros

[jerlands]

No, but based on Michel's reply, I don't think it matters now...  All of these changes must be at the mothership rather then in the devices.

 

-Xathros

 

Yes, I was just curious about update.

 

 

Jon...

[Xathros]

Yes, I was just curious about update.

 

 

Jon...

I'll power cycle tonight and see if anything changes.

 

-Xath

[Michel Kohanim]

Hi Guys,

 

No, I haven't. I shall do so tonight. Things were a little better last night! But, just a little.

 

With kind regards,

Michel

[Xathros]

I power cycled my Echo last night.  After boot, software version remained at 3032.  Before I rebooted, I did notice that the timer function is now back to where it started with a short and to the point response to "Alexa, Timer status".  Mine never suffered from some of the symptoms Michel mentioned a few posts back and continued to respond with "OK" for all successful CoHo/SH requests.

 

-Xathros

Edited April 20, 2016 by Xathros

[jerlands]

I power cycled my Echo last night.  After boot, software version remained at 3032.  Before I rebooted, I did notice that the timer function is now back to where it started with a short and to the point response to "Alexa, Timer status".  Mine never suffered from some of the symptoms Michel mentioned a few posts back and continued to respond with "OK" for all successful CoHo/SH requests.

 

-Xathros

 

I would think you'd have received an update by now.. in fact your missing two...  I'd contact support and see what can be done.  1-877-375-9365

 

 

Jon...

[Xathros]

I'm either blind or dyslexic.  Both of my Echos are at 3202  Not 3032...

 

-Xathros

[jerlands]

I'm either blind or dyslexic.  Both of my Echos are at 3202  Not 3032...

 

That must be going around

 

I found the version history in Wiki

 

 

Jon...