@abboberg Fw 2.0.19-sdk2 was an old beta firmware that is no longer compatible. I've removed everyone on that track to be on the current. If you do a fw update now you should get a version that works.

@flic-v not sure exactly what you did but if you set a custom password through the app, this should override the password on the back.

@flic-v the password is written on the back side of the hub

@akiraK Ok you can now firmware update your hub by either waiting up to 24 h while being connected to internet, or press the pin hole on the hub for exactly somewhere between 2 and 5 seconds, then release. It will then blink during the update and then reboot. In the app you can check that the hub then has firmware 3.0.10.

Hi. I have applied the patch you linked to and built a new firmware for Flic Hub LR.

@akiraK @yea @Djelibeybi please give me the serial numbers of your hubs so I can assign the new firmware if you want to test it, to see if the patch works.

@akiraK thanks, will take a look.

@oskaremilsson And the hub isn't already added to the app? Otherwise it must be something wrong with the Bluetooth Low Energy scanner feature on that phone. We just do a filtered scan (by service uuid) and show whatever is being found.

So what happens? Does it not find the hub at all during scanning? Is the LED on the hub red or orange? (orange means connected)

@nb525 it should not matter or not if the button is "standby" or not. When you press the button, it should connect immediately and deliver its button event. If not, make sure you don't have too many active Bluetooth connections on your phone.

Maybe you could try another browser? We have tested Chrome and Firefox.

And make sure you have turned on hubsdk access using the Flic app while being connected to the hub in the settings.