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