These boards are new.. so hopefully this is the beginning of a vibrant community and I'm asking in the right place.

I found Flic because I was looking for a simple bluetooth button that I could use to drive home automation. Flic seemed to fit the bill, especially with the implementation of the Linux SDK in response to the request for that feature.

I have an RPi3 that is my test device, with Raspbian Jesse installed. So this is about as simple/straightforward as it gets - no weird bluetooth dongles to play with, nothing exotic like Arch - this should be the most straightforward works-out-of-the-box implementation possible.

The instructions are included at the github repository. They are easy enough to follow, although incomplete for RPi3 - there a few additional libraries needed in order for bluez to build properly.

The troubleshooting steps at the end were helpful and needed to get basic connectivity going. So that's all good.

However, in the end, I was not able to achieve connectivity following the instructions. I went to create an issue on github, only to find after hours of debugging that the issues I ran into were already known: there are known problems with versions of bluez newer than 5.37, although this isn't mentioned in the instructions at all. So anyone following the instructions given will fail.

I'm coming here to request that for Linux developers, an RPi3 has got to be the most basic out-of-the-box hardware that should just work. As in, it should be extremely well-tested that a new developer getting started following your instructions will have success. The barrier to entry here is extremely low - we can buy an RPi3 for about the same price as a single Flic button. So my request is to focus on the RPi3 as a "reference platform" and nail down that new developer experience to make it smooth.

Then if developers want to branch out and go crazy with C.H.I.P. devices or Arduino or some other ARM or x86 platform and you want to support those too, great. But this is my request to please at least make the RPi3 onboarding experience rock solid. I expect you'll have a lot more uptake and people singing your praises if you can tap into the millions of RPI users and make them happy from Day 1 using your product.

Thanks for listening.

These boards are new.. so hopefully this is the beginning of a vibrant community and I'm asking in the right place.

I found Flic because I was looking for a simple bluetooth button that I could use to drive home automation. Flic seemed to fit the bill, especially with the implementation of the Linux SDK in response to the request for that feature.

I have an RPi3 that is my test device, with Raspbian Jesse installed. So this is about as simple/straightforward as it gets - no weird bluetooth dongles to play with, nothing exotic like Arch - this should be the most straightforward works-out-of-the-box implementation possible.

The instructions are included at the github repository. They are easy enough to follow, although incomplete for RPi3 - there a few additional libraries needed in order for bluez to build properly.

The troubleshooting steps at the end were helpful and needed to get basic connectivity going. So that's all good.

However, in the end, I was not able to achieve connectivity following the instructions. I went to create an issue on github, only to find after hours of debugging that the issues I ran into were already known: there are known problems with versions of bluez newer than 5.37, although this isn't mentioned in the instructions at all. So anyone following the instructions given will fail.

I'm coming here to request that for Linux developers, an RPi3 has got to be the most basic out-of-the-box hardware that should just work. As in, it should be extremely well-tested that a new developer getting started following your instructions will have success. The barrier to entry here is extremely low - we can buy an RPi3 for about the same price as a single Flic button. So my request is to focus on the RPi3 as a "reference platform" and nail down that new developer experience to make it smooth.

Then if developers want to branch out and go crazy with C.H.I.P. devices or Arduino or some other ARM or x86 platform and you want to support those too, great. But this is my request to please at least make the RPi3 onboarding experience rock solid. I expect you'll have a lot more uptake and people singing your praises if you can tap into the millions of RPI users and make them happy from Day 1 using your product.

Thanks for listening.