Posts made by oskar

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

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

@atruttmann Hi! Unfortunately this clashes with a build in functionality that after 8 seconds the Flic will disconnect and advertise in "Flic mode". This is to give users a way to connect the Flic back to the Flic app in the case you would not be able to disconnect it from the other device.

@jonasnordstrom Hi! This is fixed in the new beta version 5.5.3!

@jeff Hi! Sorry to hear about this! Could you check to verify that the Flic app has access to the local network? This can be done in iOS Settings -> Flic -> Trun on "Local network". If it is already turned on, could you try turning it off and back on again?

@jf Hi!
Could you describe at which step it failed? Did the RPi discover the Flic at all?

I don't have a RPi at hand but just tried with Kubuntu and did not see any issues.

Also to make sure, did you add it by going to System Settings -> Hardware -> Bluetooth -> Add new device?

@a-j-towler Hi! I have reached out to you through our support system (aka email), it's a bit easier to communicate there

@samjay Hi!

Very sorry to hear this. Unfortunately this seems to be somewhat common with our HomeKit users, as you describe it seems that HomeKit does not realize something has changed.

The only way to completely re-do the HomeKit pairing from scratch is unfortunately to factory reset the Flic Hub. This makes it appear as a new device to HomeKit and hopefully into a working state.

To do this, locate the pinhole button underneath the LED on the back of the Flic Hub. Press Using a pin or needle, press and hold this button for 10-15 seconds. The LED should blink to indicate that it is rebooting.

Remove the Hub from the Flic app by pressing and holding on the Hub icon. Now re-add your hub and button and enable HomeKit for the button.

If you have performed all these steps and you still can't find your button, we strongly encourage you to file a bug report with Apple so that we can escalate this issue.

@ColCustard Hi! This issue should now have been fixed in the latest version of the Flic app for iOS!

@na51hog Hi!

This issue has finally been resolved by SmartThings, authenticating should now work again!

Sorry for the inconvenience!

@a-j-towler Could you try one last thing: factory reset of the Flic Hub. To truly re-do the HomeKit pairing, the only way is unfortunately is to factory reset the Flic Hub. You can do this by locating the pin hole button underneath the LED. Using a pin or needle, press and hold this button for 10-15 seconds. Upon releasing, the LED should blink to indicate reboot and you need to re add your button and now get a chance to pair this to HomeKit.

Very sorry for having to ask you to do this, but if this does not work, I strongly encourage you to file a bug report to Apple in order to escalate this issue within Apple.