@rob-loosx This is an excellent idea, much more intuitive than "push and twist".
-
With the long promised Matter support now released I must say that I'm disappointed. Yes, it seems to work for anyone who wishes to stay in the Flic ecosystem, but one of the advantages of Matter is to enable interoperability between ecosystems and devices from different vendors, so the user can decide which ecosystem to use, or even use multiple ecosystems at the same time.
Flic allow me to see other Matter devices using their hub, but I can't use Flic on other ecosystems because there is no bridge that publishes Flic in Matter. That's half of the solution and it's the half I'm not using. I don't seem to be alone.
The Flic Twist was released about a year ago, it's great as a twistable switch and it works when used within the Flic eco system. It doesn't offer all of it's functionality in any other ecosystem, and it's not even fully implemented in their own SDK.
In this new dawn of IoT, major vendors, even ones that previously worked hard to lock their users into their own ecosystem, abandon exclusivity and embrace open standards like Thread and Matter. But not Flic. We're only offered full functionality within the Flic universe.
This may of course be Shortcut Labs strategy, but if so, I draw the conclusion that Flic know something that even Apple, experts in keeping users in their own ecosystem and still marching out and into Matter, have missed. I either don't understrand Shortcut Lab's strategy or – I'm not in their target group.
For Flic's sake (no pun intended) I hope there is some substance to the strategy of swimming against the stream. I'm on the brink of abandoning Flic because I cannot fully use the Twist in Home Assistant or Apple HomeKit. The only Flic product that can be well integrated in other ecosystems than Flic are my Flic 2 buttons. If it's just about buttons there are quite a few alternatives thad don't require an additional and quite expensive hub.
Please enlighten me if I have misunderstood something here.
-
I have successfully implemented the SDK to create an OSC module that send a trigger to QLab. However, it only works once. In other words, I press the button, it send the OSC string to QLab, everything works as it should. But then it's as if it stops listening for another button press. Am I missing something? Here is my JS in main.js:
var oscClient = require("./osc").create("192.168.1.202", 53000); var buttonManager = require("buttons"); buttonManager.on("buttonDown", function(obj) { oscClient.send("/cue/2/start", function() { console.log("message sent"); }); });``` -
hubsdk.flic.io is currently down. Please fix this.
-
I am using the SDK with various scripts, to send a webhook on button click.
Now that i also have the FlicTwist it still can only report up to 'SingleOrDoubleClickOrHold'. (see https://hubsdk.flic.io/static/documentation/)With the added functionalitity of the FlicTwist i would like functions/types such as '3h-double-click' or '9h-hold'. And off-course 'TwistLeft' and 'TwistRight'.
Any timeline for a new SDK with FlicTwist-support?
(or is there a work-around with the current version?)