I am now working on a new device that will help to maintain a device for each Sonos zone; each new Sonos will be automatically discovered and added as a new Vera device.
It will be released soon.
My code is based on calls to http://:1400/status/topology with the IP of one Sonos zone.
Can someone confirm that the result of the HTTP request lists all the Sonos zones in SonosNet, even the Sonos that are not temporarly disconnected (not powered) ?
I have two play:3 configuged as a stereo-pair in the kitchen (K?k). I only want one device to show up for this in Vera because they always plays the same thing.
This might be a “special case” you’ll have to handle in the topology plugin.
[quote=“big517, post:2, topic:174636”]Yes and No, The result is a page that has 2 options, when you click either one it will expand to show you the Players, and servers respectively;
Zone Players URL: javascript:toggle(‘idp2587584’):
Media Servers URL: javascript:toggle(‘idp2586752’)
I hope this helps.[/quote]
What I use is the Zone Players part.
I need to know if it lists always all your zones, even if one of them is disconnected (unpowered - if it is the correct english word) ?
[quote=“hek, post:3, topic:174636”]I have two play:3 configuged as a stereo-pair in the kitchen (K?k). I only want one device to show up for this in Vera because they always plays the same thing.
This might be a “special case” you’ll have to handle in the topology plugin.
Might be not easy.
I see that your two Play:3 have the same group: RINCON_000E587E838C01400:2
They have the same strange name “K?k”. Is it the real name you gave to your zones ?
stereo-pair is a special Sonos feature, isn’t it ?
Can you help me to identify a stereo-pair ?
Could you unpair your 2 Play:3 and then provide me the new topology ?
Note: I have to handle the special case of the bridge too.
Note 2: please unplug one of your 2 Play:3 and tell me if the topology is updated.
Bad news even if it seems to be logical as you said.
If I delete the Vera device when the zone is unplugged and create it again when the zone is plugged again, it will break scenes using this device.
3 possibilities:
1 - I maintain the Vera devices to be conform to the Sonos network topology
2 - I create new devices but never suppress devices
3 - I suppress devices only after a certain delay of inactivity => how much time ?
When stereo-paired they both have the same group-id (RINCON_000E587E838C01400:2). The master unit has coordinator=true, and slave unit have coordinator=false.
When unpaired they have different group id (RINCON_000E587E83B801400:16, RINCON_000E587E838C01400:2) and both has the coordinator property = true.
I have not tried grouping units in any other way (like you do when playing same content in different rooms).
I would suggest you create all devices you find (use UUID as the unique identifier?) as slave devices. The plugin never deletes a device but it could update it’s “state” to “SLAVE” or something.
When beeing slave you cannot control it (all buttons disappear etc) and status is Slave. When beeing offline it could have the same disabled GUI and have status offline visible.
If user REALLY want to delete an auto-created device they use the trashcan on the devicetab. If the deleted sonos show up in the the network the unit will be auto-created again.
[quote=“hek, post:12, topic:174636”]When stereo-paired they both have the same group-id (RINCON_000E587E838C01400:2). The master unit has coordinator=true, and slave unit have coordinator=false.
When unpaired they have different group id (RINCON_000E587E83B801400:16, RINCON_000E587E838C01400:2) and both has the coordinator property = true.
I have not tried grouping units in any other way (like you do when playing same content in different rooms).[/quote]
That’s not enough as it is what you got with a normal grouping. Check dinkeldorf’s data. I need to find something else to distinguish stereo pair. Name could be an idea but I assume there is something better in the description file.
I would suggest you create all devices you find (use UUID as the unique identifier?) as slave devices. The plugin never deletes a device but it could update it's "state" to "SLAVE" or something.
When beeing slave you cannot control it (all buttons disappear etc) and status is Slave. When beeing offline it could have the same disabled GUI and have status offline visible.
Yes, I use UUID as unique identifier.
Good idea with the SLAVE and OFFLINE state.
Even in SLAVE state, certain actions are probably allowed, like volume adjustment. But I could disable "normal"l actions and update accordingly the GUI.
If user *REALLY* want to delete an auto-created device they use the trashcan on the devicetab. If the deleted sonos show up in the the network the unit will be auto-created again.
For SLAVE and OFFLINE state and the impact on GUI, I can certainly do it without using the network topology but with normal UPnP calls.
OFFLINE state is already detected with the displayed message “Cannot contact…”, I just have to update the Player tab.
For SLAVE state, I have to search a proper way to get the info and then adjust the Player tab.
By the way, I will not be able to “grey” (disable) buttons in the Control tab and buttons on the device, it is not something possible with the MCV flash GUI.
Weird that “Living Room 2” didn’t disappear for you… When I disconnected one (of the stereo-paired units) it was removed from the topology immediately…
Are you absolutely sure that your Living Room2 Sonos zone is unplugged ?
Reading your information, I would have concluded that it is even the master of a group including Whole Home zone and Portable zone.