dmhacker / dmhacker-youtube Goto Github PK

Hi,

I'm trying to set up your Alexa skill and my own Heroku server to power it, but I've run into a bit of a snag. Simply put, I believe I have the skill and Lambda set up correctly (This is my first go-around, though, so I might be mistaken about that.) yet the skill does nothing. After triple-checking the settings, I decided to go to your server and try playing a video manually, to make sure the problem wasn't on the backend. When I did, either by putting in a video ID or by searching, it only went to the video player screen, searched for about 30s, and returned me to the landing page with the message, "An error occured during processing." I then tried setting up my own Heroku server, again following your instructions, and I got the same errors on my end.

I'm really excited to get this working, and I'm sure I've just made a mistake somewhere, but I can't find it. Any thoughts?

Please refer to dmhacker/alexa-youtube-skill#78.

Did something change on alexa? I have both the youtube and the google developer skills setup and they worked fine for a long time..now neither seem to work...I've updated github and heroku to ensure they are deployed with the latest code but still alexa doesn't understand when I say "alexa tell youtube to play human league" which previously worked unless I'm getting the skills mixed up.

Hello, I follow your new instruction, it deployed successfully but the log say app crashed after starting:

2017-08-12T22:36:56.160020+00:00 heroku[web.1]: State changed from crashed to starting
2017-08-12T22:36:59.478981+00:00 heroku[web.1]: Starting process with command `node app.js`
2017-08-12T22:37:01.374424+00:00 app[web.1]: bash: node: command not found
2017-08-12T22:37:01.423978+00:00 heroku[web.1]: Process exited with status 127
2017-08-12T22:37:01.437545+00:00 heroku[web.1]: State changed from starting to crashed

Do I have to do something to specify this is a node js app?

Thank you,

Hi! I have deployed the service into Heruko following the guide you provided. When I do any action on the frontend app I get:

Failed to load resource: the server responded with a status of 503 (Service Unavailable)

The strange thing is that I got the error above also using your service at https://dmhacker-youtube.herokuapp.com.

Here is the log I collected from Heroku console:

2020-08-17T07:15:39.310757+00:00 app[web.1]: {
2020-08-17T07:15:39.310792+00:00 app[web.1]:   id: '4VR-6AS0-l4',
2020-08-17T07:15:39.310794+00:00 app[web.1]:   link: 'https://youtube.com/watch?v=4VR-6AS0-l4',
2020-08-17T07:15:39.310795+00:00 app[web.1]:   title: 'Ludovico Einaudi - Nuvole Bianche'
2020-08-17T07:15:39.310795+00:00 app[web.1]: }
2020-08-17T07:15:40.308584+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/search/nuvole%20bianche" host=aaaaaaa.herokuapp.com request_id=3ee6359c-c5bd-4188-81c0-ba0c760ca114 fwd="82.51.125.173" dyno=web.1 connect=0ms service=1783ms status=503 bytes=0 protocol=https
2020-08-17T07:15:40.303649+00:00 app[web.1]: internal/validators.js:117
2020-08-17T07:15:40.303682+00:00 app[web.1]:     throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
2020-08-17T07:15:40.303683+00:00 app[web.1]:     ^
2020-08-17T07:15:40.303683+00:00 app[web.1]: 
2020-08-17T07:15:40.303694+00:00 app[web.1]: TypeError [ERR_INVALID_ARG_TYPE]: The "url" argument must be of type string. Received undefined
2020-08-17T07:15:40.303694+00:00 app[web.1]:     at validateString (internal/validators.js:117:11)
2020-08-17T07:15:40.303695+00:00 app[web.1]:     at Url.parse (url.js:159:3)
2020-08-17T07:15:40.303695+00:00 app[web.1]:     at Object.urlParse [as parse] (url.js:154:13)
2020-08-17T07:15:40.303697+00:00 app[web.1]:     at doDownload (/app/node_modules/miniget/dist/index.js:90:28)
2020-08-17T07:15:40.303697+00:00 app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:79:11) {
2020-08-17T07:15:40.303697+00:00 app[web.1]:   code: 'ERR_INVALID_ARG_TYPE'
2020-08-17T07:15:40.303698+00:00 app[web.1]: }
2020-08-17T07:15:40.347133+00:00 heroku[web.1]: Process exited with status 1
2020-08-17T07:15:40.381539+00:00 heroku[web.1]: State changed from up to crashed

If instead I try with your api, this is what happens:

curl https://dmhacker-youtube.herokuapp.com/alexa/v3/search/bnV2b2xlIGJpYW5jaGU=?language=it
{"state":"success","message":"Found video result","video":{"id":"4VR-6AS0-l4","title":"Ludovico Einaudi - Nuvole Bianche","link":"https://www.youtube.com/watch?v=4VR-6AS0-l4"}}

curl https://dmhacker-youtube.herokuapp.com/alexa/v3/download/4VR-6AS0-l4
{"state":"success","message":"Beginning download process.","link":"/site/4VR-6AS0-l4.m4a"}

curl https://dmhacker-youtube.herokuapp.com/alexa/v3/cache/4VR-6AS0-l4
{"state":"success","message":"Not in cache"}

Am I doing something wrong?

Hi,
I hope you can help me with my issue.
I have been using Alexa youtube skill since March 2018 without any problems. About two months ago I received email from AWS with information about node.js runtime 6.10 is coming to the end of live (see below). But I carried on using it for a while.
First issue with Alexa not pulling music from youtube was about two weeks ago as we were on holiday for few weeks so not really sure when the issue started really. As soon I realised a problem I got my attention to this email from AWS about node 6.10.
After visiting my AWS account I tried changing lambda runtime from 6.10 to 8.10 and then saved the function. Tried to test Alexa skill and most of the time it will fail and play message "There was a problem with the requested skill response". I had few successful skill responses on occasion on odd songs but it doesnt happen very ofter. Not really sure what Im doing wrong here. Do I need to do anything apart from changing runtime from 6.10 to 8.10 ? Is there any alteration required to the code ?
Please let me know what I`m doing wrong. Do I need to republish this function after saving it with new runtime ?
Today I tried changing runtime back to 6.10 and skill had exactly the same response , most of the time it would failed however it happened twice this morning when it would actually play music - see attached pictures.

"
Hello,

Your AWS Account currently has one or more Lambda functions using the node.js 6.10 runtime. The Node Foundation has previously published that node.js 6.x "Boron" will be declared End-of-Life (EOL) on > April 2019 [1], and will stop receiving bug fixes, security updates, or performance improvements. Per the AWS Lambda runtime support policy [2], language runtimes that have reached their EOL are deprecated in AWS Lambda.

Invokes for functions configured to run on node.js 6.10 will continue to work normally, however the ability to create new Lambda functions configured to use the node.js 6.10 runtime will be disabled on April 30 2019. Code updates to existing functions using node.js 6.10 will be disabled 30 days later on May 30 2019

We encourage you to update your node.js 6.10 functions to a newer version of the Node runtime (node.js 8.10) so that you continue to benefit from important security, performance, and functionality enhancements offered by more recent releases. The newer node.js 8.10 version has improved ECMAScript support, along with other language and API improvements. The AWS Lambda programming model [3] for node.js 8.10 maintains backwards compatibility with previous versions to simplify portability. We recommend that you test your Lambda function to validate its behavior on the newer version of Node.js.

Should you have any questions or concerns please contact AWS Support [4].

[1] Node Foundation’s announcement of EOL: https://nodejs.org/en/blog/release/v6.9.0/
[2] AWS Lambda runtime support policy: https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html
[3] Using the AWS Lambda node.js 8.10 runtime: https://aws.amazon.com/blogs/compute/node-js-8-10-runtime-now-available-in-aws-lambda/
[4] AWS Support: https://aws.amazon.com/support

Sincerely,
Amazon Web Services
"

Hey @dmhacker , I am pretty interested in setting up my own Heroku server so I can have AWS Lambda query my own Heroku server instead, and I have put my own Heroku URL as an Environment variable in the node.js code that I uploaded to Lambda, (replaced 'https://dmhacker-youtube.herokuapp.com' with process.env.HEROKU_APP_URL + '/alexa/' and process.env.HEROKU_APP_URL + '/alexa+check/',), but what enviornment variables do I need to set on the Heroku side and what node.js Build Pack should I be targeting? Right away I am getting some error messages with this repo on Heroku and I suspect I am missing some Env Vars on the Heroku side or other configuration. Also what setup do I have to do with an AWS Bucket? Thanks

@dmhacker Can you update this repository? The YouTube searches are coming up empty on Heroku.

I built the app and specified a youtube API key but the web interface doesn't return any results. Doesn't matter if I use my own or the one specified in the configs.
https://raw.githubusercontent.com/dmhacker/alexa-youtube-skill/master/index.js

How can I extend the lifetime of the cached video?

Invalid template repository:
The source could not be retrieved.

Yo,

Thank you for your amazing work here.
It works like a charm even if, because of Heroku, the download of the video and the encoding as a sound for Alexa is a bit slow.
Did you try to use it on a dedicated server or on your personal computer ?
Which performances did you get ?

I'm planning to deploy it on one of my servers but the CPU is pretty basic, I don't know which system requirement I have to follow in order to have good performances (would be perfect if it took an average of 15sec to download the video and encode the sound)

Keep up the good work !

• Xerib

Getting an error when using this:

2018-02-09T07:46:20.996613+00:00 app[web.1]: Query result: Metallica - Enter Sandman [Official Music Video]
2018-02-09T07:46:21.695946+00:00 app[web.1]: events.js:154
2018-02-09T07:46:21.696003+00:00 app[web.1]:       throw er; // Unhandled 'error' event
2018-02-09T07:46:21.696019+00:00 app[web.1]:       ^
2018-02-09T07:46:21.696035+00:00 app[web.1]: 
2018-02-09T07:46:21.696052+00:00 app[web.1]: Error: Could not extract signature deciphering actions
2018-02-09T07:46:21.696054+00:00 app[web.1]:     at /app/node_modules/ytdl-core/lib/sig.js:48:11
2018-02-09T07:46:21.696056+00:00 app[web.1]:     at IncomingMessage.<anonymous> (/app/node_modules/ytdl-core/lib/request.js:43:9)
2018-02-09T07:46:21.696058+00:00 app[web.1]:     at emitNone (events.js:85:20)
2018-02-09T07:46:21.696059+00:00 app[web.1]:     at IncomingMessage.emit (events.js:179:7)
2018-02-09T07:46:21.696061+00:00 app[web.1]:     at endReadableNT (_stream_readable.js:913:12)
2018-02-09T07:46:21.696063+00:00 app[web.1]:     at _combinedTickCallback (node.js:383:13)
2018-02-09T07:46:21.696078+00:00 app[web.1]:     at process._tickCallback (node.js:407:11)
2018-02-09T07:46:21.631122+00:00 heroku[router]: at=info method=GET path="/alexa-check/CD-E-LDc384" host=xxxx.herokuapp.com request_id=447829c3-796b-4e26-b541-e7053e48b82b fwd="34.230.17.7" dyno=web.1 connect=1ms service=14ms status=200 bytes=273 protocol=https
2018-02-09T07:46:21.797499+00:00 heroku[web.1]: State changed from up to crashed
2018-02-09T07:46:21.784314+00:00 heroku[web.1]: Process exited with status 1

The service seems to deploy normally:
-----> ffmpeg app detected
-----> Install ffmpeg
DOWNLOAD_URL = https://www.johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz
exporting PATH
-----> Discovering process types
Procfile declares types -> web
-----> Compressing...
Done: 70.1M
-----> Launching...
Released v6
https://famewolf-youtube.herokuapp.com/ deployed to Heroku

However that url displays an error. I followed the process..had the skill already working and wanted to use my own instance so created the youtube api, cloned the github and connected them to heroku. Can you point me in right direction?

This is all that shows in logs:
2017-11-25T05:11:42.308518+00:00 heroku[web.1]: State changed from crashed to starting
2017-11-25T05:11:45.929086+00:00 heroku[web.1]: Starting process with command node app.js
2017-11-25T05:11:47.769107+00:00 heroku[web.1]: Process exited with status 127
2017-11-25T05:11:47.685534+00:00 app[web.1]: bash: node: command not found
2017-11-25T05:11:47.781747+00:00 heroku[web.1]: State changed from starting to crashed
2017-11-25T05:12:13.992213+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=famewolf-youtube.herokuapp.com request_id=bb4f7da4-9b43-4c2f-9ae0-330dd9b78320 fwd="173.125.16.148" dyno= connect= service= status=503 bytes= protocol=https
2017-11-25T05:12:14.669071+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=famewolf-youtube.herokuapp.com request_id=36cafcc0-3326-4750-93b6-41424349b6c5 fwd="173.125.16.148" dyno= connect= service= status=503 bytes= protocol=https

The lamda function failed with this error. Do you have any suggestions as of why?
Thank you so much!

2017-08-10T09:13:51.892Z	39847bd5-7dac-11e7-bf61-c376ad7ff20a	SyntaxError: Unexpected token C in JSON at position 0
at Object.parse (native)
at Request._callback (/var/task/index.js:78:29)
at Request.self.callback (/var/task/node_modules/request/request.js:188:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request.<anonymous> (/var/task/node_modules/request/request.js:1171:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage.<anonymous> (/var/task/node_modules/request/request.js:1091:12)
at IncomingMessage.g (events.js:292:16)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)