-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gmusicapi version check thinks v10 is older than v4 #100
Comments
i get the same message and it's frustrating. |
The Find where it checks for the version and remove it, as described above :) |
I'm doing active development on this plugin at https://github.com/squeezebox-googlemusic/squeezebox-googlemusic - hechtus is MIA. This issue is fixed in my repo. |
Cant get this plugin to load at all on Vortexbox 2.4 Installed all the bits needed but it wont load the plugin up at all, just get this error in the log [16-07-10 16:40:41.4006] Slim::bootstrap::tryModuleLoad (286) Warning: Module [Plugins::GoogleMusic::Plugin] failed to load: |
When trying to wrestle with getting Google Music working on my Pi as once again it stopped working, I installed the latest gmusicapi which is now at version 10.
This causes the plugin to say:
A more recent version of the Python package "gmusicapi" is required. Please install at least version 3.1.0 and restart Logitech Media Server.
You can remove this check by editing the Plugin.pm file line 61
I tried changing '4.0.0' to '15.0.0' which didn't seem to work as i expected it.
So I ended removing the conditional for the version completely.
This didn't fix the signing in issues though. The problem is with the 2FA and or application passwords.
I gave up and created a new Google account and uploaded all my music to the new account.
This doesn't have 2FA and so far it is logging on every time.
Not ideal, and I might have a sit down and try to figure out what the problem is with the current plugin. But the constant restarting of the media server every time i changed something was driving me mad. Is there another way for force a reload of the plugins without a full restart?
The text was updated successfully, but these errors were encountered: