Re: Play Sonos Groups - Enhancement Request

Hello @Emil - first off, I love all the Sonos-related enhancements that have been recently deployed. It's allowed me to remove many of my IFTTT commands and do them natively in the flic app. Love it. Thanks to the flic team.

I wanted to see if you knew if Sonos exposed the formal Groups that thy have in their app? If so, is this something that flic can incorporate into the Control tab of the Action Type view? Maybe if groups exist they show above the Sonos Device list?

Thanks.

@Emil That's a shame they don't provide the "static" Groups in their API. Yes, checkboxes versus radio buttons would be a game changer. Thanks. Mike

Re: Play Sonos Groups - Enhancement Request

Hello @Emil - first off, I love all the Sonos-related enhancements that have been recently deployed. It's allowed me to remove many of my IFTTT commands and do them natively in the flic app. Love it. Thanks to the flic team.

I wanted to see if you knew if Sonos exposed the formal Groups that thy have in their app? If so, is this something that flic can incorporate into the Control tab of the Action Type view? Maybe if groups exist they show above the Sonos Device list?

Thanks.

@Emil I believe the groups that you speak of are the lower g groups. Yes, they are dynamic and can change fairly easily (too easily imo) and I think that's why Sonos now has Groups (upper G). In the Sonos app you can create a Group, give it a name, and select the speakers/rooms that you want assigned to that Group. Then when you go to play music, instead of selecting specific speaker/rooms you can select the Group. For example, I have groups named Inside and Outside. The speaker/rooms in those Groups remain the same regardless of how I might dynamically change them throughout the day. But sometimes I might only want music in the Office or Den, which I might dynamically connect as a group. So it seems the question is whether or not Sonos exposes these Groups in their API? And can you send a play command to a Group? Or simply a "player"? I don't know.

I'd like to request an enhancement that we have the ability to select Sonos Groups when choosing where to play the music source. Right now the app only allows for the selection of "players", which is a specific speaker/room in Sonos vernacular, but Sonos also has defined Groups. I realize that playing through a "player" will play through any Sonos speaker that is grouped (lower g) with that speaker, but that is not a formal Sonos Group (upper G). Sonos Groups are static containers that allow us to define a specific list of players. Please add the Sonos Group selection option along with the "players" function. Thank you. https://docs.sonos.com/reference/groups-getgroups-householdid

@Emil the Sonos API method: https://docs.sonos.com/reference/favorites-getfavorites-householdid

@beachb_sl Hey, curious if you could describe in more detail the type of light/color feedback that you're looking for?

My buttons do have visual feedback. If I click a button that has not been paired the light shows red. If I click a button that has been paired but is not within range of my hub the light shows as yellow/orange. And when the button successfully passes along the click action it blinks green.

@buckyswider @Emil Agree, would be nice if there was a for the hubs to synchronize the configurations across a single account.

@msiekkinen This is great!!! So what did the final install look like? Has it held up?

@rick-0 While it would definitely be nice to be able to do this natively within Flic, you could do this with the IFTTT service. Not sure if you've ever used it. Below is a link that describes how. Essentially, create 2 IFTTT applets that are linked together via web hook with a Delay before the second one starts. Yes, more involved than an average consumer is going to want, but still an option. (and I believe it requires an IFTTT Pro account $)

https://help.ifttt.com/hc/en-us/articles/13299982764315-How-to-Add-Delays-Between-Actions

@rob-loosx @admin-flic Funny, before I bought the Flic Twist my expectations for how the selector was going to work was similar to how you describe it. My thought was that you turned the selector to a position and that then identified which virtual button you were using. All actions (push, double push, push/twist, hold, etc...) would continue to apply to the virtual button that you'd selected until you changed the selector to a different virtual button. In essence, you would have 12 buttons in one that didn't always reset to the main button after every use. So a little different from how you describe it. And a little different from how it works now where the selection is only temporary. Granted, if you wanted to know which selector was active you might burn battery life with a light on. Maybe you add a motion sensor so the selected button light comes on when you're in front of it. But again, more battery. Just thinking out loud.