Hi!

A quick update on this, we discovered a minor difference in how the LIFX buld acts depending on model, which created this issue.

We have now fixed this so we will soon release a new firmware update which makes this work!

@kortenkamp said in Flic Midi - How to set it up?:

". Are you still workin

Hi!

I can only say that it is coming "very soon".

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

Hi!

I'm sorry to say that Siri is still not possible because of a change that was made to CoreBluetooth in iOS. We still don't know if this was intentional or if it is a bug. Apple has not explicitly said that this is not allowed, but after having submitted bug reports to Apple and getting no response at all we are not very hopeful at this time.

I'm sorry about this.

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

@beachb_sl

Hi! You can find an implementation of SHA-256 here:

https://geraintluff.github.io/sha256/

@philippe-lux-67 Hi!
Sorry for not getting back, we did have a look at the logs but unfortunately there was nothing we could see that would spark an idea for a potential workaround. We do not have the ability to test or update old versions of our app, so I'm afraid there is not much we can do about this.

@scullracer Hi!

Sorry to hear about the hardware issues. Unfortunately it is not possible to create such action for Flic in iOS due to limitations in the API to trigger arbitrary Shortcuts.

@swordfisherman Hi!

Could you please contact dm-support@flic.io, preferably from the same email that you are trying to get confirmed and we can help you there!

Hi!

Sorry about this, we have uploaded a new version of the Flic app that fixes this and we are currently awaiting approval!

@philippe-lux-67 Hi!

Unfortunately I don't have access to an iOS 10 device (minimum supported version is iOS 11 currently), but in theory it should work since we have not made any breaking changes to the Flic firmware so they should work with the old apps and OS versions.

However, it might be that Apple has released a security update that changed something in Bluetooth that made it break.

If you go to Help & Feedback and Submit BT Log we can have look if it gives any idea for a workaround.

Sorry about this.

@info-6 Thank you so much for reporting this, we will check this out and update the branch with this change!