music-assistant / hass-music-assistant

Turn your Home Assistant instance into a jukebox, hassle free streaming of your favorite media to Home Assistant media players.
Apache License 2.0
1.39k stars 51 forks source link

Apple Music error in RC3 #2649

Closed Kebo2r closed 3 months ago

Kebo2r commented 4 months ago

What version of Music Assistant has the issue?

2.1.0 RC3

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

2024.7.3

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

The problem

Downloaded the beta yesterday. Now getting this error when trying to play Apple Music:

2024-07-20 07:28:53.597 ERROR (MainThread) [music_assistant.webserver] Error handling message: player_queues/play_pause: ClientSession._request() got an unexpected keyword argument 'encoded'

Worked fine in the previous couple of betas. Have deleted, reinstalled, reconfigured, etc. Local Media works.

Thanks!

How to reproduce

Add Apple Music provider. Attempt to play any media. See error.

Music Providers

Apple Music

Player Providers

Fully Kiosk, SnapCast

Full log output

music-assistant.log

Additional information

Other providers work ok and Apple Music worked fine in RC2

What version of Home Assistant Core are your running

2024.7.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)

chasut commented 4 months ago

Seeing this as well. Apple Music over Airplay on AArch64 HA add-on.

bushcraftytim commented 4 months ago

Yes - seeing this in RC3 too.

davidlarkins commented 4 months ago

I am also seeing this error with playing anything from Apple Music on RC3.

OzGav commented 4 months ago

This will be fixed in then next update.

davidlarkins commented 4 months ago

Can confirm this is fixed in 2.2.0b0. Thanks!

Kebo2r commented 4 months ago

Confirmed! Fixed and working!  Thank you!Sent from my iPhoneOn Jul 22, 2024, at 12:38, davidlarkins @.***> wrote: Can confirm this is fixed in 2.2.0b0. Thanks!

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>