@kerry-thacher Hi!

Unfortunately, no. At least not from what we have found.

You can use the "alternative keymap" in the Universal Keyboard action to prevent the on-screen keyboard from hiding while the Flic is connected, however, this also limits what we can do with keyboard commands.

(Note that you need to "Forget" the Flic from iOS Bluetooth device list if you change the keymap for it to have effect).

So Apple requires the device to identify as a keyboard to be able to do certain things, like trigger system wide keyboard commands (which is what this video suggests as a trigger for Shortcuts), and this enforces the behaviour that the on screen keyboard disappears.

Sorry about this, it would certainly be a neat feature to be able to trigger iOS Shortcuts without affecting the on screen keyboard.

@j that is the simplest way to get automatic access to your flows. You can probably set up your manual web hooks if you want, using the http request action, but you need to manually enter the url.

@gabrielmgrossman Please file your issue to https://flic.io/support.

@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.

@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.

@oskar

Thanks for the update. I appreciate it.

I've also logged an issue with the WebKit project in case they can shed any light: https://bugs.webkit.org/show_bug.cgi?id=290779

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

@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.

@Emil Ah sorry realised I was under the apps settings and not the flic button itself!! Working perfectly and exactly what I had hoped! Thank you.

Their comparison table: https://flic.io/flic-hubs#comparison-table

@Emil That fixes the issue. Thanks!

@gerald don't you see my reply?

@oskar That's great thank you! I just managed to separate the logic to different files so it's shaping up well. Thanks for the help