Great write-up!
One question: will the fliclib still grab the bluetooth chip exclusively and making it unable to function with other bluetooth devices? More precisely, do I need to get a seperate bluetooth dongle just for the flic buttons?
Hi
I also have a flic button I want to include in HA. Should I still follow the steps 1-4 as above or has anything changed since then with new versions of HA?
are all 4 steps necessary for installing flic or either 1-3 or 4?
if you want the Flic Server as a Service, so you need to install as a System Service (4). So you didn’t musst the service start manuel after every boot.
But i have HA now as Hass.io and there doesn’t exist Sudo…
Is it just to repeat step 3 to add more buttons?`
Edit: Just realized that it is just to press down the next button 7 seconds and it will show up! Awesome!
Hmmm. I’m having some major issues with my buttons. Really hope someone can help out!
I’m running a Pi3 with Hassbian and Home Assistant 0.52.1 and I currently have 3 Flic buttons. After a reboot/startup of the Pi the buttons seems to be working just fine. But after a while the buttons does not work anymore and I need to reboot the Pi. I can’t find any buttons using the startScanWizard either…
Anyone that can help me troubleshoot?
Thanks!
I will try the addon later this week if I get the time.
I did do a complete re-installation of my system and and the buttons seemed to work just fine. It actually worked for a couple of days without issues. Then I decided to install a USB webcam (using this guide: https://home-assistant.io/blog/2016/06/23/usb-webcams-and-home-assistant/ ) as the last part of restoring my old setup. After this I got the same problems as before (buttons working for a short time after boot, then not responding)! Could motion in someway cause issues with Flic-service? It seems a bit far-fetched, but I can’t remember doing any other changes to my working setup…
I have just installed newest version of Hassbian with HA 0.57.3 and want to integrate flic again but I am still not quite sure how this can be done the best way.
It seems that there is more than one way according to the previous posts.
In what folder on the pi should the files be placed. I have put them in the home folder but it does not Work.
weird enough, on my RPI 2 with a USB bluetooth and venv install I needed to disable the /etc/systemd/system/bluetooth.target.wants/bluetooth.service by commenting the [Service]
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth
[Service]
#Type=dbus
#BusName=org.bluez
#ExecStart=/usr/lib/bluetooth/bluetoothd
#NotifyAccess=main
##WatchdogSec=10
##Restart=on-failure
#CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
#LimitNPROC=1
#ProtectHome=true
#ProtectSystem=full
[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service
I got too many WizardBluetoothUnavailable which conducted me to say that the bluetoothd daemon was interfering with Flic as stated in the Flic readme.
Everything work now yeah!
… Now I’m trying to install the flics and the link cant be found… NOOO
@Underknowledge I also tried to reinstall HA and flicd and came across this link:
It installs flicd in a docker container. Works flawless
1 Like
Atm on it 
always missing the flic Linux SDK install instructions for now- but I’ll dig me thru i guess.
AAAH! I have to install the docker first!!11
curl -sSL https://get.docker.com | sh
btw! Found the “hidden” guide for the other ones who want it more complicated xD
sudo wget https://github.com/50ButtonsEach/fliclib-linux-dist/archive/1-beta3.tar.gz
sudo tar -zxvf 1-beta3.tar.gz
uname -m (should get you armv7l)
cd armv7l
./daemon -l -f flic.sqlite3
but this docker is stupidly easy!
but i have to use “sudo docker xxxyyyyyyyyy” first. Did i do something wrong there?
Try to run this command and then logout and login again to get rid off sudo:
sudo usermod -aG docker $(whoami)
Hi,
I have hassbian on a 3+, is it safe to say your instructions should still work?
I’m a complete novice so before I dive in I just wanted to know if it’s still valid?
Thanks
Paul.
i use Hassio on a Raspi with 73.01 and it’s works
Sorry to bump this.
Had to reinstall Hass after a SD failure so updated to HassOS on my Pi3B+.
I found out you dont need to use the BT addon but am now stuck at using the flicd ‘addon’:
Available HCI devices found:
hci0
Trying hci0
Successfully bound HCI socket
Flic server is now up and running!
Error: Timeout while initializing HCI, exiting. Try restart the program or replug your Bluetooth controller.
I get htis error constantly.
There is so much convoluted information around flicd depending on which version/build/hardware you are using, I’m struggling to know where to start with the new HassOS!
Anybody able to chip in a point in the right direction?
1 Like
Hi thank you for the guide @Schmidij_ch 
works perfect but i think i can only use RP3 bluetooth only with flic, cause when ever i start the service i lose connectivity to my Xiaomi BLE Temperature and Humidity sensor.
Is this to be expected ?
Thank you and wish a happy new year !
For the ones still trying to integrate Flic buttons. After I had my Flic service running on 3 different machines in the course of time the setup process did go on my nerves.
so How Ludeeus is always saying automate, automate, automate, (I pressed cmd+v here)