This has been solved 😌
See full discussion over at reddit here.

@Emil I see, I didn't think of that! Thanks for your help!

Thanks a lot! I will make sure to try the fix when the firmware update comes out.

Are there any plans to when this will happen?
And is there any way to get a notification for new firmware updates?

@stenr The bluetooth connection has been transfered to the new phone but cannot be activated. Message: An app is required touse this connection. The Flic app is installed....

I made an update to our server. Please try again now.

@walterianneo I made an update to our server. Please try again now.

@Emil It worked. Thanks! 🙏

@Emil Hey just trying to get an update on this

@rob-loosx many thanks for these examples, really helpful. I wonder if you can help with an integration I need for LightwaveRF which uses UDP. The API for it is here and I'm wondering if your UDP script would be a starting point for this? Unfortunately my programming is limited so I doubt I can work out what needs changed but if you or anyone can point me in the right direction that would be great.

@Emil many thanks for that. Yes looks like it's entirely possible using the SDK. However I'm a complete novice when it comes to coding and this is probably beyond my capabilities.

If anyone else has written a script which will integrate LightwaveRF Link into Flic that would be great.

@joegeiger said in Can I use a flic button for CURT Echo?:

@Emil Thanks for the info! I have all first gen flics. I ordered a new version 2 button to see if it will work. I’ll let you know if it works.

It works! The CURT app paired and is working with the flic 2 button. Thanks for the help.

For other folks finding this as yet unanswered question via a search: FWIW, I have been using magnets on the back of multiple flics for over 6 months now with absolutely no ill effects.

@paul-j-houghton as target for Flic. Then you should be able to see if something looks strange in the request.

@slbickford THIS still works. Thank you

@pinnace0 make sure you have activated sdk access in the hub settings while you are connected to the hub in our Android or iOS app. Also make sure you're not both connected to wifi and ethernet at the same time (this issue will be fixed in a future firmware).