@jitmo I'm not a multicast expert, but I would suggest you to use any example code you can find on the web for Node.js for server and client, make that work, and then just put it on the Flic hub.

@ems220 what is the LED colour and pattern on the button when you try to connect?

We're on holiday and will answer your support ticket when we come back later in August.

@alastairjamieson seems like a bug. Will fix later in August.

@ems220 exactly what message do you get? The only time the setup should fail is if the button already has an active connection ongoing to another device (requires the devices to be in range).

@antonio-mestre the net module implements just a raw TCP socket. The secure web socket protocol uses the Websocket protocol on top of the TLS protocol on top of the TCP protocol.

Right now our sdk unfortunately does not include modules for TLS (but we have https) nor Websocket, so you would have to implement that yourself if you want to use wss, using the net module in the bottom for TCP.

Hi,

The IR device consists of a transmitter and a receiver, which are separate.

If you can record signals in the IR provider in our app but your device does not react when played back, and you have tried this for multiple devices, it might be that either the hub pcb or ir accessory has become broken.

For support and warranty requests please contact us at https://flic.io/support.

@akira We have activated Alexa in the Japan region so don't really know why this is happening. You could maybe try another Alexa region such as US.

@jamie-m-garner Yes. The Alexa integration is a cloud to cloud integration.

@paul-mckibbin Our Alexa integration is a cloud to cloud integration. After you have set up Alexa, you could theoretically throw out the Alexa device through the window and uninstall the Alexa app and it should continue to work, assuming you have set up Alexa to perform another cloud action (initiated by Alexa cloud)...

So I can't understand why the app version in your phone is important.