Hi. Not right now, since we now use Duktape (https://duktape.org) as the javascript engine, which does not support promises and async. Maybe we will change to JerryScript or something in the future if there is a demand for this. We could potentially add some polyfill for promises but in that case I think it's better to get something that supports async.
Nice!
This is great work, like to see more of this.
Our runtime is not 100% compatible with node.js and you can't directly install npm modules. However you could try copy-paste the source code into our IDE and maybe it will work.
We don't have any magic basic auth rewrite on the hub, compared to iOS.
Please see https://community.flic.io/post/18192 how to do it manually instead.
Hi. We use dhcpcd-8.1.9 (https://github.com/NetworkConfiguration/dhcpcd/tree/dhcpcd-8.1.9). You are free to investigate the code there to see if you can find any cause of this. Other than that, nothing on the Flic hub sends out dhcp requests.
@xAPPO you can have a flic paired with two hubs. When pressing the button it will simply connect to the first one that responds. The hubs otherwise don't "talk" to each other.
Everything runs from a read-only system, so i doubt malware has gone into it. Probably just some bug in the widely used Linux OS we run on it if anything.
I would be glad if you could share Wireshark logs or something of the packets you are seeing.
Hello. It works for us. You could check in Wireshark or something if the Sonos answers to the ssdp requests we send out on the LAN.
@editdave it's written on the back of your hub. It can also be changed in the app.
Did the record part work all the time, while the playing part failed all the time?
Are you using the 1st hub generation or the 2nd (Hub LR)?
Please add the following line at the top of your file:
Buffer.from = function(v) {return new Buffer(v)};
I think that should work.
@flic-io-2 Hmm this will not be possible using the Flic app. You could create your own app using our sdks that does what you want if you can build it yourself...
If you have a "Bearer" token, just add a header named Authorization, with the value "Bearer your_token".
What you should do is to first call bind, followed by setBroadcast(true) on the socket. Then you can send messages using send.
FYI, the API is made to be compatible with Node.js API https://nodejs.org/api/dgram.html.
@rob-loosx The hub sdk is pretty standalone from the flic app. You can have code running all the time. You can also interact with buttons (such as scan new buttons and get button events when they are pressed).
@info-6 If something is not working, please send a complete description at https://flic.io/support.
@chrismcband You need to add the Alexa action to the Flic button first in the Flic app and then press done/save and then back. At this point the configuration will be synced to our backend.
Then it should be visible in the Alexa app, assuming you have logged in to the same Flic account in the Alexa app.
Just add the Alexa action to both Click and Double Click in the Flic app.
Ok we have finally released this now!
See https://flic.io/flic-hub-sdk for more information.
@agheler You need to make sure you have internet connection on your iPad. Then also make sure you actually save the action by pressing "Done" inside Alexa action configuration, and then press the back button to reach the main view.