Fibaro the Button Problem

[fi-bar-oh 47]

Not sounding like a great panic button solution...

[kandetvara 3]

Same here - I have 2 Buttons and for the first couple of days they worked like a charm. Now one month later they are simply not usable. They only respond after a couple of clicks, like "waking them up". Sometimes they do not respond at all anymore. In the GUI you just see a flicker of the green text (not sure what it is exactly saying) once pressed. It does not show how often it got pressed anymore and no programmed actions are conducted. Doesn't matter if programmed in LUA or Magic. I am running 4.100 on an HC2.

 

Completely useless. I already sent one back which was exchanged but the same behavior started weeks later....

 

kandetvara

[Sankotronic 2,370]

I just changed Wakeup interval to 4000 sec. and now it works. It was not touched for two days and it just accepted my two push command from first try. If this proved to be ok then I will order few more. I need at least one more for setting our coffee machine to ready state  

[kandetvara 3]

Mine was always sitting at 4000 sec. Did no difference. Tried to Change it to 3000 just for fun - doesn't work - Defaults always back to 4000.

This Thing is really Buggy....

 

But I heard that there are some People out there who do not have any Problems. Others though have the same we have...

[LP1 0]

Ok i searched a little bit further.

The button sends zwave communication to the controller (i see the blue led flikkering on the hc2) but the icon in the screen didn't display the 1X and didn't work.

This is not only if the button is long time unused but also random in normal use.

It looks like that the communication is not right every time.

The button is one meter from the hc2.

 

[tinman 1,070]

well, i sniffed with Z-Wave Zniffer, on both "broken button" which was send back by customer and "working" button which i used before. I have not found any issues on the hardware itself. For sure this is not a prove, as i should normally use more than one "broken" devices, but here is where Fibaro have to check it. As i wrote before, associations might not work immediately, and it might be an issue with magic scenes (not confirmed with button, but observed on other devices in earlier HC2 fw version).

 

For these who wish to check if this have something to do with their scenes: Create new LUA scenes, and run them manually. They will simulate button click (they will send scene event to HC2, in this way one can check everything on HC2 without any RF communications check).

 

Scene to emulate 1x click:

 

Please login or register to see this code.

scene to emulate 2x click

 

Please login or register to see this code.

and so on ... so when you run these scenes, HC2 will think the button has been pressed and will run whatever scene you have set to do something on button push. So even if button is broken, or some communication issues exists, you still can see if your scene is running properly.

 

Btw., i do use such scenes to control e.g. our Sonons Plugin, where one big scene is checking if button was clicked 1x, 2x, 3x, 4x ... and doing whatever i wish to do, and these emulation scenes are only to emulate clicks (what for? simple, i wish to have one scene where the customer can no do anything, and lot of small scenes which can be easily used e.g. to run exact same action as if customer would push the button, e.g. widget scenes which emulate 1x and 2x). It this way is easier for us, and faster to support. I think this API has been not yet made public (i have not found anything on developer.fibaro.com), it belongs to plugins API but it can be used for any kind(?) of centralscene emulations (without hardware interaction).

[twanve 18]

Same problem to me, spend € 50,- and unstable

Pusch 10 times and 2 times it works. On the left side you see only "transfer ok"

What to do, send back ore Fibaro fix this problem....?

 

Twan

Edited November 27, 2016 by twanve

[Guest calvin4000]

Ok, I suppose it was bad luck.... I sent the Button back where I ordered it for an exchange, and the new one works perfectly so far..

 

I even ordered one more to be sure, and it also works without any problem....

 

Before, I had exactly the same problem, 'transfer ok', but no action at all...

Edited December 8, 2016 by calvin4000

[Sankotronic 2,370]

Hi @calvin4000

 

Since you just included new Button to your system, can you please check on Advanced tab to what value is set "Wake up interval"? Was it by default 0 sec?

 

Thank you

 

[Guest calvin4000]

