First I just wanted to say that this plugin is simply brilliant. It is my single most used plugin for creating scenes. Lolodomo, thank you so much for continuing to develop this.
I just updated to Version 1.0 and added the plugin via the app store, and I am trying to get to grips with the new TTS behaviours you introduced (I think it was in beta 3, which I missed!)
It seems that the new behaviour is to save state, group the units to the configuration set in the new GroupZones parameter, say the message, then go back to the previous group configuration and carry on. This is giving me 2 problems:
[ol][li]It makes the process take longer, because of all the ungrouping and grouping that is going on (I have 4 Sonos units, which I typically leave grouped in one big group)[/li]
[li]Sometimes the grouping function doesn’t seem to bring all my devices back into the group. This means that it doesn’t always continue as expected. I’ve noticed this problem as well when using the UpdateGroupMembers action [/li][/ol]
Would it be possible in a future version to let me specify something like “EXISTING” in the GroupZones parameter, to bypass all the grouping and ungrouping when I don’t need it?
Has anyone else seen the issues with the grouping? Usually repeating the UpdateGroupMembers action fixes it…
Yes, technically, I think this additional feature is doable. I agree that it will increase speed.
An interesting feature that I could use myself.
It is added to my TODO list.
Regarding your issue, I noticed no problem on my side. Dies it happen when you play a particular source (Sonos service) ? I am asking myself what could happen if the playback takes several seconds to start.
With some further investigation, the group gets stuck usually with one particular Sonos device (the one in my Living Room that is furthest from all others and does occasionally drop out whilst in normal playback mode). I’m now wondering if it’s more a connection/timeout issue.
Do you have any timeouts going on within the plugin and grouping? It seems to be almost instantaneous if I run the group command a second time from the plugin, however it seems to always work first time with the normal Sonos Controller app on my PC…
I’ll try out Sonos support and see if they can help (this unit is also connected through a LAN cable and so I don’t think should be getting any connection issues!)
I have now implemented this new feature. If you just want to use the current group setup, call Say or Alert using value “CURRENT” (don’t care about case) for the parameter “GroupZones”.
So, this parameter can now be set to:
comma separated list of zone names if you want to send your message to several zones
“ALL” if you want to send your message to all Sonos
“CURRENT” if you want to send your message to a particular Sonos zone including its current group
Is grouping zones “CURRENT” something that is still supported? I have a problem when my playbar zone is grouped with another zone and I use a alert or a say action it leaves the group and does not re-join that group afterwards. so I thought I would try using the CURRENT for zone grouping but doesn’t seem to make any difference.
That makes sense, the playbar even in normal scenes doesn’t re-group properly. Lolodomo, is there anyway you could add support for the playbar? I would be willing to help test or anything else if needed. Thanks
Using the updated JS file attached to this message (first unzip the file), please give me the value of the variable ZoneGroupState now displayed in the Help tab in the following conditions:
1 - all zones are ungrouped, included the Playbar.
2 - playbar is grouped to another zone and is the coordinator of the group.
3 - playbar is grouped to another zone but is not the coordinator of the group.
This could help me to understand what are the difference with playbar.
Ok I need to fix my XML parsing because the playbar introduced an additional subtag for linking the subwoofer.
Not an easy change but when done playbar should be supported for grouping through the plugin.
There is something else to check.
When your Playbar is member of a group and its coordinator, please check in the help tab the value of AVTransportURI variable for one of the other members. In your case, I expect this value: x-rincon:RINCON_000E58BC013001400
Is it this value ?
[quote=“lolodomo, post:15, topic:181300”]There is something else to check.
When your Playbar is member of a group and its coordinator, please check in the help tab the value of AVTransportURI variable for one of the other members. In your case, I expect this value: x-rincon:RINCON_000E58BC013001400
Is it this value ?[/quote]
[quote=“SteveZ, post:17, topic:181300”][quote=“lolodomo, post:14, topic:181300”]Please try with the updated file attached to this message and let me know if things are better with Playbar.
If not, please grep “testParsing” in the Vera logs and provide the result (you will have these logs each time groups are changed).[/quote]
This is working Perfect! Thank you so much![/quote]