-
Notifications
You must be signed in to change notification settings - Fork 219
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
Duplicate Airplay Devices (ending with _______+) #163
Comments
That's because you probably have some Sonos speakers that have native AirPlay 2 capability (the duplicates without the '+'). You can prevent AirConnect from including these speakers with command line options '-m' and '-n': take a look at how I do this at the following link: https://github.com/pwt/docker-airconnect-arm/blob/master/Dockerfile See the text at the bottom of the Dockerfile. |
It may be something similar, though. It's only the speakers with a '+' that AirConnect is adding as AirPlay targets. I only have experience with (a wide range of) Sonos speakers, but you may be able to modify my advice for the speakers you have. Failing that, you can generate and edit a 'config.xml' file to disable specific speakers. |
oops accidentally closed the issue |
Yes, the AirPlay targets with '+' appended to their names are the ones created by AirConnect. You have two options for getting AirConnect to exclude the speakers that already support AirPlay: 1) Exclude the speakers automatically by model name and/or model number.
2) Exclude the speakers manually by disabling them in a configuration file.
|
BTW, one thing you can do is set the |
im going to try both of these ideas will let u guys know if i need anymore help |
so i did this: First, generate a config file by starting airupnp with the -i config.xml option; you can then stop airupnp. but now i dont think it sees the config file so i still see the + devices |
I'm afraid I don't know what a So, create the file
Caveat: I haven't tested this at all. |
will try this and let u know |
how do i check to see if it runs when it starts up |
The obvious thing to do is to check that the relevant speakers appear in your list of AirPlay targets. You can also check for the log file: |
i dont have the file |
you can use the -p option. It will create a file named with contains the processus id. If the file is empty, then it is not running. But why are you worried about that at the first place? |
so i want the file to see if air connect launches when i log into my mac |
It's the date of the build |
ah ok i have another issue believe it or not i have the config.xml setup with all the devices i want disabled and one of my devices is still duplicated with a + at the end how can i fix this? |
Use the advice I gave you there #163 (comment) |
thats what i did but it still doesnt seem to work |
Could you post the contents of your |
will do as soon as i get home |
so im still trying to play around with it. All good so far. ill report back at the end of the week |
Me again lol after forcing myself to figure out how to set up airconnect (took me a good 3 hours and I'm super proud of myself 😆) I now am able to airplay to my chromecast and Sonos but I see that in my airplay menu there are duplicates of all my speakers and i wanna know if its possible to get rid of it some how or maybe you can do something to the file and make it ignore the other devices or something idk im stupid with this stuff lol but its a lil frustrating but it is possible to live with
The text was updated successfully, but these errors were encountered: