@slbickford THIS still works. Thank you

@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 ❤

@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 🙂

@fjolnir Please try again now.

Nowadays, the Spotify app is available for Android devices also. You can directly download it on the Google Store. After that, you can play Spotify playlists online via the Shuffle Play mode. With a free Spotify Premium, it has many limitations to listen to playlists.
If you'd like to get a better listening experience, the best way is to upgrade to Spotify Premium.
If there is something wrong happened, and Spotify not working well via the app, you can try to use AudFree Spotify Music Converter to download Spotify songs as local files after that you can still listen to Spotify playlist on Android via any music player instead of using the Spotify app.

@Emil It's been what? A year? "Still on the roadmap" Yes of couse it should be! WHEN? WHEN? How hard is it to understand? We will probably sit here in 5 years and you will say "Still on the roadmap guys!!!".

@siobhanellis I'm pretty sure that device's Homekit support is just for simple triggers and not for the "analog" dial. Do you have any further information regarding this?

@pascal-0

It's been... what, a year now since they came out (and the multiple years it was in development)? It's pretty obvious they have no intention of delivering on their promises.

@hugo-pc hi, I got a few twists and setup was quick and easy for controlling Sonos. But then when I upgraded the Sonos firmware, the twist and all of the flic buttons stopped working. All of these flics are connected to Hub LRs.

The issue is now fixed, flic pushed a new firmware to the Hub LR. It is now on version 4.2.13.

Thank you Flic 🙂

@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.

@Emil i received an update from Amazon Japan Alexa team. They said that Flic has found the problem and will fix this in the next release. Can you help share when the release will be so we can continue testing?

@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.

@anton Hello! I just wanted to update you and let you know that so far, everything you have helped me with on this project has worked quite well. I still don't have any clue how to autostart terminal, but so far it has not been hard to just restart it when I need. What I'm wondering about now is this - I've bought six more flic buttons to add (these will complete what I've planned on the virtual organ), and need to add them to the hub. I've got enough keystrokes left to assign to them, but am now wondering if I need to do anything to the python program to allow it to recognize them and send the internet request. Could you advise? I'm adding to this thread instead of starting a new one, in order for you to place it in context. Thanks! Diane

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

@Emil
Since version 2.1 of Matterbridge the dimmers should show up as 0x0101. Unfortunately I don't have the twist but for example my tuya dimmer is now shown correctly.

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.

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.

@oscar Hi!
Sorry to hear this. Yes, the pairing dialogue not showing up is the issue here but we are not quite sure what causes this.

Could you please try the following procedure and see if it fixes your issue:

Go to System Settings -> Bluetooth and turn Bluetooth off and then back.
Remove any Flic device in the list if there are a.

Go to System Settings -> Security & Integrity -> Integrity
In the left pane, select Bluetooth.
Make sure Flic is in the list and has a checkmark.
If Flic already has a checkmark, uncheck it and re-check it again.

Please let me know if this worked for you!

Kind regards

@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.