@Emil It was before the factory reset which put it back to 3.0.3 as reported in the app. I heard via email that someone fixed it in the backend and I should be able to try updating again, just checked for updates and now it is back on 4.2.4 as of 2 minutes ago.

Thanks!

@mp What exactly do you mean when you say "network loop"? This is not a problem we have heard of before, so any more info would be helpful.

First, connect the Hub to the network using the cable and provide an IP using DHCP. Then connect the Hub using Flic Hub SDK. Then Please use the command 'network state' at the command prompt. You will get the MAC address.

@jonasnordstrom Hi! This is fixed in the new beta version 5.5.3!

@psanner The combination we support right now for HomeKit is the Flic Hub LR together with either Flic 1 or Flic 2.

@MagAa

Hi Magnus! Old colleague from Nationaltheatret here.
I guess you already had your show, and found a solution by now.

But i've written a simple Node.Js Server to achieve what you want.

you'll Need the hub, but that could be connected with WIFI or Ethernet near or on the stage.

Then my script receives the HTTP request from the hub to the show computer running the server, and sends OSC messages to QLab.

I have made an Alpha version of this, and i will upload it on my github tomorrow.

https://github.com/IkaKomura

Håper det står bra til!

Bernt Karsten Sannerud

For more information, please read https://stackoverflow.com/questions/2678551/when-should-space-be-encoded-to-plus-or-20.

In the current firmware version, a + in a query string is translated to %20 before the request is being sent. So, your device will receive the query string 1%20PowerOn, which should be interpreted exactly the same as 1+PowerOn.

In the next firmware version, we will no longer translate + to %20 anymore.

@ronsell I had the same issue, I removed the hub from Apple Home, then reset the Flic Hub, then went through the entire process of setting up the hub and then setting up the Flic button. It now works as expected.

Which bit should work?
Updating the firmware,
Discovering the devices in Alexa,
or
Adding a Smarthings device?
Or Possibly all 3 ?

What has been changed?
I can't test until I get home in the next couple of hours !!

@idoygr Hi there! Please note we will be sending you a replacement for the Hub. Could you please contact us to laura@shortcutlabs.com with your updated address details? Many thanks!

@eric-dsouza so today i deleted the Flics from the hub. I then re-added Flic A to the hub and re-connected the device to the routine in Alexa, it worked! I then did the same with Flic B, and now they both work! let's see how long it stays working

@robarammisc
Hello!
We use this script with the hub at Nationaltheatret in Norway, and it works super nice!
I have put two buttons on two different phones, so that the actor who answers the phones, push the button, and it sends an osc-command to Qlab to stop the ring ring que.
The hub is about 20meters away from the buttons, and we have 350-370 audience every day.

@MediaMan sure!

Just pair each flic to each hub and assign the same configuration for every hub for a specific button.

Note that Smartthings can only be used with one flic hub though, per Samsung account, due to a technical limitation.

@Emil has this issue been raised, that we can only add a single Hue bridge (even if two are detected) to a flic hub LR?

@treegartner
Seconded.. I had a reply about a bug fix in latest FW but no reply from Flic?

If you don't configure WiFi on the hub, it should not emit any WiFi signals as far as I know... Do you see something different?