-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Filter out players ? #74
Comments
I think it's a good enhancement to provide a Note that when these zoneplayers are excluded, you won't be able to use them in any of the features provided by homebridge-zp. In particular, you will no longer be able to group them from HomeKit, which you would want to do to send the AirPlay 2 stream to zoneplayers that don't support Airplay 2. I need to check if the zoneplayers report whether they support AirPlay 2. Otherwise, we need to whitelist the models that support AirPlay 2. Could you please run
substituting the IP address of one of your zoneplayers that supports Airplay 2, and attach |
Seems like there is something in there:
Maybe it would be possible to not exclude them but just "hide" (not sure if this is possible) and so still support the other features. Let me know if you need anything else. |
Unfortunately, no, this is exactly the same output as I get from my zoneplayers, that don't support AirPlay 2. It mentions a state variable I've published a beta version that logs these events. Could you please install it ( I'm not sure if
The only way to do that (sort of) in HomeKit is to move them to an otherwise unused room. I never tried this before, but I might be able to create the accessory, and not tell homebridge about it. That way I would still have the accessory's structure internally, but it won't be exposed to HomeKit. You would still see it in the homebridge log, however. |
Here you go... I enabled airplay 2 on |
Thanks. What models are ZPS13 (Schafzimmer) and ZPS14 (Wohnzimmer)? The other three, ZPS12, are recent Play:1 models, aren't they? Ok, it would seem like each player emits a
I don't see that in the log. Could you please start Was AirPlay 2 enabled in Wohnzimmer while you captured the log? I double-checked my own installation. My ZPS12 Play:1 player also includes |
ZPS13 == Sonos One All others == Play:1
Yes this sounds about right...
I can try this again later...
No, only for Schlafzimmer (ZPS13)
I think what the log shows I right here... Only ZPS13 and ZPS14 support Airplay 2. |
Using `DeviceProperties` event, see #74.
Thanks for the info!
Thanks. Could you try with v0.3.20-1 (again, install thru So the good news: we can detect which zoneplayers support AirPlay 2. The bad news: with the current design of homebridge-zp, this is only detected after the accessory has already been exposed. This might actually be the compelling reason to refactor homebridge-zp to use dynamic platform accessories (see #1). More bad news: currently, you need the accessory of the (intended) group coordinator to mark it as coordinator, before joining other zones to the group. To be able to join a hidden Airplay 2 player, it must be presented as selectable input. Another thing on my long-term todo list (see #8). |
Yes these are reported correctly:
|
Let me know if I can help with anything else... And keep up the good work! Thanks a lot :) |
- Create the accessory for each zoneplayer as soon as it's discovered, but delay creating the services and characteristics, until after the homebridge server has started. - Subscribe to `DeviceProperties` events as soon as the accessory has been created, so the discovered capabilities and setup can be used for creating services and characteristics. Needed for #74. - No more need for whitelists.
Zoneplayers that support AirPlay 2 already appear in Apple's Home app. When `"excludeAirPlay": true` is set in config.json, these zoneplayers aren't exposed by homebridge-zp. See #74.
Could you try the latest beta (v0.4.0-0)? I refactored the startup of homebridge-zp, so the capabilities are detected before the services and characteristics are created. Zoneplayers supporting AirPlay 2 won't be exposed when Could you please capture another debug log and post that, so I can see homebridge-zp works as intended?
Haven't worked on that one yet. I want to be sure the refactored startup logic works, before making more changes. |
@ebaauw sorry I was not able to capture a debug log yet but from a quick testing all seems to work. When I use |
Good catch. Normally homebridge will call
|
Call `getServices()` for excluded zoneplayers, see #74.
Just released v0.4.0. Closing this issue. Input select (and possibility to join the group of a non-exposed ZonePlayer) continues in #8. |
Hi there,
I wonder if it is possible to filter out some players and so not show up as switches ? A few of my Sonos devices already have airplay 2 and so show up in the home app already.
The text was updated successfully, but these errors were encountered: