@flic-16 Can you try this base64 encode method instead:

function base64Encode(str) { return Duktape.enc('base64', str); }

@dustingtorres Yes! It is one of the priorities we have currently.

Hello Emil, is there any update on this? Thanks!

@abboberg Thx, and I do know that and used it in the past. I guess I forgot about this one. So much for remembering things. Of course, this means I need to configure each and every butten separately by hand instead of using the SDK for the whole hub.

Thx anyway!
Joachim

@oskar I try to get the hub to communicate with Touch Designer. As I understood I need to fill in the correct IP and Port in the first line of the main.js
Unfortunately I can't get it to work. The console tells me that the message is sent but nothing happens in Touch Designer. Any hints on that?
All the best, Pascal

@flameeyes Could you explain a bit how your ipv6-only hostname certificate is set up and works technically, and what CA signs it?

Hey @rs, very late to the party here.

The Flic hub does not appear to have third party integrations, although the Hue API looks pretty straightforward.

Did you find the Hue developer docs? https://developers.meethue.com/develop/get-started-2/

Did you have much luck/progress?

How can I help?

Hey @jonas-wallin, I’m very late to the party although more than happy to help (pro bono), if you still need the assist!

Hey @andy, a little late to the party here, looks like you’re trying to integrate to the old LightwaveRF Connect series.

I have Connect series in my house and have successfully used their API, although my Flic hub simply sends button clicks to a Raspberry Pi which does the integration to LightwaveRF.

Have you had any luck/progress on this? How can I help?

@martinm When an incoming FIN packet is received from the remote endpoint, the socket is automatically properly closed unless the allowHalfOpen option is set. If that option is set, the socket is properly closed at the time when both an incoming FIN has been received and the local user has called the end method on the socket (in any order). Nothing is done at garbage collection time, so if you use the allowHalfOpen property, remember to close the socket by calling the end method. If the allowHalfOpen is not set, you can still use the end method to send your own FIN packet.

@martinm Hi!

Excellent bug report, thank you!

This has been fixed in the new firmware that is currently in beta. If you want to try it out, please PM me your hub serial number and I can assign the new firmware to your hub.

@claudia thank you so much, that feature was my wish now for ages. I am very happy that you listen to your customers.

Hi, please refer to the newest topic. https://community.flic.io/topic/18233/release-of-mqtt-client?_=1674825212929
We now provide an MQTT client. 😎

@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