Skip to content
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

Fixes for mopidy install script #19

Closed
sandyjmacdonald opened this issue Feb 4, 2020 · 10 comments
Closed

Fixes for mopidy install script #19

sandyjmacdonald opened this issue Feb 4, 2020 · 10 comments
Assignees

Comments

@sandyjmacdonald
Copy link
Member

  1. Pending a new release of Iris on PyPI, do the following in the install script:

python3 -m pip install https://github.com/jaedb/Iris/archive/develop.zip

  1. Add support in the config file for the changed button pin in newer revisions of the Pirate Audio boards (more info in Add BCM24 to button config to support newer Pirate Audio boards #16 ):

bcm24 = volume_up,active_low,250

  1. Remove lines with semicolon comments in the config file, as they seem to bork it in more recent Mopidy versions.
@sandyjmacdonald
Copy link
Member Author

Until a release of Iris on PyPI, you can give this modified install script a go, which does the above. It works for me on the latest version of Raspbian Buster (2019-09-26).

https://gist.github.com/sandyjmacdonald/b72b65d827d85166b4739e12867d9e1b

@jplegat
Copy link

jplegat commented Feb 7, 2020

It did work on a clean Buster installation.

However, following the instructions on https://learn.pimoroni.com/tutorial/sandyj/getting-started-with-pirate-audio to add local files doesn't work because the Mopidy-Local extension was not installed in the process.

sudo python3 -m pip install Mopidy-Local did the trick.

Thanks for updating the script!

@GregJohnStewart
Copy link

GregJohnStewart commented Feb 11, 2020

Sounds like that should be part of the script then? Worked mostly, except the default http config is broken. (doesn't seem to like a blank hostname). Also kind of stuck on fixing this, as i'm new to this, if someone could tell me the magic value to put for the hostname that would be cool :)

For reference, getting the "Must be a resolvable hostname or valid ip" message when the ip is set to 0.0.0.0

@blomsoft
Copy link

I use the IP address i.e. 192.168.1.42 in my case.

@Gadgetoid
Copy link
Member

I could swear that 0.0.0.0 worked for me. It certainly did in Mopidy 2.x so this is probably a Mopidy bug. I have a vague recollection of this being discussed elsewhere, but my git-search-fu is not serving me well today.

@GregJohnStewart
Copy link

GregJohnStewart commented Feb 13, 2020

Figured it out, it did like 0.0.0.0, but I noticed this issue: mopidy/mopidy#1868

After removing the inline comment it worked just fine.

Gadgetoid added a commit that referenced this issue Feb 13, 2020
@Gadgetoid
Copy link
Member

Aha, that's the one- thank you! In all this chaos I'd forgotten to remove the inline comments that Mopidy 3.x broke.

@blomsoft
Copy link

Thanks, confirmed to work with 0.0.0.0 without inline trailing comment.

@kristerj
Copy link

This is super helpful. To sum up, to get running on a fresh buster install with the steps in the tutorial that expect the local module:

  1. Install python3
  2. Modify install script
    -install from develop.zip
    -remove semicolons
    -pin change
  3. Pip install local module

Is that correct?

@Gadgetoid
Copy link
Member

You should be able to combine 2. into just "run the install script" since Mopidy Iris is now released onto PyPi and i've fixed the config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants