Describe your system and processes, and post your config file.
- Posts: 31
- Joined: Thu Dec 09, 2010 12:53 pm
- Bot?: No
I somehow figured it out. In my Alexa Skill I had it set Payload version = v3 per Amazon's recommendation as v2 is deprecated (screen shot below). I changed it to v2 and everything worked fine. I went back into the Lambda JS and changed the following:
- The value for payloadVersion to 3 on lines 123, 269, 368, and 534. I didn't find any others.
- The value for version in each appliance object to 3.
I then published the Lambda, updated the ARNs in my skill, and changed the Payload version from v2 back to v3. Didn't work. I changed it back to v2 and it worked again. I'm not sure where the update is that needs to be made to use v3.
Also, I'm assuming I'll need to change my IP address constantly unless I purchase a static IP address from my ISP, yes?
- Site Admin
- Posts: 1616
- Joined: Sun Jul 18, 2010 7:51 am
- Bot?: No
- Location: Huntington Beach, CA
You could always use a dynamic DNS service and point the Lambda function to that name instead of an IP. For a while they weren't letting you select V2, so good you were able to do so. If I get time one of these days, I'll update it for V3. Not really sure how many people actually use it.
Who is online
Users browsing this forum: No registered users and 1 guest