I unloaded and reloaded last stable version (v. 1.1.5) but still no playback. Logs at http://logs.volumio.org/volumio/HyNb6fq.html indicate there is a playback bug and to contact you.
Jul 18 09:01:33 musicbox2 volumio[949]: InnertubeError: Something went wrong at PlaylistExpandableMessage!* *Jul 18 09:01:33 musicbox2 volumio[949]: This is a bug, please report it at https://github.com/patrickkfkan/Volumio-YouTube.js/issues
Might have to reflash and reload but I will check on my other player to confirm.
I am confused. Your screenshot shows YouTube2 plugin, and you said you updated to latest beta version, but then you said you unloaded and reloaded latest stable. So in other words you are running v1.1.5, a version which is known to have issue with playback.
So I checked your logs and there was no mention of YouTube2 plugin at all. They do mention the YT Music plugin, which you have v1.1.0 installed – again, a version known to have playback issues. v1.1.1 (beta) is what you need to be running.
Also, if you are having issues with beta version, check that you have in fact installed it properly through the following steps:
Sorry I may have posted on the wrong thread but I’m using the YouTube plugin not YouTube2 and I’m installing using the steps indicated. I will recheck, try again and get back to you.
Thank you for your prompt response and your continuing efforts in keeping the plugins updated.
v1.1.1 has been in the beta channel for more than a week… you probably missed it because you didn’t arrive at this thread sooner and Volumio made installation of beta plugins as convoluted as it can be.
I am new to Volumio. Had installed the Youtube Music Plugin (1.1.1) couple of days back. It worked fine for a day or two. But from yesterday it is not working. If I click on the Play button of one of the songs in search results, it shows an error in the orange colored box, as somebody else had posted here earlier. Any help?
Thanks. I tested the signing in with v1.1.3. It still didn’t automatically sign in after a restart, but it did so as soon as I went into the plugin’s settings. Previously I needed to toggle disable/enable to do that.
The plugin only signs in when you access its settings or begin browsing. This is to avoid the past situation where a bug in the sign-in process froze the entire setup.