It is not a full solution. It should solve all cases, while you are not using a device corresponding to one of your Sonos belonging to the pair. So, if you are using the device corresponding for example to your “Kitchen” zone, you should be able to use ALL (or “Loftstue” as grouped zone) for PlayURI and Say commands, without breaking the pair. You should even be able to group/ungroup your pair with your Kitchen zone using the UI (Kitchen device).
Please provide a feedback if all this is working well now with the new version.
What remains to do is to control properly the Loftstue pair from a Vera device.
When the pair is not grouped with another Sonos zone, you should be able to use properly the device attached to the master of the pair, which is in your case the one having IP 10.0.1.40. But using this device to control the pair while the pair is attached to another group will probably have an unexpected behaviour, including breaking the pair. It would be interesting that you try from the UI and this device to play for example a new radio while the pair is attached to another zone, and see what happens.
Regarding the other Sonos (the one with IP 10.0.1.10) of your pair, I think you should probably avoid to create and use a Vera device for it, because it could probably break the pair too. It is the one with the tag “Invisible” and finally it is the one to not “show” in the UI. The solution would be to disable actions on this device.
I have finally been able to do some testing, and the results is promising.
I have based my testing on using the UI.
I can select the pair as part of a group in the group section of the UI.
But when I “Apply” the pair is not shown as part of the new group in the sonos application.
The music is however played on the whole group. And I can adjust the volume on the pair by changing it in the sonos application.
If I try to remove pair from the group via the UI it does not work. It is removed, but if I click on the player tab and then go back to the group tab the pair is selected again. But if I use the unselect all function the group is correctly dissolved.
It also appears that the say function is working good with the pair. My pair is working fine after the command is used.
Thanks for the update.
Let me now if you need more specific tests.
Ok, I think we have to check something.
Please create one Vera device for each of your 2 Sonos (pair).
Then please provide the value of the variable AVTransportURI (you can find it in the Help tab) for each of the 2 devices
1 - when the pair is alone
2 - when the pair is grouped with another Sonos zone
[quote=“lolodomo, post:7, topic:178520”]Ok, I think we have to check something.
Please create one Vera device for each of your 2 Sonos (pair).
Then please provide the value of the variable AVTransportURI (you can find it in the Help tab) for each of the 2 devices
1 - when the pair is alone
2 - when the pair is grouped with another Sonos zone[/quote]
[quote=“haavard, post:6, topic:178520”]I can select the pair as part of a group in the group section of the UI.
But when I “Apply” the pair is not shown as part of the new group in the sonos application.The music is however played on the whole group. And I can adjust the volume on the pair by changing it in the sonos application.[/quote]
That’s annoying, it would mean the association is not done correctly.
Unfortunately I have no real idea why.
Not bovious when I have no way to test.
If I try to remove pair from the group via the UI it does not work. It is removed, but if I click on the player tab and then go back to the group tab the pair is selected again. But if I use the unselect all function the group is correctly dissolved.
The code I run to leave a group is certainly wrong for a pair. I will propose something new soon.
[quote=“haavard, post:8, topic:178520”][quote=“lolodomo, post:7, topic:178520”]Ok, I think we have to check something.
Please create one Vera device for each of your 2 Sonos (pair).
Then please provide the value of the variable AVTransportURI (you can find it in the Help tab) for each of the 2 devices
1 - when the pair is alone
2 - when the pair is grouped with another Sonos zone[/quote]
I imagine Pair B is the master in this case.
No real surprise but I have probably to set again AVTransportURI to x-rincon:RINCON_000E587F447C01400 for Pair A when the pair is leaving the group. That’s not done in the current code.
I recently noticed this behaviour with Amazon Cloud service. I believe I first noticed the same issue when I had a Qobuz access. It happens after a TTS call. That’s probably a bug. I will investigate.
The tracks in your queue are coming from what Sonos service ?
I never noticed this problem when tracks are coming from my media library.