Posts: 455
Joined: Oct 2012
Reputation:
42
AFAIK we use standard https, port 443.
Posts: 142
Joined: Oct 2012
Reputation:
0
I tried it on the latest Gotham nightly last night and 13 is working fine.
Posts: 49
Joined: Dec 2012
Reputation:
0
I'm wondering if I have fallen foul of Google's dictum that you may only deauthorise 4 devices a year.
Funnily enough my YouTube plugin failed last night. Something I rectified by copying the old settings.xml file into userdata/add_on_settings
I'm now wondering if copying any values from that into the Google Music plugin's setting file would help?
Posts: 49
Joined: Dec 2012
Reputation:
0
One weird thing I've noticed and it may be Android specific but, after each unsuccessful attempt to run this plugin my volume is set to 0!
Posts: 455
Joined: Oct 2012
Reputation:
42
crocodilezzz, the addon is failing to authenticate, have you generated an application-specific password?
Posts: 455
Joined: Oct 2012
Reputation:
42
Application-specific password is only needed when you use two-factor authentication.
crocodilezzz, and then it failed with 'invalid credentials' again? and if you open the addon settings, the credentials are empty? and after you enter them? on the next boot they still there?
The addon settings should be stored in /home/pi/.xbmc/userdata/addon_data/plugin.audio.googlemusic/settings.xml, please check if it is being created and has your settings.
Posts: 49
Joined: Dec 2012
Reputation:
0
Ah. Thanks foreverguest. My usernane and password are stored in Settings.xml but no authorisation key or device ID, which is what I expected to see after looking at the YouTube plugin's setting file.