Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

search or play puts in two FF's on the end #21

Open
ranger786 opened this issue Feb 20, 2017 · 6 comments
Open

search or play puts in two FF's on the end #21

ranger786 opened this issue Feb 20, 2017 · 6 comments

Comments

@ranger786
Copy link

Alexa, tell roku to play titanic
Alexa, tell roku to play king kong on plex

in all the searches it puts the extra "FF's" at the end, how to fix this?

Thanks

@julianh2o
Copy link
Owner

Hmm, you might want to look into line 200 in https://github.com/julianh2o/RokuAlexaLambdaSkill/blob/master/RokuControlServer/server.js

That's where the keypresses for searching and playing are coming from. Is it possible that it's not tabbing over enough when it's trying to go to the results? Has there been an update in how the search layout operates?

Look at that sequence there and see if you can follow along with it. The line that goes createTypeSequence(text) is the one that's actually simulating the correct letters. Perhaps the series of "right" pushes below it are doing something weird?

Unfortunately it'll be pretty hard for me to debug without seeing exactly what's happening for you.. I'd tinker with that code (and relaunch the server each time you edit it) and see if you can get something working!

@cmon69
Copy link

cmon69 commented Mar 21, 2017

I'm getting that two!

@cmon69
Copy link

cmon69 commented Mar 22, 2017

ranger786, did you find a solution? I didn't want to mess with the code but am thinking of trying it after taking out

rokuAddress+"keypress/right",
keyDelay,
rokuAddress+"keypress/right",
keyDelay,

@julianh2o
Copy link
Owner

julianh2o commented Mar 22, 2017 via email

@cmon69
Copy link

cmon69 commented Mar 23, 2017

Here is the video, also I wanted to mention that I was having the same issue using the scripts that I had previously use from https://github.com/chris1642/alexaroku if it helps. https://www.youtube.com/watch?v=gFcHfBSAyvw&feature=youtu.be

@julianh2o
Copy link
Owner

Sorry for the delay, got swept up in something!

I think you should be able to fix this by inserting a new line after line 221 if server.js.

Line 221 reads: ],createTypeSequence(text),[

If you add a new line after that something like..

 1000,

Or to be extra safe...

2000,

It may work for you.

Looks like you might want to also increase the delay on line 220 from 500 to something like 1000.

Let me know if that helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants