FlicTeam

The problem is that groups can be pretty dynamic. You can hold the play button on one player and it automatically joins another group that is playing music in your household. And with the sonos app it is easy to move around speakers between different groups. That said, it is possible that a group id that was valid when a flic was configured might not be valid after a while after grouping back and forth.

That's why we think it's more simple to pick a player you want to play on, and we will then at runtime when the action is executed check which group that player belongs to and play on that group. May I ask in what circumstances this strategy is a bad idea?

@josh-k Hi!

The way we get around the keyboard not showing is to report as a "Consumer Control" device, which is what tells iOS that it might not be a full keyboard, thus still showing the on screen keyboard.

It seems that this is also what imposes the limitations on sending key codes to a web page.

Sadly, in my testing I could not find a combination where the on screen keyboard was still visible and at the same time getting key events through to an unfocused web page.

We are still on the lookout for a workaround for this but right now I'm afraid we don't have a solution.

@josh-k I see, it indeed seems like capturing keyboard events without having a text field focused has been restricted since iOS 18.

There might be workarounds but I have not tried them personally, but maybe try this:

Set "contenteditable" to "true" on an element, and have the user tap the element to give it focus:

<div id="editor" contenteditable="true">Tap here</div>

@josh-k

Hi!

I tested this on iOS 18.4, and it seems to work. I tested with the "A" and "Return" to type into the address bar of Safari. Both seem to work.

I also tested on:
https://www.toptal.com/developers/keycode

(Note that you have to focus the textfield for this to work)

Could you let me know if there is any detail I'm missing in recreating this issue?

Note that it's a good habit to "Forget" the device if you go between different keymaps since this is cached for the Bluetooth device.

@mx5_94 Seems like a very powerful option. We'll definitely implement that!

@SME This works perfectly fine in the Android app. You find the KEYBOARD COMMAND action under the Flic Universal category. There you select "Keys" and then A, B or C.

@mx5_94 thanks for the feedback. I assume you think it's more convenient to use sonos favourites over sonos playlists?

@craig-2 we are internally experimenting with our new hub sdk features (https://community.flic.io/topic/18536/new-flic-twist-features-for-the-hub-sdk) together with home assistant (communicating over mqtt) and it works pretty good. So that is one option.

The other option is to expose devices in home assistant as matter devices, as explained here https://community.flic.io/topic/18457/home-assistant-twist-another-angle.

@mosthated Sorry forgot to mention that only the iOS app shows this provider right now. It will come later to Android.

@bmatest0910 You need to carefully study the readme at https://github.com/50ButtonsEach/flic2lib-android, in particular the section https://github.com/50ButtonsEach/flic2lib-android?tab=readme-ov-file#scanning-for-new-buttons. What API level does your app target and what Android version does your device have?

If targeting and running on Android 12 or higher, ACCESS_FINE_LOCATION is not the permission that you should request at runtime, but BLUETOOTH_SCAN and BLUETOOTH_CONNECT.

If you really need ACCESS_FINE_LOCATION in your app for your other purposes, not Flic-related, such as GPS, you need to follow the instructions at https://github.com/50ButtonsEach/flic2lib-android?tab=readme-ov-file#api-versioning-and-manifest-permissions.