Fibaro button

Mine still hasn’t arrived… not sure how you got yours so fast!

So I whacked one together earlier in the week, it’s my first attempt, so please:

a.) go easy on the poor code
b.) expect bugs.

but it means the Fibaro button actuall shows up as a button in ST and allows you to assign actions for single, double, triple and quadruple clicks seperately :slight_smile:

Would LOVE for anyone to improve on it, because like it say, it’s not 100% yet!

Cheers,

Owen

1 Like

Good stuff! Looks like it uses similar central scene commands to the z-wave.me wall controllers.

Have a see if you can get it to recognise up to 8 x clicks (which I think is the limit for this device).

I’ll help out when mine arrives… if you haven’t already sorted the whole thing out!

1 Like

AdamV!

Hey yes it does. I know this because it was your code that I ripped off in the first place! So thanks for doing basically 99% of the work!

Owen

1 Like

Nice! - well it looks like I won’t be getting mine for a while as I ordered the brown one, and apparently there is no UK stock of this yet. They only have shipped red, blue, white and black ones… annoying and no eta!

Hmm interesting, I ordered one Red and 2 Whites, and only my Red one has arrived. - I spoke to Steve @ Fibaro who said they hadn’t had any stock of White Buttons in the UK yet :S

Better give him a call on Monday again!


I stopped at 4 clicks because that’s all that is supported using the standard button controller smartapp, also, i only really needed single and double click for my use case, (a button next to my bed to run routines like ‘night mode’ or ‘morning’/‘home’ etc

It also recognises holds and releases as seperate commands, I tried to get that to work, but the button always got stuck in the ‘HELD’ mode. - I think the expecation is that there is a seperate command for ‘HELD RELEASED’ but I couldn’t work out how to reliably get that to work.

The other issue is around the ‘wake up’ command, (which happens when you quadruple click the button) - It was throwing an error for a while, which i basically got it to ignore. - Not even sure what the wake up command should do, so I abandoned that.

Ok - so mine finally came - and I’ve made a device handler.

some key features:

  • it will register button clicks (up to 5) as button pushes for ST made apps
  • It uses ST’s numberOfButtons attribute so you should find even for some ST made apps you should be able to use all five clicks
  • I’ve made a special integration with CoRE, so that you can specify the exact number of clicks or use hold start, hold release and even hold length as triggers

enjoy!:

1 Like

Excellent!

How much physical pressure do you need to apply to the button? I don’t think I’ll get one as I have enough button controller devices at this point, but I’m bound to get asked in one of the assistive technology groups.

That is, could someone with limited arm strength Press it easily with an elbow or the heel of the hand? Could an assistance dog press it with their nose?

(For dogs, we don’t typically teach double clicks or long holds, we just set all the button variations to the same action. But there are a lot of buttons out there that the dogs can use. My dog can use a Flic button, a smartenIT 3 toggle, an Iris smart button, and a Logitech Harmony pop button. But he can’t use an Aeon minimote or a Securifi keyfob.)


not my dog, but mine knows the same behavior

I think it might be ok for assistive dogs but does need to be pressed straight down, not at and angle.

I’m just starting to train my dog to use it (not an assistive dog) for when he wants to go out and he’s tiny but just need to teach him to press straight down.

For human hands, it’s brilliant. Very well made and hasn’t failed me yet!

Kraeg

1 Like

I don’t think it requires much pressure… it’s a pretty simple device!

I am finding however that a lot of clicks are not registering. Sometimes the button just sends a wake-up notification rather than the info on how many times it was clicked! Very annoying

2 Likes

Yep - I’m finding it’s too unreliable to use daily. It’s definitely the device as well as I can see from the logs its reporting the wrong button press

1 Like

@AdamV you should give it a another go, I have two fresh ones doing just as supposed, thanks to your device handler that is.

1 Like

@einars I’m interested in getting a couple of these. Are your buttons still working well?

I returned them due to:
When you play around with them, they work perfect.
When they ”slept” for a while they were kind of unpredictable when they got activated again.

One push could easy become zero push.
Triple could become one, and then two pushes.
So for usage you need to be sure you got your one, two, three, four and such.
It’s not your option.
Ended up buying nodon octan for my usage.

If you want something cool, and make all kind of clicks start the same thing, you could get one.
But not worth it in my opinion.

That was basically my experience as well.

I’m playing with the Philio Smart button now. Seems much more reliable… however it’s a weird device so may not suit everyone’s needs.

Also - still using my trusty zwave.me & popp wall button controllers in every room in the apartment

1 Like

I have bought the Fibaro button for using it with the uk Smartthings hub. Except for the held, it works fine combined with the button controller smart hub. Now I can switch 4th activities usin the same device. Thank you very much!

2 Likes

Just sent back the Fibaro button. It would pair with an Almond+, I could add it to ST via the community device handler, and then it would do… absolutely nothing at all. I persevered for an entire evening trying to get it to play nicely, but to no avail!

do you use the UK ST or the US ST?

UK ST… does it work with one and not the other then?

The Fibaro button comes in two different models. One on the UK frequency and one on the US frequency. A Z wave device must exactly match the frequency of the hub that you are using (and the frequency cannot be changed after the device is manufactured). But as long as it paired, it should’ve been on the matching frequency, so it doesn’t sound like that was the problem.

It may just have been a bad device, it happens. :disappointed_relieved: