Any comments about my feedback from the flic team?

@finn probably some bug or something in Homepod then. The mapping between button click type and what lights should be controlled is fully contained within the homepod/Apple TV. The flic hub only delivers the click events.

@gregorysinclair I put a reply addressing that error message in the other thread.

From what I can tell with my testing, it will still work, you just have to get creative with your button creation and mapping.

@Emil I use the flic app on Android connected through a Flic Hub

@Barlium Ahhhh dang. Stupid mistake on my part but I'll leave this post up in case anyone else is a dummy like me.

I started a manual routine, but didn't see that there's a save button as it was hidden under my phone's keyboard. Flic wasn't finding my scenes because I edited them but never saved them. I didn't see the obvious solution because I was blinded by both my keyboard and my confusion over the nomenclature.

Don't be like me.

😜

@jhamers Sonos's official API is unfortunately quite limited. See https://docs.sonos.com/reference/about-control-api for what features it supports. Please reach out to Sonos and suggest that they should offer more features to third party apps.

@reluctantflux

Anyway, really curious on how people have been creative to actually utilize the twist feature, and how they did it.

Unfortunately, they haven't.

I as well as many here, are HomeAssistant users looking to do similar things, but they have not updated the SDK to support the twist, and it has been multiple months since it's release. There is still no way to use the twist functionality outside of the.. what, 2-3? integrations that they have listed in the app.

They seem to refuse to update the SDK with this functionality, even though they had years to get the software ready for the release of this device. You try and bring it up here, everything just goes silent. No one will give an update, timeline, anything. Absolutely terrible customer service and product support.

We all just have a bunch of fancy paper weights at this point.

@scott-0 if you use "smart dimming" rather than "advanced dimming", then the volume should react to external changes and the issue you describe should not happen.

@rbjohnston isn't https://flic.io/start sufficient?

One of my two flic twists was missing the adhesive.

I am using command strips. So far so good. I've one in place for a couple of weeks. I am using the command strip that is similar to velcro.

@Emil - both seem to be available - not sure which Google Home uses (assume direct): https://developer.smartthings.com/docs/devices/direct-connected/get-started/

https://developer.smartthings.com/devices/cloud-connected

@Emil it's not a solution to group using an app. The whole idea with flic is to awoid using apps. We need a way to be able to click a flic and then play a Playlist at random in the whole house.

@Emil If you would simply update the SDK to support all flic twist features and operations, we could sort things out ourselves, one way or another. All of the functionality exists in the Hub LR for other integrations (albeit, extremely few, but it is still there), so it doesn't seem like you can't, it just seems like it won't. It was said Matter is the priority. Well, Matter seems to be going nowhere, so can we please at least get the functionality we were promised and paid for in the meantime? I should not have to beg to get what I paid for.

Why will no one give any sort of update, or tell us what is going on? That is the very least you could do. It is incredibly frustrating.

There are many companies out there who have delays, timeline adjustments, whatever else.
In this situation, there are two types of companies. Good companies, and bad ones.

What to the good companies do? They offer transparency, they give updates, they try and work out solutions.
What do the bad companies do? They give useless vague information or say nothing, and give excuses.

I have yet to hear any useful updates, or solutions. Yes, Matter took/is taking longer than you expected for whatever reasons. Ok, so that means 'oh well, too bad' for everyone? I don't understand why you can't just update the SDK. Why don't I understand? Because no one has told us why or why not. If you can't do it, say so. If you can do it, say why you won't.