@ymsetjenesta Where do you see this? Can you send a screenshot?
-
Hi,
since I use the http request for many smart home solution to fire a tcp packet to a port, if I use the flic connected to a iphone, I get every time the message box "Internet Request: The network connection was lost".
Packet still work.
Is it possible to deactive the message?
With Flic Hub the message didn't appear.
Thanks.
-
Hi,
I have mac mini as a server (Mid 2010) and its lacks Bluetooth LE support.
I am assuming that anything built with Broadcom BCM20702 would work - but I'm assuming, and that doesn't always work out for me :)
Has anyone tested and confirmed working specific Bluetooth dongles on the mac with the Flic Mac client?
-
Hey guys,
Just bought my first Flic products!
Including a Hub 2.
Setting up was great and easy at first.
However, trying to program SmartThings….
It says the hub needs a firmware update. (For Homey, HomeKit, and SmartThings to work)
Then when I try to update, it says I have the most current version. Very frustrating.
I’ve tried both WI-FI and Ethernet as well as factory reseting.
Currently the hub is running 3.0.6
HELP -
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?