@Emil There are 2 total mentions of the hub on that page. One is an tiny numeric annotation that takes you to the fine print of the bottom of the page. The second is a single bullet in a list of other items. In my opinion, it’s not prominent enough if the entire integration relies on it. I understand it is on your customer (me) to read it all in detail. More set up explanation / troubleshooting would be helpful. The set of Wemo switches that the hub can not find are the newer small model WSP080. I have several Insight switches and model F7C063 that all come up no issue. Thanks.

Still waiting for Siri <3

@anton said in Flic for Mac?: @tcbeatie Cool! Good that you solved it. Regarding the triggers, as you see we do provide the "raw" buttonUp and buttonDown events. This means that you should be able to create a script in which you can define your own click types. Also, have a look at flic-service-osx if you ever feel like making something even more complex ;) I saw references to that, but not sure how to implement. Easiest might be a triple click? My current use case is a button in the kitchen that controls the mac next door; volume up/down/pause|play is easy.. A triple click to do something cool like speak the weather would be awesome :)

In order to play Spotify playlist on Android, you can try to download and save Spotify music as local files via DRmare Spotify Converter. Then you can move the music files to your Android devices for using directly.

@bashar_8383 If you get "Client EOF" in the flicd log, it simply means the client connecting to flicd has gracefully exited. I suggest you to ask the people working on home assistant for this kind of issue.

@bambi2000 Thanks. I did manage to get the basics working (as well as find the streams for P3 and P4 :-) ). I also managed to group players by setting CurrentURI of the "slave" IP to the UUID of the "master". <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetAVTransportURI xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"><InstanceID>0</InstanceID><CurrentURI>x-rincon:RINCON_XXXXXXXXXXXX1400</CurrentURI><CurrentURIMetaData /></u:SetAVTransportURI></s:Body></s:Envelope> Now I just wish Flic would create some sort of copy function to make it easier to reuse those commands:-) And that Sonos would open their official API for better integration and remote control.

Congratulations on having the sincerity and transparency to make this honest though painful admission.

@anton Hi anton - the program is running well - thanks again for your help on that. I have googled how to get a python script in terminal to autostart, but I am overwhelmed by what looks like outdated information, and coding language I'm not super familiar with. Can you give me the step by step information to get that last piece set up? I did manage quite easily to set up a static IP address, so that's working as well. It's just the autostart part that I haven't got down yet. Thanks! Diane

If you want more advanced control over your LIFX devices, I wrote a blog post with a few examples of how to leverage Photons Interactor to do some really nifty stuff, including starting/stopping Tile and Beam animations.

@amir Thanks for the clarification. It's greatly appreciated. As you can see, quite a few people didn't take the videos that way. As a result, your update helps to set the expectations appropriately. I look forward to becoming a fan once we reach that plateau. Best of luck on getting there.

I also have a problem controlling wemo lights from flic app (when using the hub). I am using the same LAN. It works fine with my Wemo Switch but the flic app can't find my lights, even though they work fine with the wemo app.

@oskar I also think its really sad, that there was never any follow up considering developer access from your side although this was mentioned in the indiegogo. There you state "basically an advanced Linux computer, much like a better-looking Raspberry Pi, with a two separate Bluetooth controllers (yep, two)" but a bird (in this case the Raspberry Pi) in the hand is worth two in the bush. I would really appreciate having ssh access to the flic hub to do custom scripts. One way would be to provide a standalone linux version so you don't have to worry about security of the platform for yourself. Much like the solution you offer with the fliclib-linux-hci on github where you can run your own flic server. I was hoping this would happen with the flic hub too.

@emil - do you know when the latest bug fix will be released to Google Play? I am unable to use my Flic buttons because of the Tasker bug - I am being very patient! The last update appears to have been released in August.

The latest version of the app has built in support for multiple Flics.

Same issue - local request works on phone but the exact same set up fails on hub.... really annoying.

@Emil Our client is sending 4 buttons to a tender and with the issues that are happening on version 8 could we request the following buttons also be placed on version 7 for the mean time. They are BA48 – A39996 BA48 – A54514 BA48 – A54466 BA48 - A51788 It would be greatly appreciated.

@bertrandom done

Was thinking of getting a hub but not interested if it does not work. I have the same issue and any other chrome cast function just does not work. I have 2 phones and one works perfectly fine when the other one doesn't so it just seems to be a software issue or it could be not having a certain permission on my phone. But I have allowed everything I can think of and there should be more information on what permissions I need to enable. The fact that this is a problem and nobody has been able to get a fix for months makes me wonder if this will ever get fixed.

@romuald Yes!

@edufediaz-publi Yes, that's what we do in the Flic app.