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

MA doesn’t work with HA 2023.3.x was: Dependency conflict on HA 2023.3 beta #1104

Closed
Mariusthvdb opened this issue Feb 23, 2023 · 46 comments
Closed
Labels
dependencies Pull requests that update a dependency file wontfix This will not be worked on

Comments

@Mariusthvdb
Copy link

Mariusthvdb commented Feb 23, 2023

What version of Music Assistant has the issue?

2023.2.1

The problem

probably getting used to this, just mentioning for reference.

How to reproduce

update to HA 2023.3

Relevant log output

2023-02-23 00:14:51.945 ERROR (SyncWorker_10) [homeassistant.util.package] 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

No response

What version of Home Assistant Core are your running

2023.3

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Generic x86-64 (e.g. Intel NUC)

@Mariusthvdb Mariusthvdb changed the title Dependency conflict o HA 2023.3 beta Dependency conflict on HA 2023.3 beta Feb 23, 2023
@OzGav
Copy link
Contributor

OzGav commented Feb 23, 2023

Thanks. Marcel will have a look. This might even get overtaken by v2 but not sure.

@varungujjar
Copy link

Just tried to install I get the same error, kind of found that its the sqlalchemy version, HASS Recorder uses SQLAlchemy 2.0.4 but MASS demands for sqlalchemy-1.4.46. I tried to fix but get the following error

Traceback (most recent call last):
File "/home/pi/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/home/pi/config/custom_components/mass/init.py", line 197, in async_setup_entry
raise exc
File "/home/pi/config/custom_components/mass/init.py", line 190, in async_setup_entry
await mass.setup()
File "/home/pi/env/lib/python3.10/site-packages/music_assistant/mass.py", line 79, in setup
await self.database.setup()
File "/home/pi/env/lib/python3.10/site-packages/music_assistant/controllers/database.py", line 43, in setup
await self._migrate()
File "/home/pi/env/lib/python3.10/site-packages/music_assistant/controllers/database.py", line 188, in _migrate
if prev_version := await self.get_setting("version"):
File "/home/pi/env/lib/python3.10/site-packages/music_assistant/controllers/database.py", line 53, in get_setting
return db_row["value"]
File "lib/sqlalchemy/cyextension/resultproxy.pyx", line 67, in sqlalchemy.cyextension.resultproxy.BaseRow.getitem
TypeError: tuple indices must be integers or slices, not str

@marcelveldt
Copy link
Member

I will not fix it anymore this time. V2 launch is very soon and then we can say goodbye to these kind of dependency conflicts forever. So for now, stick with previous HA or live a while without MA ;-)

I am really working on the last bits of MA v2.0 so keep an eye on discord for the beta instructions.

@erkr erkr added wontfix This will not be worked on dependencies Pull requests that update a dependency file and removed triage labels Feb 25, 2023
@OzGav OzGav pinned this issue Mar 2, 2023
@OzGav OzGav changed the title Dependency conflict on HA 2023.3 beta MA doesn’t work with HA 2023.3.x was: Dependency conflict on HA 2023.3 beta Mar 2, 2023
@OzGav
Copy link
Contributor

OzGav commented Mar 9, 2023

Impossible to say with certainty but days to weeks not months.

@Aasikki
Copy link

Aasikki commented Mar 9, 2023

I will not fix it anymore this time. V2 launch is very soon and then we can say goodbye to these kind of dependency conflicts forever. So for now, stick with previous HA or live a while without MA ;-)

I am really working on the last bits of MA v2.0 so keep an eye on discord for the beta instructions.

Hopefully V2 will be awesome! I always update on day one, so going without it for now, but it was always giving me issues with yotube music anyways, so here's hoping V2 will be smoother!

@userMak
Copy link

userMak commented Mar 11, 2023

Impossible to say with certainty but days to weeks not months.

make it days please :)

@Aasikki
Copy link

Aasikki commented Mar 11, 2023

Impossible to say with certainty but days to weeks not months.

make it days please :)

Hey now, not cool to hurry up someone doing awesome stuff for free :)

@OzGav
Copy link
Contributor

OzGav commented Mar 11, 2023

https://github.com/music-assistant/home-assistant-addon

V2 is available . Note that it is still in beta so other issues may arise.

@userMak
Copy link

userMak commented Mar 11, 2023

https://github.com/music-assistant/home-assistant-addon

V2 is available . Note that it is still in beta so other issues may arise.

do we have to uninstall the previous version?

@OzGav
Copy link
Contributor

OzGav commented Mar 11, 2023

You need to temporary disable the MA integration in HA, they can be installed at the same time but not run at the same time.

Make sure to not run HA slimproto integration and/or LMS at the same time as MA 2.0

@DidibabaQiu
Copy link

https://github.com/music-assistant/home-assistant-addon

V2 可用。請注意,它仍處於測試階段,因此可能會出現其他問題。

Thank you for your selfless dedication

@znack14
Copy link

znack14 commented Mar 12, 2023

"This add-on is incompatible with your device's processor or the operating system you have installed on your device"
What shall I do? Is raspberry pi 3 support planned?

@OzGav
Copy link
Contributor

OzGav commented Mar 12, 2023

Are you running the 32 bit version of the OS?

@znack14
Copy link

znack14 commented Mar 12, 2023

Вы используете 32-битную версию ОС?

yes i have a small raspberry pi 3

@OzGav
Copy link
Contributor

OzGav commented Mar 12, 2023

There is a 64bit version of HA for the Raspberry Pi 3. I am assuming that is why you can’t install the add on

@znack14
Copy link

znack14 commented Mar 12, 2023

Для Raspberry Pi 3 существует 64-битная версия HA. Я предполагаю, что именно поэтому вы не можете установить надстройку

yes I have armv7L. But there will be no other. It is bad that it is not installed.

@OzGav
Copy link
Contributor

OzGav commented Mar 12, 2023

Not sure. This says the raspberry pi 3 has an arm v8 https://pi.processing.org/technical/

There is a 64bit version of the HAOS for the raspberry pi 3

@znack14
Copy link

znack14 commented Mar 12, 2023

Ах, вычислительный модуль! Хорошо, тогда я спрошу у разработчиков, но я не думаю, что MA будет работать с 32-битной версией. Я подтвержу для вас.

thank you

@music-assistant music-assistant deleted a comment from userMak Mar 12, 2023
@OzGav
Copy link
Contributor

OzGav commented Mar 12, 2023

@znack14 Sorry MA V2 will not run on your hardware. 1GB RAM is not enough as HA alone needs that. To run HA and MA together the advice is:
Minimal rpi4 (or comparable), no rpi 3
64 bits cpu and OS
absolute minimum of 2gb memory, 4 gb or higher recommended

@FedericoBS
Copy link

FedericoBS commented Mar 12, 2023

I can not find the advanced option on the queue in the beta version. i need to disable the icy metadata to avoid stuttering. Can you help?
In the beta version i can not adjust the group volume as in the previous.

@OzGav
Copy link
Contributor

OzGav commented Mar 12, 2023

ICY metadata has been left out of the current beta as there should be no need for such advanced settings to begin with. Marcel said he can add them back if there really is a demand/need. Is the issue exactly the same or does the music just stutter sometimes ? Stuttering has nothing to do with ICY. A lot of awful noise does.

@jurgenhaas
Copy link

How can I install this AddOn if I'm running HA in Docker, i.e. without supervisor?

@OzGav
Copy link
Contributor

OzGav commented Mar 13, 2023

Have a look at post 2 in the beta channel https://discord.com/channels/753947050995089438/1083643113484070953

@jurgenhaas
Copy link

Mmph, I need Discord??? My goodness, this is one of the worst platforms wrt privacy. Nayways, I logged into an account but the link responds with "No text channels". Is it too much to ask for providing required information here in the repo?

@OzGav
Copy link
Contributor

OzGav commented Mar 13, 2023

Just trying to save the duplication..

HOW TO INSTALL/RUN THE BETA OF 2.0 ?

Preferred method: Home Assistant Add
By far the most convenient way to run the Music Assistant Server is to install the Music Assistant Add-on:

Add the Music Assistant repository to your Home Assistant instance.
Install the Music Assistant add-on.
Add repository on my Home Assistant

Click the link below to add the Music Assistant repository to HA:
https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fmusic-assistant%2Fhome-assistant-addon

Alternative method: Docker image
An alternative way to run the Music Assistant server is by running the docker image:

docker run --network host ghcr.io/music-assistant/server

You must run the docker container with host network mode and the data volume is /data. If you want access to your local music files from within MA, make sure to also mount that, e.g. /media. Note that accessing remote (SMB) shares can be done from within MA itself using the SMB File provider.

@jurgenhaas
Copy link

Thanks a lot @OzGav much appreciated. The problem with that link is that it only works when HA is run with supervisor, otherwise that link doesn't work, right?

So I have to go with the separate docker image, which is fine too.

@schoenwaldnils
Copy link

Is the V2 the default when adding it via this link?
I still get the same error as before.
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

@gaussey
Copy link

gaussey commented Mar 13, 2023

Just trying to save the duplication..

HOW TO INSTALL/RUN THE BETA OF 2.0 ?

