chris1642/alexaroku

alexaroku's Issues

Issue W/Lambda

I did all the setup and installation of this awesome skill back in January of this year (2017) and it's worked flawlessly up until about a month ago. I've been looking at what the issue may be on and off but can't seem to figure it out. I setup mine on a raspberry pi to avoid tying up a computer. My problem seems to be with Lambda. When I try running the test, I get the following error. Any ideas?? Hoping someone can help,

{
"errorMessage": "Cannot read property 'application' of undefined",
"errorType": "TypeError",
"stackTrace": [
"AlexaSkill.execute (/var/task/AlexaSkill.js:72:62)",
"exports.handler (/var/task/index.js:299:10)"
]
}

When I look at the log file when envoking the skill with Alexa, the following is logged.

02:07:09
START RequestId: f680aaa2-70dd-11e7-9d94-2560061df5a7 Version: $LATEST
02:07:09
2017-07-25T02:07:09.351Z f680aaa2-70dd-11e7-9d94-2560061df5a7 session applicationId: amzn1.ask.skill.e15f54c0-edb5-4a63-8720-76b68d28a436
02:07:09
2017-07-25T02:07:09.572Z f680aaa2-70dd-11e7-9d94-2560061df5a7 dispatch intent = PlayPause
02:07:12
END RequestId: f680aaa2-70dd-11e7-9d94-2560061df5a7
02:07:12
REPORT RequestId: f680aaa2-70dd-11e7-9d94-2560061df5a7 Duration: 3003.38 ms Billed Duration: 3000 ms Memory Size: 128 MB Max Memory Used: 19 MB
02:07:12
2017-07-25T02:07:12.351Z f680aaa2-70dd-11e7-9d94-2560061df5a7 Task timed out after 3.00 seconds

"LITERAL" slot type deprecated and unavailable in UK

This skill looks brilliant - unfortunately, it cannot be used in the UK as the "LITERAL" slot type is not available. (I believe it is or soon will be deprecated in USA too).

Would it be possible to change the skill to use CUSTOM slot types instead?

Many thanks.

use an autohotkey script to resume script when it crashes

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
#persistent
Loop
{

Process, Exist, node.exe ; check to see if Printkey.exe is running
If (ErrorLevel = 0) ; If it is not running
{
Run, C:\Users\username\server.js

}

Else ; If it is running, ErrorLevel equals the process id for the target program (Printkey). Then close it.
{

}

Sleep 600000	; sleep 10 minutes

}

README.md and link back to original repository

Hey @chris1642,

Would you mind adding a README.md file to the root of the repository? (this file will display to anyone who navigates to this Github repository right on the front page below the file list)

Also, I'd appreciate if you included attribution and a link back to my project so that people can find it if they're looking to contribute: https://github.com/julianh2o/RokuAlexaLambdaSkill

Anyone have issues with port forwarding on Netgear routeR?

Issue with step 42

Hi Guys, for some reason - on step 42, the node command prompt doesn't give me an IP for the Roku. Any idea what could be wrong?

thanks! and some comments!

Hey, just wanted to say thank you so much for this! It works great!!

I had a few hiccups setting it up, but they were pretty unique to my situation.

The first issue I hit was when I belatedly realized that the Alexa skill needs to be set up under the same Amazon account that you use for the Echo. This is probably obvious and wouldn't even be a problem for most people, but in my case, the Echo is set up with my wife's Amazon account, but I already had an AWS account, so I figured I could just use that - no dice! For obvious reasons, (it's not a published skill...), the AlexaRoku skill needs to be configured on the same Amazon account as the Echo.

Second, after I realized I should be using my wife's account, I tried to set up the Alexa skill and the Lambda function using her account. I was able to set up the Alexa skill just fine, but Amazon wouldn't let me access Lambda because this was a brand new AWS account. Apparently, according to Amazon, "[AWS] services may take up to 24 hours to fully activate." So that was a bummer. Thankfully, I was able to use the Alexa skill from my wife's account with the Lambda function I set up under my account. 🎉

The last thing I'd like to point out is that when I uploaded the zip file with the code for the Lambda function, I wasn't able to edit the code in the AWS console because the zip contained multiple files. To get around that, I just added the code from AlexaSkill.js and serverinfo.js to index.js (and edited the requires/exports accordingly, of course). Then if you create a zip from just that one file, you can edit the code direct in AWS, which was super handy when I was debugging.

Thanks again for this excellent guide! The level of detail you provided is wonderful. Now I can watch TV without getting up to grab a remote that's across the room. :D

Android TV and shield

Amazing documentation and setup instructions. I was able to get the echo to communicate with my roku on the first attempt.

I use the roku in the bedroom and have a Nvidia shield as my primary plex client. I assume that a lot of the core plex function could be reused on the shield. Once I understand the source more, I am going to look into trying to modify your source with work with the shield. Any thoughts on this? Have you looked at the shield at all?

package.json not being recognized as json file

I keep getting this error message and I cannot figure out a workaround

Slot types and English (UK)

Hi,

My Echo is setup with language set to 'English (UK)'. When I try to set up the Intent Schema and Sample Utterances, I get the following error:

** Error: There was a problem with your request: The built-in slot type AMAZON.LITERAL is not supported for this locale.**

Does this only work with US Echoes?

While following directions, there is now Alexa Skills Kit, in the Lambda Trigger section in the white open dotted box.

Search with Plex on Roku Stick

When I ask, for example, "Alexa tell Roku to play Star Trek on Plex", it will start up Plex and go into the search, but the button presses are WAY off and there will end up being only two or three letters typed into the search bar...and none of them are letters in the movie I requested.

I'm not sure if it's because the Roku Stick takes longer to start Plex, thus throwing the timings off for future commands or if there's some other quirk with the Roku Stick that's causing the issue.

There is no issue with Alexa hearing the command, it's within Plex and the search option.

Playing Undefined

Hi, when I try to say Alexa tell Roku to play tarzan on Plex, it says playing undefined. And if I say Alexa tell Roku to play movie tarzan on Plex, then on the search of plex, it's writing MOVIE TARZAN. lol
Any idea why please
tks
Seby

Not recognizing package.json

I tried validating the file on json validator, and it does not appear to be a valid json file.

Results

Error: Parse error on line 1:
<
^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'

Roku Premiere search doesn't work

Great skill here.

I found that the key presses for my Roku Premiere were off, and would get stuck searching. I fiddled around with the code, and eventually got search working. You can see my changes in 175158d