Airsonos seems to only find nodes that are 'coordinators'

[ericcfrey]

First, thanks for writing airsonos. It is great. I have an old AirPort Express connected to a line in, but it is not nearly as reliable or convenient as airsonos.

I have a Sonos system with 3 wired connections, two of those with wireless on and one with wireless off, and several systems that are only connected via SonosNet. Airsonos does not find all the nodes. I tried restarting it several times and seem to get the same ones every time. I looked in the status webpage under the toplogy link and notice that the only ones it sees are have yes in the "Coordinator" column. I see the same behavior if I run airsonos on a Mac or a raspberry pi 2. Any ideas?

[ericcfrey]

I figured out that devices have the Coordinator field in the topology display set to False when they are grouped with another device. For example, I had Bathroom grouped with Bedroom. Bedroom showed up with Coordinator true and Bathroom with it false. Bedroom was detected by Airsonos' search process while Bathroom was not. If I used Airplay to direct a stream to Bedroom it played on both speakers. I guess this works as expected. While playing the stream to Bedroom I ungrouped it. Rather strangely, the stream started playing only to Bathroom. The topology table listed true for both Bedroom and Bathroom. However, only Bedroom was listed as a potential AirPlay target. If I restarted Airsonos it found both Bedroom and Bathroom and created AirPlay targets for each of them.

What would be nice is if Airsonos automatically detected changes in topology and created or destroyed AirPlay listeners.