Preferred method: Home Assistant Add By far the most convenient way to run the Music Assistant Server is to install the Music Assistant Add-on:

Add the Music Assistant repository to your Home Assistant instance.
Install the Music Assistant add-on.
Add repository on my Home Assistant

Click the link below to add the Music Assistant repository to HA: https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fmusic-assistant%2Fhome-assistant-addon

Alternative method: Docker image An alternative way to run the Music Assistant server is by running the docker image:

docker run --network host ghcr.io/music-assistant/server

You must run the docker container with host network mode and the data volume is /data. If you want access to your local music files from within MA, make sure to also mount that, e.g. /media. Note that accessing remote (SMB) shares can be done from within MA itself using the SMB File provider.

So Mass is now an separate addon rather than a HACS addon?

I assume this excludes the use of HomeAssistant media players which was the main reason for using it, I currently use it to play to a Yamaha receiver which is no longer accessible, the only thing it’s seeing is my pc as a “Chromecast”.

edit: it’s now seeing my Yamaha receiver, how do you add a network share as a provider?
Previously I had to mount my network share inside hass. Also, does anyone have an automation example that would play a playlist using MASS V2 on an a receiver?

@OzGav
Copy link
Contributor

OzGav commented Mar 13, 2023

So I have to go with the separate docker image, which is fine too.
Yes docker for you

@OzGav
Copy link
Contributor

OzGav commented Mar 13, 2023

Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

You need to disable or remove the existing integration then install the new add on.

@OzGav
Copy link
Contributor

OzGav commented Mar 13, 2023

edit: it’s now seeing my Yamaha receiver, how do you add a network share as a provider? Previously I had to mount my network share inside hass. Also, does anyone have an automation example that would play a playlist using MASS V2 on an a receiver?

V2 has samba shares as a provider now so mounting not required
Current,y there is no HA integration so automations don’t work. Expect the integration in about a week.

@Tech33
Copy link

Tech33 commented Mar 13, 2023

@znack14 Sorry MA V2 will not run on your hardware. 1GB RAM is not enough as HA alone needs that. To run HA and MA together the advice is: Minimal rpi4 (or comparable), no rpi 3 64 bits cpu and OS absolute minimum of 2gb memory, 4 gb or higher recommended

I am also on same boat with rpi 3 :( would be soo great if you can fix V1 for backwards Compatibility

@OzGav
Copy link
Contributor

OzGav commented Mar 13, 2023

I’m sorry but it is impossible to fix V1 as this is due to HA changes not MA

@andrewigali
Copy link

Installed the v2 beta on Rspberry4 Argon One HAOS 2023.3.3, Supervisor 2023.03.1, but can't running. Clicked the Start button, but nothing happened. No error on log and i can't sett.
The old HACS version can't loading, not work. :(
I restored to an earlier system version, but not helped.
Now the Music Assistant doesn't work at all. :(

@OzGav
Copy link
Contributor

OzGav commented Mar 14, 2023

You can’t have both running at once. Make sure V1 integration is disabled or removed prior to trying to start the add on

@andrewigali
Copy link

You can’t have both running at once. Make sure V1 integration is disabled or removed prior to trying to start the add on

Unfortunately, it doesn't work even if I disable Music Assistant in the Settings Devices & Services menu.
Can someone make a video on how to switch from the no longer working Music Assistant to the new version?

@OzGav
Copy link
Contributor

OzGav commented Mar 14, 2023

There was an issue with one of the beta. Which beta do you have installed? Make sure you have the latest.

@andrewigali
Copy link

andrewigali commented Mar 14, 2023

There was an issue with one of the beta. Which beta do you have installed? Make sure you have the latest.

2.0.0b4

In Music Assistant log:
IMG_20230314_075003

The speakers are Google Nest Audio.
But doesn't work. :(

@OzGav
Copy link
Contributor

OzGav commented Mar 14, 2023

I think you should open a separate issue for us to step through this. The screen capture above shows MA working. It has started and has found your players. So you saying it doesn’t work is not clearly explaining what isn’t working.

@andrewigali
Copy link

This is the problem:
Screenshot_2023-03-14-10-54-25-884_io homeassistant companion android

Screenshot_2023-03-14-10-54-37-971_io homeassistant companion android

IMG_20230314_110613

@OzGav
Copy link
Contributor

OzGav commented Mar 14, 2023

As I said above please open a separate issue. I will remove the above posts soon to reduce this thread length. Just add all that you posted above.

@marcelveldt
Copy link
Member

closing this in favor of #1143

@marcelveldt marcelveldt closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2023
@marcelveldt marcelveldt unpinned this issue Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests