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.21k stars 44 forks source link

Unable to locate RAOP Play binary for linux/aarch64 #2442

Closed chasut closed 2 weeks ago

chasut commented 2 weeks ago

What version of Music Assistant has the issue?

2.1.0b4

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

2024.5.1

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

The problem

After update to the latest beta, attempted to select an airplay player and received this error. "Unable to locate RAOP Play binary for linux/aarch64".

How to reproduce

Setup airplay or attempt to play to existing airplay player.

Music Providers

NA

Player Providers

Airplay

Full log output

log.txt

Additional information

Log is from fresh uninstall/re-install of the add-on. I did a full uninstall and reinstall of the add-on as well as custom integration. HAOS on M2 Mac, so generic-aarch64

What version of Home Assistant Core are your running

2024.6.2

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

macOS

Frederick-G764 commented 2 weeks ago

I have the same setup and the same issue.

eamonnsullivan commented 2 weeks ago

I'm running Music Assistant on a Raspberry Pi, with a Ubuntu 20.04, and when I installed b4, all of my airplay devices stopped working, but the chromecast ones still worked. Sounds like the same issue.

sdg05 commented 2 weeks ago

same issue on a RPI4 running HAOS, first install of the beta version, Sonos works, no airplay to the HomePods

Unable to locate RAOP Play binary for linux/aarch64

marcelveldt commented 2 weeks ago

Should be fixed in the last update.

OzGav commented 2 weeks ago

@chasut @Frederick-G764 @sdg05 can one of you confirm this has been fixed

sdg05 commented 2 weeks ago

Thank much! That fixed it for me.. On Jun 13, 2024, at 7:37 PM, OzGav @.***> wrote: @chasut @Frederick-G764 @sdg05 can one of you confirm this has been fixed

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

chasut commented 2 weeks ago

Yes, looking good! Thank you.