mike-grant / haaska

Home Assistant Alexa Skill Adapter that supports v3 of the Alexa Smart Home Skill API
MIT License
537 stars 117 forks source link

Timeout #173

Open japurillo opened 4 years ago

japurillo commented 4 years ago

For some reason, I always get a timed out on tests. Even extendid it to 1 minuite and still it times out.

START RequestId: 0c000ef2-9fe1-49d2-a508-995d8a8603b1 Version: $LATEST END RequestId: 0c000ef2-9fe1-49d2-a508-995d8a8603b1 REPORT RequestId: 0c000ef2-9fe1-49d2-a508-995d8a8603b1 Duration: 30030.17 ms Billed Duration: 30000 ms Memory Size: 320 MB Max Memory Used: 51 MB Init Duration: 261.84 ms
2020-07-25T07:28:18.113Z 0c000ef2-9fe1-49d2-a508-995d8a8603b1 Task timed out after 30.03 seconds

Any ideas?

Arvics commented 4 years ago

@japurillo Did you solved your time out issue?

I have the same: "Task timed out after 60.06 seconds"

christopherdopp commented 4 years ago

I am also getting a timeout on the tests:

START RequestId: 48bd06c0-5f0f-47c7-826b-0a6b4406aa97 Version: $LATEST
END RequestId: 48bd06c0-5f0f-47c7-826b-0a6b4406aa97
REPORT RequestId: 48bd06c0-5f0f-47c7-826b-0a6b4406aa97  Duration: 3003.14 ms    Billed Duration: 3000 ms    Memory Size: 128 MB Max Memory Used: 22 MB  
2020-08-02T03:18:45.693Z 48bd06c0-5f0f-47c7-826b-0a6b4406aa97 Task timed out after 3.00 seconds

my test event was copied from the steps:

{
  "directive": {
    "header": {
      "namespace": "Alexa.Discovery",
      "name": "Discover",
      "payloadVersion": "3",
      "messageId": "1bd5d003-31b9-476f-ad03-71d471922820"
    },
    "payload": {
      "scope": {
        "type": "BearerToken",
        "token": "access-token-from-skill"
      }
    }
  }
}

Do we need to specify the bearer token in this test event or is it ok as is?

christopherdopp commented 4 years ago

Well, after I posted this, I read a post in the Haaska Super Thread that said a user figured out a timeout was because they were missing a port in the URL of their config.json file. In my case I had the url specified to "https://****.duckdns.org:8123" - the port was specified, but when I copied the url to chrome it returned the "This site can't be reached" error. In my case removing the port number and leaving the url value of the config.json file to "https://*****.duckdns.org" allowed the lambda test to complete successfully. (replace **** with your duckdns.org domain name)

kchatcha commented 3 years ago

Hi Anyone, Do you have any idea for fixed this issue? I have tried with many edit on you guy recommended. It won't work for me. I have got error as

{ "errorMessage": "2020-10-06T14:19:37.591Z e55830b1-2f97-4983-9b61-4cf39f700302 Task timed out after 3.00 seconds" }

I'm very newbie and follow all the instruction of this gig and Youtube https://youtu.be/dmeIEEKmv58

Not success for me!!!

LeeTaylorX12 commented 2 years ago

Had the same issue .. resolved by removing port number in json config