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.

Sign up for GitHub

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

Jump to bottom

Cannot install Music Assistant system integration #1111

Closed
downeymj opened this issue Mar 2, 2023 · 11 comments
Closed

Cannot install Music Assistant system integration #1111

downeymj opened this issue Mar 2, 2023 · 11 comments
Labels
triage

Comments

@downeymj
Copy link

downeymj commented Mar 2, 2023

What version of Music Assistant has the issue?

2023.2.1

The problem

Unable to successfully install Music Assistant. The instruction process fails at the step of installing the system integration.

How to reproduce

  • Download Music Assistant via HACS integrations
  • Restart HA per instruction
  • Under HA's Settings > Devices & Services > Integrations > Add Integration, choose "Music Assistant".

Expected behavior:

  • Configuration wizard appears to set up integration.

Actual behavior:

  • Dialog box appears "Please wait, starting configuration wizard for Music Assistant" with spinner, but hangs.
  • Eventually, the following Error appears: Config flow could not be loaded: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html>

Relevant log output

Logger: homeassistant.util.package
Source: util/package.py:107
First occurred: 03:37:44 (3 occurrences)
Last logged: 03:38:10
Unable to install package music-assistant==1.8.7.4: ERROR: Cannot install music-assistant because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip is available: 23.0 -> 23.0.1 [notice] To update, run: pip install --upgrade pip

Additional information

N/A

What version of Home Assistant Core are your running

Home Assistant 2023.3.0; Supervisor 2023.01.1; Operating System 9.5; Frontend 20230301.0 - latest

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Raspberry Pi
@downeymj downeymj added the triage label Mar 2, 2023
@OzGav
Copy link
Contributor

OzGav commented Mar 2, 2023

This is an issue with HA core. MA is incompatible with > HA 2023.2.x
Downgrade or wait for MA 2.0
#1104

@OzGav OzGav closed this as completed Mar 2, 2023
@downeymj
Copy link
Author

downeymj commented Mar 2, 2023

Eek, that's unfortunate to hear. Thanks for the info.

Is the MA 2.0 code in a different repo than this one? I didn't find a branch or anything here.

@OzGav
Copy link
Contributor

OzGav commented Mar 2, 2023

Not yet released. Will be another week or so.

@downeymj
Copy link
Author

downeymj commented Mar 2, 2023

Yeah, I understand there isn't a release available yet. I was wondering where we can find the code in its current state of development. The last commit to the main branch in this repo was 2022-12-08 so I figured it must be in some other repo?

@OzGav
Copy link
Contributor

OzGav commented Mar 2, 2023

Yeah sorry its not publicly available at this time.

@downeymj
Copy link
Author

downeymj commented Mar 2, 2023

That's ... odd.

Is there a reason it's being developed in secret?

@OzGav
Copy link
Contributor

OzGav commented Mar 2, 2023 •
edited
Loading

Secret is a totally inappropriate word to describe it. Marcel is working on it by himself as well as his actual job. He doesn’t have 36 hours in a day and so has not had time to properly setup the new repo

@marcelveldt
Copy link
Member

This project consists of several repos which all together form Music Assistant. The "core" of MA is being rewritten to 2.0 version which shall be released in a beta soon. Nothing secret about it, just multiple repos and branches. Also wondering why it is so important. There's nothing you can do now to get 2.0 working anyway

@cociweb
Copy link

cociweb commented Mar 2, 2023 •
edited
Loading

This project consists of several repos which all together form Music Assistant. The "core" of MA is being rewritten to 2.0 version which shall be released in a beta soon. Nothing secret about it, just multiple repos and branches. Also wondering why it is so important. There's nothing you can do now to get 2.0 working anyway

Because, I think, the guys would like to help (at least with a workaround patch) and keep it working with the latest Ha Core (on the release day as well) :)
The last 3 Ha Core update made the integration unusable for the first days/weeks.
Eg. I would like to keep the 2023.03 as it is now, but MA<2.0 broke now... I don't see neither where is the dependcy implemented to make a trial fork for myself of the <2.0 version... May, the overwhelming majority of the community are more appreciate the stable and working versions than the new (but instable) features -which later (after beta release) become stable- because most of us is a HA user rather than a HA developer. And it is painful for a user, if a something not working after to upgrade to the latest release (especially if they put their own effort on the automatism to keep every component on the latest available and released version)
Please don't misunderstood it: what are you doing is incredibly awsome!!! Please keep it doing!

@marcelveldt
Copy link
Member

marcelveldt commented Mar 2, 2023 •
edited
Loading

  1. Music Assistant (v1.x) uses the databases package for all database access, which is in turn based on SqlAlchemy Core.

  2. Home Assistant updated to sqlalchemy 2.0 which is not compatible with the databases package: SQLAlchemy 2.0 encode/databases#530

  3. Music Assistant 2.0 is in the making for about half a year now and it is partly rewritten. Most important change is that its "core" will be addon/docker based so it will be detached from HA, so we no longer have to suffer from this kind of dependency conflicts. The HA integration part will just be a "dumb" connector.

  4. The v2.0 is not yet in a shape where somebody can test it, please allow me to publish a first beta version.

My wish was to provide another fix/patch release for Music Assistant 1.x for HA 2023.3+ support but as you can read in the linked issue above, that is going to be hard unless someone patches databases for the SQLAlchemy...

@cociweb
Copy link

cociweb commented Mar 2, 2023 •
edited
Loading

Thank you Marcel,
I think it is a very clear and understandable communication: the excuse is reasonable.
Let's hope someone of us has the proper knowledge to provide SQLA2.0 patch. If not, until that, let me wish time for You, and patience for us - without bother of you - to bring us an awesome release again! (Hint: pin the issue as an announcement to minimize the number of the reopens. - Never mind: it was pinned half an hour ago)

Furthermore, let us know, if you can delegate sub-tasks and need further help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cociweb @marcelveldt @OzGav @downeymj