Skill taking too long to respond about geemusic HOT 12 CLOSED

It is likely due to your network provider, and the latency inherent to a proxy. Others may know how to improve your current setup, but if all else fails, you can deploy a completely free Heroku instance which will definitely perform properly because the infrastructure runs on AWS. The steps to do this are detailed in the README.

from geemusic.

Thanks for the tip. I looked into the Heroku free tier but I am worried about the fact that it will sleep after 30 minutes of inactivity. Do I have to be actively playing music through my echo and pinging the server with requests in order for it to stay active? Or will just having this code running in the background waiting for requests count as activity?

from geemusic.

from geemusic.

to answer your original question: I would try to run this on your main computer with ngrok to see if you can get it running on a fully powered computer. if you're still having problems with that setup then it might be an issue with your ISP.

Has anyone else run into this issue before? I've yet to see it so it's hard for me to test/debug.

from geemusic.

The Heroku sleep mode is definitely a potential issue, and with a quick test, it appears the boot time isn't usually fast enough. You might be able to use IFTTT or your local pi to query the server every 25 minutes or so, but if not you will definitely run into issues.

from geemusic.

We might want to add a note about that to the README. I can throw that up later today when I have time unless someone wants to submit a quick PR before then.

from geemusic.

Okay I will try getting it up and running on another computer and see if that works. Any idea if I will need to generate a new google application password? I don't know if they are tied to specific hardware once used the first time

from geemusic.

I have used the same password on multiple machines without issue.

from geemusic.

Sounds great. I'll post an update with the results, hopefully by later today.

from geemusic.

Alright I've got a quick update.

I ran through the setup to get my laptop running the server and it works perfectly. Quick responses every time and not a single "skill took too long" response. The laptop I have is a pretty cheap dual core that I use for basic coding stuff but it was still significantly faster than the raspberry pi, which was especially noticeable when doing the installation. My laptop took about 5 minutes and the raspberry pi takes about 20 minutes.

I had previously been using one of the original raspberry pi's but I got a model 3 for Christmas that is supposed to be quite a bit faster. I will try setting that one up as the server at some point and see if that works better.

from geemusic.

Glad to hear you got it up and running. Sucks that it isn't working on the original Pi but hopefully you'll have better luck with the 3rd gen chip.

I'm going to close this issue for now, but feel free to comment again letting us know if you have better luck!

from geemusic.

So it appears that the original pi was the culprit here. I got my rpi 3 set up and it works just fine. I guess this software is more computationally demanding than I thought! Might be worth dropping a note about the original Pi not working into the readme. I could see a lot of people thinking the pi would be a perfect candidate for this sort of project.

from geemusic.