Knock function doesn't work

[amau05]

8<------------------------ BUG REPORT -----------------------------------------

Expected behavior

When I knock on the table it should send the login info

Actual behavior

It doesn't send them

Step by step guide to reproduce the problem

Have the knock function enabled and knock on the table.

I did set the sensibility on high in multicute, and made sure it's enabled in the device settings. It has always be a bit bugged from the beginning, never really understood why, I had to change settings often like re-enable it, disable and re-enable login prompt, disable advanced settings or things like that... But now whatever I do It doesn't work. I use bundle 12 on the device.

Operating System

• Windows 11

Mooltipass Extension

• the firefox extension: latest 1.10.10

Mooltipass Application

• MooltiApp: latest 1.01.0

Mooltipass Device

• The Mooltipass Mini BLE

[limpkin]

could you try in low sensitivity? sometimes knocking too strongly can also cause issues.

[amau05]

I've just tried it and middle too, it didn't change anything

[limpkin]

could you send us a video demonstrating how you knock to support(at)themooltipass(dot)com?

[amau05]

Email sent

[amau05]

Still no solution found despite several email exchange

[Happyman0815]

Same problem for me using Chrome. In the beginning it worked very fine but later it was not working anymore (after playing around with configurations). ==> Probably a configuration problem.

Workaround: For me it worked again after restarting the Mooltipass Device. How to:

1. Enabling the following setting in the Moolticute tool: Tab "Hardware Settings" --> "General Settings" --> "Switch Off Device After USB Disconnection".
2. Save the updated settings on your device
3. Plug-out the USB cable from Mooltipass
4. Wait some seconds
5. Plug-in again the USB cable
6. "Knock Detection" should work now if enabled.

In general I have the impression that the Mooltipass sometimes needs a restart to accept some configurations.

[amau05]

Thank you! It actually did the trick. It's seems it is fixed now, I logged inon a few websites without issues, the only knock it didn't take was here on github for the security key which I had to press the button for but as it's not really a password maybe it's on purpose?

I use Firefox so it's not a chrome only issue but most likely a device issue. Maybe add a restart option in the menu?

[Happyman0815]

Just an idea: Check the github credentials in the Browser plugin configuration and with the Moolticute software. Maybe you have a customised configuration for this homepage.

[amau05]

The device was asked about the security key, what I meant was that the knock function didn't work on the security key and I had to validate by pushing the button on the mooltipass. I didn't log in using the security key willingly, I used traditional method with my login and password but for security reason (I guess?) Github asked for it after successfully logged in with credentials.

(I know the difference between 2FA and a security key, I didn't use 2FA and I don't keep my 2FAs on the device but elsewhere so even if it was supposed to be 2FA the device couldn't give it)