2 minutes ago, Sankotronic said:

Hi @calvin4000

 

Since you just included new Button to your system, can you please check on Advanced tab to what value is set "Wake up interval"? Was it by default 0 sec?

 

Thank you

 

 

FYI: Wake up interval (s): 0 by default

 

On both of them, I just checked right now.....

[Sankotronic 2,370]

14 minutes ago, calvin4000 said:

 

FYI: Wake up interval (s): 0 by default

 

On both of them, I just checked right now.....

Ok thanks, it is good to know, because my was also with that interval set to 0 sec what I think is not good and after some time was not working properly since it needed at least two, three pushes more to activate desired action, but now with this settings is working OK.

[elisiussen 8]

On 23/11/2016 at 6:27 PM, calvin4000 said:

Common, Fibaro, we shlould not have to wakeup The Buttons before using them, it never happens with minimotes or NodON switches/remotes... something is wrong...

 

+1 the FGPB does NOT work reliably. Just writes "transfer OK" in the interface but does not trigger scenes nor LUA (yes, I used the right ID) - it works occasionally. Transfer OK gets submitted every time - no exceptions - just does not trigger scenes. Never seen this behaviour from any other devices.

[LP1 0]

The behavior of 'transfer ok' is the same with me

[Guest calvin4000]

With my first 'Button', I got the same 'transfer ok' message without triggering anything.... Finally, I sent it back to the shop where I bought it, got an exchange, and the new one worked 99.9% so far... once I had to wake it up (4x press) and then it was fine again.....

Edited December 20, 2016 by calvin4000

[Guest calvin4000]

Damn it, one of my button does it again... I always have to wake it up first and then it works.... For a short while.... 

[hTiger1 50]

17 hours ago, calvin4000 said:

Damn it, one of my button does it again... I always have to wake it up first and then it works.... For a short while.... 

Hi
I do not know if this helps.
You must feel the spring force from the beginning of the pressure.
You may try to tighten the spring under the battery: Remove the battery and gently pull the spring to make it a little longer.

[Orgli 15]

Since 12/2016 I have five buttons included:

- two as "pure" panic buttons

- three as scene controllers - each one triggers six different scenes (1-5 press and long press).

 

With the panic buttons there were no problems. Even after changing rooms (mesh caused no problems).

 

In some rare cases (once a month) I think that it is my fault by clicking too slow or too fast (eg. "push - pause - push" ist not interpreted as a double push but as two single pushes which leads to different scenes).

Only in one case I suspected the button felt "asleep" so the first push "woke up" the button and the second push startet 1-push-scene.

[mobbie 10]

Looks like there are a few threads on this but with support it looks like mine are now working, whereas before 2 of my 4 were not working at all (ie get transfer ok but no 1x or 2x etc)

 

Process to fix for me.

 

Upgrade to the latest official update 4.120

Bring the button close to the hc2

Do a soft reconfigure 

Wait 2-5 mins

Move button to intended location

Press button 4 times to wake

Now works 99%. (Compared to 0%) - and i havent had to rewake or do anything to it in 3 days so far.

 

See if that works?

 

Mobbie

[kjt 3]

On 4/4/2017 at 9:36 AM, mobbie said:

Looks like there are a few threads on this but with support it looks like mine are now working, whereas before 2 of my 4 were not working at all (ie get transfer ok but no 1x or 2x etc)

 

Process to fix for me.

 

Upgrade to the latest official update 4.120

Bring the button close to the hc2

Do a soft reconfigure 

Wait 2-5 mins

Move button to intended location

Press button 4 times to wake

Now works 99%. (Compared to 0%) - and i havent had to rewake or do anything to it in 3 days so far.

 

See if that works?

 

Mobbie

 

I paid for this button 100%. I expect it to work 100%.

[mobbie 10]

@kjt completely agree.. anyway day 4 its started to fail again... my minimote works 100% since day one.. silly of me to assume fibaro made good quality equipment.