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

HA Supervisor warning related to enable_uvloop not existing in the schema for Music Assistant Server Beta #3477

Closed
1 task done
AlainPeccable opened this issue Jan 18, 2025 · 6 comments

Comments

@AlainPeccable
Copy link

What version of Music Assistant has the issue?

2.4.0b17

What version of the Home Assistant Integration have you got installed?

No response

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

  • Yes

The problem

Warning in supervisor:
WARNING (MainThread) [supervisor.addons.options] Option 'enable_uvloop' does not exist in the schema for Music Assistant Server (beta) (d5369777_music_assistant_beta)

How to reproduce

Unknown

Music Providers

Not sure it could be related but I use YTMusic & Radio

Player Providers

N/A

Full log output

music-assistant.log

Additional information

No response

What version of Home Assistant Core are your running

2025.1.2

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Alternative

@marcelveldt
Copy link
Member

You probably have the addon installed for a while already ? Like more than a year ?
We had that uvloop setting in a very old version of the addon, I think there is still some leftover in your case.
I think it would be sufficient to simply set some setting of the addon (e.g. loglevel) different, save that and change it back to "reset" the config.

@AlainPeccable
Copy link
Author

Indeed I have it for quite some time.

I tried the suggested solution, but this warning come back in Supervisor. I may try then to fully remove it and reconfigure from scratch.

@OzGav
Copy link
Contributor

OzGav commented Jan 27, 2025

Any updates on this?

@OzGav
Copy link
Contributor

OzGav commented Jan 31, 2025

This will be closed soon due to no follow up

@AlainPeccable
Copy link
Author

Didn't had time to fully remove it and reinstall. I'm now running the last beta but this remains in the supervisor log. I'll proceed today with the uninstall (keeping parameters) and reinstall.

@AlainPeccable
Copy link
Author

Solved after uninstalling and reinstalling the server.... reconfiguring everything is a bit painful and not yet completed.

Example: You can't choose a custom name for the provider during the config, so you add the account/cookie save then have to edit back to put a custom name. (I have 6 YoutTube accounts ... 🦖 )

It doesn't find any of my players (TV, Onkyo, Google Speakers).
When I uninstalled the server I didn't remove the integration... it discovered a new MA integration after the reinstallation of the server. Previous integration was still there with the various players, so I removed it and try to configure again but no players.

I'll check back the doc to see what I missed but now it's synchronizing several thousand tracks from filesystem so I let it first complete. 2h that I'm on this so little pause.

As the original reported issue is solved this can be closed...

@OzGav OzGav closed this as completed Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants