Well, i just found a workaround: i have a raspberry PI with volumio … i took the youtube directory from plugins directory with winscp and copied into x86 volumio. At that point i enabled plugin, and VOILA, working !
Hi Sepherim,
I am aware of the problem and I will be looking into it as soon as I have a moment.
I will make sure to update this thread once it is fixed.
This is a really good plugin that many people use. Thank you for your work and support.
If we exceed the limit, will we have to pay a monthly fee or pay a one-off fee to Google?
Creating your own api key would be complicated for plugin users?
It is a good idea to keep a list of polled music, because if I choose something from the plugin’s polled list and I click to my playlist and then go back to the plugin’s polled list, the list is no longer visible and you need to change a character in the search field and retrieve it to appear in the list generates unnecessary queries.
I think today we’ve again exceeded Google API’s quota.
I installed Volumio yesterday and spent the whole evening trying to figure out why the Youtube plugin doesn’t work. Glad that I found this thread and now know why - just checked my logs, I have the “daily limit exceeded” problem as well.
Would be awesome if you guys could add the possibility that I can enter my own API key as well. I think that users that run software like Volumio should be able to do this and I assume this is the easier solution to fix this than to get a paid solution for everybody?
Thanks for maintaning this plugin, hope I can use it soon!
Would it make sense to at least offer users the option to generate your their own key and enter it.
If the user doesn’t enter the key then they fall back and default to the shared API key. It could be under a hidden “Advanced configuration” section in the UI that just overrides the default.
I completely agree that expecting every user to create their own key isn’t a suitable solution. But allowing users to enter their own key, would:
a) allow more technical users an option to continue use when the API limit is hit.
And b) potentially reduce the load on the shared API key by removing the number of users utilising it.
I’m sure if you shared some step by step instructions for creating a key, the majority of Volumio users would be technical enough to follow and understand it if they wanted to. But those that can’t would still just use the shared key by default if don’t decide to configure anything.
To the plugin author: Congratulations on the heavy usage! Well past free tier pretty often : )
To the users: This plugin works great, but indeed does often run out of free API usage due to so many users. It is entirely possible, if you have a google account, to create project credentials yourself to access the youtube API without using the build in volumio-youtube key. Some brief instructions are below.
Activate the API
Uninstall the Youtube plugin, then reinstall it, then reboot your volumio. Don’t ‘enable’ the plugin yet.
Log into google developer section at https://console.developers.google.com. You might have to activate a new project, or your account in some way, that I had already done.
Find the API library, and search for and enable Youtube data API v3.
You are 1/3 of the way done.
Create credentials
Create a new project, named something like volumio-youtube-yourusername
Use the google developer page to add credentials for this project. Select the youtube data API you just enabled. It will say lots of things about oauth2, and the like. If you have to choose an access category, webserver should work fine.
Download the resulting credentials in json format. It will probably be called client_id.json or similar.
You are now 2/3 done.
Edit the auth.json file for the plugin
Copy the /data/plugins/music_service/youtube/auth.json file off your volumio
Edit it in a text editor, and replace all the matching fields with the data from your client_id.json file, except the redirect.
Copy the file back into your volumio at the correct location:
/data/plugins/music_service/youtube/auth.json
Enable the youtube plugin. Copy the code displayed as previously, into google.com/device
Leave the youtube plugins settings page, then go back in. It should successfully authenticate.
Done
You now have a (mostly) functioning youtube plugin. Depending how you configure your project, accessing user account data may not work, but public results should always function. You’ll have enough free API usage for your personal use, I’m sure.
Don’t paste your client secret anywhere on the internet unless you want other people using your API credit.
If you update the youtube plugin, your changes will get blown away - so save the auth.json file you create. Maybe the author will add expert settings for you to plug in your own values for client_id and client_secret - but it is too much generally to expect users to deal with these values and API registration. If I was the developer I’m would probably have other higher priorities.
Thanks for the tips and the well documented how-to.
I just followed the steps as described but I get stucked on the plugin settings page where the code zone remains empty.
Any idea on what I forgot ?
I got stuck at the same point as edwin69.
After looking into it, i changed the “ytapi_key” in the index.js (same folder) and kept the original auth.json. (I think you will need to deinstall and restart … and then make the change in the index.js)
I see now my requests in the google console, so this seems to work. For this you need to create an api key and not a oauth-client-id.