Alexa is timing out very often

[kxkayser]

Hi. Have been using this great service for almost 2 years and have about 15 devices defined. Lately, in the last month or so, Alexa has been responding with “(device name) not responding. Please check it’s network connection and power supply” quite often. In fact, most times the first command for a given device she times out but subsequent commands to the same device work normally. Actually, the command works despite the bad return message. My network is very reliable and fast and as I say, this is a relatively new issue. Any ideas about how to debug? Thanks

[Bra1nK]

This has been happening here on and off for years and I'm guessing it's an Amazon issue, I think their servers are getting busy especially at peak times.

[kxkayser]

OK Brian. Thanks for the quick response. Let’s see what happens after the holiday shopping is over.

Regards,

Ken Kayser

Tobaccoville, NC

@.***

From: Brian Kelly @.*** Sent: Friday, December 17, 2021 1:51 AM To: hardillb/node-red-alexa-home-skill-web Cc: kxkayser; Author Subject: Re: [hardillb/node-red-alexa-home-skill-web] Alexa is timing out very often (Issue #131)

This has been happening here on and off for years and I'm guessing it's an Amazon issue, I think their servers are getting busy especially at peak times.

— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-alexa-home-skill-web/issues/131#issuecomment-996479586 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALCGTV4GWTVBTQD7SWMF6U3URLMWXANCNFSM5KH2RZAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ALCGTV73SA2BLADHJTJDPZLURLMWXA5CNFSM5KH2RZA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHNSREYQ.gif Message ID: @.***>

[Bra1nK]

I think it's more to do with the new Alexa devices coming on line, there's been loads of special offers recently and it's liable to get worse over Xmas at least until they up the capacity. All this assumes my guess is correct.

[kxkayser]

One additional piece of information. It only happens on devices using your node. Devices using smartlfe for example work normally

On Fri, Dec 17, 2021, 9:09 AM Brian Kelly @.***> wrote:

I think it's more to do with the new Alexa devices coming on line, there's been loads of special offers recently and it's liable to get worse over Xmas at least until they up the capacity. All this assumes my guess is correct.

— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-alexa-home-skill-web/issues/131#issuecomment-996750768, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALCGTV62CLSEQI26DQGK7IDURNAB7ANCNFSM5KH2RZAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[SpeedyRS2]

Since a few months I have the problem also more and more often. Meanwhile with almost every call. The action is carried out in the end, but the message still comes. The execution is often also very delayed.

[kxkayser]

Frankly, it became unusable. I have switched out all my nodes to with virtual-smart-home. It required some reprogramming but all responses are now instantaneous.

Ken Kayser

Tobaccoville, NC

@.***

From: SpeedyRS2 @.*** Sent: Sunday, December 26, 2021 11:23 AM To: hardillb/node-red-alexa-home-skill-web Cc: kxkayser; Author Subject: Re: [hardillb/node-red-alexa-home-skill-web] Alexa is timing out very often (Issue #131)

Since a few months I have the problem also more and more often. Meanwhile with almost every call. The action is carried out in the end, but the message still comes. The execution is often also very delayed.

— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-alexa-home-skill-web/issues/131#issuecomment-1001207969 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALCGTV75GWCX3K3BQ5OEOQTUS46OJANCNFSM5KH2RZAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ALCGTV6XA2KW6KULTV7Z7N3US46OJA5CNFSM5KH2RZA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHOWTRII.gif Message ID: @.***>

[hardillb]

I will try and find some time this week to move the broker and db to a bigger machine. I just haven't had the spare time yet

[kxkayser]

OK, please let us know when you accomplish this. I’d like to be able to use it again.

Regards,

Ken Kayser

Tobaccoville, NC

@.***

From: Ben Hardill @.*** Sent: Sunday, December 26, 2021 11:35 AM To: hardillb/node-red-alexa-home-skill-web Cc: kxkayser; Author Subject: Re: [hardillb/node-red-alexa-home-skill-web] Alexa is timing out very often (Issue #131)

I will try and find some time this week to move the broker and db to a bigger machine. I just haven't had the spare time yet

— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-alexa-home-skill-web/issues/131#issuecomment-1001209858 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALCGTV743V75E4AYLPJHQATUS4745ANCNFSM5KH2RZAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread. https://github.com/notifications/beacon/ALCGTVZRHKIB6V47HXOQNUTUS4745A5CNFSM5KH2RZA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHOWUAAQ.gif Message ID: @.***>

[hardillb]

New broker/database machine is up and running please let me know how it's going as I don't have access to my test hardware at the moment.

[Bra1nK]

Devices have stopped responding

[hardillb]

The broker keeps crashing at the moment, it runs for a long a while then falls over

[hardillb]

OK, back on old hardware, should be back up (if a little laggy). Will work out what was killing the broker on the new hardware later.

[Bra1nK]

Yes working again

[GetUpdate]

Still have the "... antwortet nicht überprüfe die Stromversorgung und die Internetverbindung des Geräts" problem too. -> It switches the device after seconds finaly.

Is there please any check option where the time went to (e.g. you send us a time stamp back?)?

THX Michael

[hardillb]

It's the broker backend, not something you can fix. I'll have another do at deploying the new backend machine tomorrow

[hardillb]

New broker/DB back end swapped in again this morning. Things look to be working properly this time. Please test

[Bra1nK]

Seems to be OK so far and currently responding faster

[GetUpdate]

Same, much faster response. Currently GREAT, loving it.

[SpeedyRS2]

Right at the moment, everything works on warp speed. Really great. Thank you very much :-)

[loxatsonnenberg]

I have still the same issue as @GetUpdate flow state is keeps "disconnected"

[Bra1nK]

Does this apply https://github.com/hardillb/node-red-alexa-home-skill-web/issues/112#issuecomment-754884628 ?

[loxatsonnenberg]

Does this apply #112 (comment) ?

That I can not confirm. The flow reports: "Error: Connection refused: Not authorized" in the debug section. My credidentials are ok, I'm able to select all the devices via NR. They are also discovered with Alexa.

[hardillb]

OK, the "Not authorized" stuff has nothing to do with this issue (which is clearly about voice command timing out) which is now fixed so I'm closing this issue. We can open a new one to track what's happening with the totally different problem.

[hardillb]

When you open a new issue, include ALL the relevant information. e.g.

• username
• version of Node-RED
• version of NodeJS
• version of Alexa node
• version of OS
• Anything from the Node-RED console logs (not just the debug sidebar)
• Are you running on Home Assistant (and have you tried to reproduce the problem outside HA)