Forget my last post, i made some stupid mistakes. At the moment i’ve installed your latest uptdate, whent true all the steps creating credentials and inserted them in the plugin settings. Unfortunately i don’t see anything changing in the account acces, no code will appear. Am i still missing something?
So what do you see under Account Access? If you don’t see the code refresh after entering your credentials, you can click Back and then enter the plugin settings again. You should see the new code there.
Don’t know why but it just keeps saying: “Code not yet available. Please come back later.” I made the credentials this morning, is there like a period of time before they become active? or should it work right away?
The credentials become active right away. When the plugin starts, it contacts Google’s authentication server to obtain the Code if access to YouTube has not been granted. If you get “Code not yet available. Please come back later”, the reason is likely to be one of the following two:
Request has not been made to Google’s auth server
Request made, but no response received
Reason 1 is highly unlikely, given the plugin can been started successfully. Reason 2 is more likely here. Could you check the logs and see if the plugin shows any errors?
This is a fantastic looking plugin. But I have a problem. I can’t get it to make any sound!
I know my system is working: spotify connect and spotify both play correctly. I was able to install your plugin using your instructions and have been able to connect to youtube and retrieve my liked videos, subscriptions etc. So I am confident that the google API side of things is good too.
But when I try to play a track, even though I get the volumio notification, there is no sound. The play symbol stays at “arrow” and does not change to “pause”. And the track time counter stays at 0:01 secs.
curl: (60) SSL certificate problem: certificate is not yet valid
more details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the cerificate, use
the -k (or --insecure) option.
Victory!! Works like charm now. Thanks a lot for helping me out. However i had to configure the date and time manualy with “sudo date -s”, for some reason time and date don’t reconfigure using “dpkg-reconfigure” or “sudo raspi-config”. Anyway, nice job helping me out!
Hi, I installed Youtube login and verified on 3th of Dec, it was work like charm. For some reason, I formatted and re-install Volumio > Youtube plugin, when I pasted the code to google.com/device, it’s say:
“Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In”
I tried to search for solution it’s the answer almost “it’s cannot fix, it’s about developer’s site”
Does anyone experience this issue like me? Sorry for my bad English.