I wanted to share a video showing how I’ve used Flic 2 buttons to control integration in a dedicated home theater. Hope you like it and it gives folks some ideas for how to use Flic buttons a bit differently. Thanks!
-
I've exhausted my stock of Flic 2 buttons and thought I'd head back to my Flic 1 buttons for some new automations. I'd forgotten that across a set of 5 of them, they all have one of the below 2 issues:
put a battery in and the light turns on solid and does not turn off put a battery in, the light turns on, then off, and then responds to a few button presses before not powering up any moreI've not been able to find anything via search, since it all just blurs into queries about the Flic 2.
Is there anything I can do to fix the older buttons? I'm assuming since all of mine are doing this it must be a known problem. I'd much rather spend some effort getting them working than send them to landfill 😞
-
I was developing a module on the Flic Hub using the Flic Hub SDK. The module sends out all button presses as UDP messages.
While working on the module, I noticed a strange bug, which I assume is a firmware issue - when sending the 36th UDP message, the module crashes with a
FATAL ERROR: uncaught: 'cannot push beyond allocated stack'I made a minimal module that will reproduce the bug consistently:
var dgram = require("dgram"); function SendJSON(data) { try { udp = dgram.createSocket("udp4"); udp.send(data, 32768, "127.0.0.1", function(err) { console.log("UDP sent. Return: " + err); udp.close(); }); } catch(e) { console.log("Error sending button state!"); } }; var i = 0; var myInt = setInterval(function() { i ++; console.log("Sending packet " + i); SendJSON("" + i + " "); }, 100);Flic Hub SDK Console output:
Sending packet 1 UDP sent. Return: null Sending packet 2 UDP sent. Return: null Sending packet 3 UDP sent. Return: null [...] Sending packet 34 UDP sent. Return: null Sending packet 35 UDP sent. Return: null Sending packet 36 FATAL ERROR: uncaught: 'cannot push beyond allocated stack'I consider this a firmware bug because of the following reasons:
the "fatal error" is not catched by the try-catch block the module is still considered "running" even after the crash (the SDK's "play" button stays in "can be stopped" state)Is there any solution to this?
-
Title says all. The ifttt can only see the flic and tags connected directly to my phone. All the flics and tags connected to my hub do not show in ifttt.
I already disconnected and connected everything and deleted and created again everything many times. It still does not show.
Help is much appreciated!! Thank you!
-
Hi all,
I posted some simple SDK scripts that may be of use to some of you:
https://github.com/loosrob/Flic-Hub-SDK-scriptsRight now, the following example scripts have been added, but more may follow:
Send UDP message to other home automation systems, so they can act on Flic button clicks Turn device on Homebridge on/off Change settings on Yamaha AV receivers Play random album on KodiBest,
Rob