@stevehooper yeah we should really try to add a direct Home Assistant integration from the Flic hub someday, since it is so popular...
In the meantime, can you use the Internet Request action in our app to send a simple http request to your device running Home Assistant maybe?
We are today announcing a Beta release of some new features in the Hub SDK that can be used together with Flic Twist.
In order to seamlessly continue to work with the rest of your smart home devices that you might have assigned to other triggers on the Flic Twist, we introduce the concept of Virtual Devices. A Virtual Device is handled by the Flic Hub firmware just like any other supported real device, but its functionality is implemented by the user in the Hub SDK, typically by writing some kind of bridge software that sends commands and receives update events over the LAN to/from the real device. If for example the brightness of a (real) light is changed by some external means, it is possible to tell the Flic Hub firmware from javascript about the new brightness level, which the hub then forwards to the Flic Twist, so that the LED status can update accordingly. That way when you twist it, it will start from the correct position.
We are also adding a "message" action that can be used to send arbitrary strings to your scripts whenever the action is triggered. The intended use case is to be able to trigger custom code also for Push/Double Push in the Selector feature or perform some action when a specific point is reached in Advanced Dimming or Scene Blender.
The virtual devices can be created in the Flic App and be set to be controlled by a Flic Twist as follows:
Using this piece of code, updates are received in your javascript code after configuring a virtual device to be triggered in the Flic App for a specific Flic Twist:
const flicapp = require("flicapp");
flicapp.on("virtualDeviceUpdate", (metaData, values) => {
// The values object can contain hue, saturation, brightness, colorTemperature, volume, position (for blinds)
console.log(`Twist ${metaData.buttonId} updated virtual device ${metaData.virtualDeviceId} of type ${metaData.dimmableType} with these values: ${JSON.stringify(values)}`);
});
When a device is modified externally, we use this function to inform the system of the change:
flicapp.virtualDeviceUpdateState(dimmableType, virtualDeviceId, values);
The dimmableType can be either "Light", "Speaker" or "Blind". The values is an object containing at least one of the fields mentioned above that is appropriate for the corresponding dimmableType. For example:
flicapp.virtualDeviceUpdateState("Light", "my_ceiling_light", {hue: 0.6, saturation: 0.7, brightness: 0.8});
The values themselves are always floating point numbers between 0 and 1.
Configure an action message to be triggered by assigning the following action in the Flic app:
The action messages are easy to receive, just register a listener as follows:
flicapp.on("actionMessage", message => console.log(`Got a message: ${message}`));
We'd love to hear your feedback!
We are slowly rolling this out in different regions. Stay tuned.
@abboberg All our firmwarers are auto-updated. In some cases we have assigned a specific firmware to specific people on request. Please reach out to us if you want to go back to the public release track.
The current hub fw version is 4.2.11.
Usually when we update the hub firmware we also update the apps. In the apps you can see a Change log in the settings menu.
@steveff Our Matter integration is just around the corner. For the Twist this is probably most relevant for lights, as no speakers I know yet support Matter.
What we also have in the pipeline for Twist is e.g. more configurable steps (4 -> 12) for Advanced Dimming/Scene Blender so that you can trigger an action (e.g. Alexa) with higher resolution and before as well as Hub SDK features for the Twist so that you can build custom integrations.
Spotify has an API (over cloud) that we could potentially use for controlling the volume, but we are not sure if the latency will be low enough to make this action have a good user experience. We also don't like that they don't provide any means to "push out" the volume status when it is changed so that the LEDs on the Twist could update accordingly (https://community.spotify.com/t5/Spotify-for-Developers/Access-to-websockets/td-p/4955299).
@hello_marley the ball is moving according to plan. Please stay tuned 
@giannis-yt I would guess at the moment the Raspberry Pi Zero Wireless is one of the cheapest options.
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.
Hi. You need to manually construct the Authorization header. See https://en.m.wikipedia.org/wiki/Basic_access_authentication.
@beachb_sl the buttons communicate using Bluetooth, not wifi. May I ask you where you have read that they use wifi?
Bluetooth Long Range is a feature introduced in Bluetooth 5.0 (also called Coded PHY) which uses error correcting codes so that the receiver can restore the packet content even if a few bits are lost.
@beachb_sl yes and of course the main difference that gives the name to Hub LR: Bluetooth Long Range.
@gerald That is very strange. Could you please shoot a video showing where you hold down the pin hole for 10-15 seconds (not less, not more), also including the LED indicator in the video?
@gerald Where did you read that you should hold down the pin hole for 15 to 40 seconds? Our manual at https://flic.io/manuals/flichublr states that you need to hold it down for 10 to 15 seconds. Please try this.
@beachb_sl Cryptographic functions are not part of the javascript language itself, but typically included in browser APIs or e.g. Node.js environments.
To use SHA-256 encryption with the Hub SDK, use a pure javascript implementation. You should be able to find that with a simple online search.
If you want to run TypeScript, my suggestion is to transpile it to javascript first.
@gianni It appears that alexa skills can only be linked to one account. So you should either use the same flic account for all your flics, or you need to create three amazon accounts and link each to each flic account.
@gianni You can assign the Alexa action to as many Flic buttons as you wish. There is no limitation.
@claes-jacobsson No idea. I guess you could try to connect to some port maybe. I don't know anything about Apple TV's network usage unfortunately.
@claes-jacobsson We have mDNS functionality but it is in beta so it is not documented yet.
But you can refer to the following code samples in the meantime (monitoring Sonos devices):
const mdns = require("mdns");
// Service browse:
browseHandle = mdns.serviceBrowse(null /*or interface string*/, "_sonos._tcp", function(obj) {console.log(JSON.stringify(obj));})
Output:
{"add":true,"interface":"eth0","serviceName":"Sonos-38420B7D0C12@Meeting Room","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"eth0","serviceName":"Sonos-C43875785444@Kitchen","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"eth0","serviceName":"Sonos-B8E937B9C4EC@Dev","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"eth0","serviceName":"Sonos-B8E937EE3C04@Dev","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"wlan1","serviceName":"Sonos-38420B7D0C12@Meeting Room","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"wlan1","serviceName":"Sonos-C43875785444@Kitchen","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"wlan1","serviceName":"Sonos-B8E937B9C4EC@Dev","regtype":"_sonos._tcp.","replyDomain":"local."}
{"add":true,"interface":"wlan1","serviceName":"Sonos-B8E937EE3C04@Dev","regtype":"_sonos._tcp.","replyDomain":"local."}
browseHandle.cancel(); // Stops the monitoring
// Resolve a service instance
resolveHandle = mdns.serviceResolve("eth0", "Sonos-38420B7D0C12@Meeting Room", "_sonos._tcp", function(obj) {console.log(JSON.stringify(obj));});
Output:
{"interface":"eth0","fullname":"Sonos-38420B7D0C12@Meeting\\032Room._sonos._tcp.local.","hosttarget":"Sonos-38420B7D0C12.local.","port":1443,"txtEntries":{"bootseq":[56,54],"hhid":[83,111,110,111,115,95,76,68,99,69,97,107,111,56,74,56,52,121,102,99,114,54,75,49,89,69,109,48,104,57,99,111],"hhsslport":[49,56,52,51],"info":[47,97,112,105,47,118,49,47,112,108,97,121,101,114,115,47,82,73,78,67,79,78,95,51,56,52,50,48,66,55,68,48,67,49,50,48,49,52,48,48,47,105,110,102,111],"infohash":[52,71,105,56,85,107,108,80,100,68,76,73,112,118,65,99,53,111,75,108,112,87,76,53,102,101,97,110,118,74,106,57,74,73,102,54,95,84,81,109,98,102,103],"location":[104,116,116,112,58,47,47,49,57,50,46,49,54,56,46,51,46,57,58,49,52,48,48,47,120,109,108,47,100,101,118,105,99,101,95,100,101,115,99,114,105,112,116,105,111,110,46,120,109,108],"locationid":[108,99,95,102,57,99,98,52,100,99,54,51,52,55,97,52,53,53,102,56,52,56,97,48,51,101,99,55,52,51,100,52,52,48,98],"mdnssequence":[48],"mhhid":[83,111,110,111,115,95,76,68,99,69,97,107,111,56,74,56,52,121,102,99,114,54,75,49,89,69,109,48,104,57,99,111,46,89,77,77,122,112,67,49,49,72,89,51,79,57,95,110,74,98,70,97,49],"minApiVersion":[49,46,49,46,48],"protovers":[49,46,52,48,46,48],"sslport":[49,52,52,51],"uuid":[82,73,78,67,79,78,95,51,56,52,50,48,66,55,68,48,67,49,50,48,49,52,48,48],"variant":[49],"vers":[53],"wss":[47,119,101,98,115,111,99,107,101,116,47,97,112,105]}}
resolveHandle.cancel(); // Stops the monitoring
// Get IP address
getaddrinfoHandle = mdns.getAddrInfo("eth0", "Sonos-38420B7D0C12.local.", /*IPv4*/true, /*IPv6*/false, function(obj) {console.log(JSON.stringify(obj));});
Output:
{"add":true,"interface":"eth0","ip":"192.168.3.9"}
getaddrinfoHandle.cancel(); // Stops the monitoring
When you see "add": false, that means the device's dns-sd entry has expired, i.e. the device has not renewed its entry before it expired. You can either monitor all devices of a certain type (serviceBrowse) or monitor a specific host (getAddrInfo).