@Emil I don't see that. I can add what each click does in HomeKit but nothing happens.

QLab is listening for osc on port 53000, and osc message is /cue/{cue_number}/go
Here is the dictionary, if it helps.

https://qlab.app/docs/v5/scripting/osc-dictionary-v5/

For our use in the theatre, I think we'll mainly use this message. And then put buttons around for the actors to push.

I started to make an Home Assistant Integration a while ago. You can find it here: https://github.com/JohNan/home-assistant-flichub

I never completed it completely but I think it should work partially at least.

It uses a TCP connection for communication that has to be setup on the Flic Hub. A linked repo is available in the above repo.

I also just noticed that Flic have released a MQTT client which should make it a lot easier to create an HA Integration. I might give it a shot to convert this one to using MQTT instead.

@Emil
Okay, that's a shame but thanks for answering.

Maybe a suggestion for the next iteration of the hub?

@Emil Thanks for the reply. I started working by itself shortly after I wrote the question 😄, but I will try this if it happens another time 😄

@Yarrow Hi there! Alexa does not have a limit, rather it's a matter of how many Flics can be connected to the phone or the Flic Hub. I hope it helps! Best regards, The Flic Team

@ledtear are you using the lifx cloud action or the lifx lan action? Are the lights already on the same wifi (they need to be set up using the lifx app first)? What model of the lifx do you have?

@simonbrohus794
Hi!

Yes, there is!

You can use Flic Universal to configure the Flic button to act as a Bluetooth keyboard and program different key combinations to be triggered when you press it.

You can read more here:
https://flic.io/flic-universal

@xAPPO @par-stalberg @scanner Here is the newest post from our side, I figured it might be interesting to you... have fun! ☺