@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 I had it previously set up so my phone was on my guest network and so was the Flic Hub. I couldn't access the site on my computer because my computer was on a different network. So I had to change the Flic Hub to be on that network.

@xappo Yeah MQTT would make the flic buttons useful again. Hope someone at flic realizes this. I have been nagging about it in every place I can find.

This is awesome!
In lack of better Javascript skills, I actually configured a Flic 2 button (through the "front door" main app interface ), just to be able to trigger the record action without a phone. Even though it worked, it felt kind of "offensive" to the code (like using a MacBook Pro as a bookend 😆 ). I guess I'll hack around with the example code just to get everything in one place 🙂

❤️👍🏼

@mikaps7 you execute the requests at the same time parallelly. If you want to execute the second request after the first has competed, you must initiate it in the callback of the first, or later.

@Emil I tried using chrome and microsoft edge. But yes the switch is on, however a red dot is still displayed when the ip address is found in the web app

We haven't really started working on this, but yes we will support it in some form.

This is what I ended up doing: https://community.flic.io/topic/18102/a-flexible-hub-running-on-a-pi-zero

@Emil I found the error: the .pem file on my server only had the server certificate, not the intermediate nor the root. The Flic Hub was the only client so far to throw an error because of this. I added the missing certificates and now it works just fine.

On a related note: for people issuing self-signed certificates, you may want to add the option of switching off certificate validation (as you have in the ui).

It works!

The problem was

old firmware (could not update myself) with new firmware the 'sdk-switch' in the flic-app was turned off, by default
-> red dot in the sdk-login-screen turning sdk-switch to on
-> green dot in the sdk-login-screen
-> login works!

thanks @Emil for the directions

We have a method "deleteButton(bdaddr)" on the buttons module that apparently is missing in the documentation that you can use.

If you use the FDM configuration to remove all buttons you should probably write [] in the field to specify an empty array and then check Exclusive.

@Emil Thanks for explanation.
Works now...
I also managed to figure out what JSON structure is going for MDM under point 3.
Basically I export pairings from dev hub and if we use those buttons on managed hub I just paste "buttons pairings" json in to the field.

You use the one written on the back of the hub. If you have changed the password however it's the one you have changed to.