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)?