Fibaro Button not working

[DebugBug 2]

8 minutes ago, mobbie said:

Support have got back to me and have replicated the problem.  Lets see if a solution appears.

@mobbie Very good. I just returned mine too - impossible to get it to work. I used to be able to get it to work sometimes, but lately (now on 4.112) it would only do the "transfer OK" - couldn't even exclude it before returning it - had to just delete the device.

Let's hope they get it fixed, please keep us posted.

[mobbie 10]

@DebugBug yep of course.  Out of my 4 I now have 2 that dont work at all (always transfer ok) one that works intermittently  (50%) and one that works most if the time.......

[mobbie 10]

Mmm support has gone quiet and now not responding... pretty poor really!

[mobbie 10]

Ok got a response today supposedly the next official (nonbeta) update will fix the problem.

 

Fingers crossed.

[PaddySe 0]

On 24/03/2017 at 2:22 AM, mobbie said:

Ok got a response today supposedly the next official (nonbeta) update will fix the problem.

 

Fingers crossed.

 

I just updated to 4.120, and my red Button still doesn't work. I can add and remove, but pressing the button does absolutely nothing.

[darren-mc 11]

yes I have two brand new ones and both seem to fail. I am going to reach out to tech support in the morning. If nothing then I will simply return them.

[mobbie 10]

Updated as well to 4.12 and still have problems.  Couldn't' even remove/add because it would never pick up 6 presses.

 

Ive informed support.  but getting ready to return.

[darren-mc 11]

ahh I tried to remove/add again just to see if it was an issue...but I had the same problem never picked up the 6 presses!

[Guest calvin4000]

I'm not the only one with this problem, I wonder if I should be reassured or not... 

 

1 out of two is working now... The second after a few press only...

 

I hate this 'transfer ok' for nothing... Last update did not change anything... 

[darren-mc 11]

I have decided that these are going back. Got six of them all the same.

[Guest calvin4000]

Certainly safer that way... 

[mobbie 10]

OK so after more chats to support I seem to have got all mine working again.

 

1. Took button off wall and moved near to the HC2

2. Did a soft reconfigure of the device

3. Waited a bit (I gave it 20mins).

4. Take the device to the location it is supposed to be in

5. Press it 4 times to make it 'wake up'

6. Now seems to work as designed.

 

From Fibaro support, looks like when you remove/add the devices, once it is in its correct location you need to press it 4 times to wake, so it knows where it is now located rather than trying to communicate directly with the HC2.

 

Mobbie.

[samuel 27]

@mobbie 

What is your wake-up setting = "0" or another value from your button ?

[Ole 14]

My button says "transfer ok" in the GUI but it doesn't execute the function, which is to turn on the lights in a room. It has perhaps worked once.

[samuel 27]

@Olesame with me, 

 

I did what @mobbie did, but still, 50% goes ok, 50% i got to press a couple of time before i got a response, or even have to wake up (press 4 times)

Yhe quickest way is to disconnect battery and reconnect again, then it works straight away again. But this is not the normal way to do so.

 

Some more suggestions to solve this would be great! thanks

 

1. Took button off wall and moved near to the HC2

2. Did a soft reconfigure of the device

3. Waited a bit (I gave it 20mins).

4. Take the device to the location it is supposed to be in

5. Press it 4 times to make it 'wake up'

6. Now seems to work as designed.

[Sankotronic 2,370]

Until yesterday I had two Fibaro Buttons and now I have only one.

 

One button stopped working. When pressed there was only message 'Transfer OK' on the device in web GUI, but no reaction at all to trigger scenes. It didn't matter at all how many times I pressed it, it was always just giving that 'Transfer OK' message.

 

I try to exclude it regular way, but even I get notification that device is successfully excluded it was still there, just changed color of the button from black to red! So at the end I used force to exclude it. Then I reset it according to user guide several times, but it refused to be included back into the system even I try to include it several times. So now I have piece of unusable plastic with z-wave chip inside.

 

No more Fibaro buttons for me! Actually how things are developing lately no more Fibaro at all!

[alexndr 1]

Just to add another complaint to the pile.

 

I have a piece of unusable plastic as well.

My first button worked ok for a week or two, slowly getting worse and ended up in picking up on of three presses. I returned it, got a new one, which made a similar journey. 

Right now it's in the state described above. "Transfer ok" and then nothing.

Must be the worst Fibaro- product ever and I amazed it's still on the market.

Contant with support ended up in the dead end: "return to Poland".

 

Edited June 11, 2017 by alexndr

[petergebruers 1,268]

8 hours ago, Sankotronic said:

Until yesterday I had two Fibaro Buttons and now I have only one.

 

One button stopped working. When pressed there was only message 'Transfer OK' on the device in web GUI, but no reaction at all to trigger scenes. It didn't matter at all how many times I pressed it, it was always just giving that 'Transfer OK' message. (...)

 

No more Fibaro buttons for me! Actually how things are developing lately no more Fibaro at all!

 

I'm running 4.131 and 'm trying to include a old Z-Wave.me (duwi) wall switch. It has a template now, but it has no property "scene activation", hence doesn't work. Maybe that's what happened to your button (see htttp://yourip/api/devices/id if you find "sceneactivation" on master or slave id). My button is still ok, but I didn't (soft) reconfigure). Also, my more modern Z-Wave.me wall controller doesn't include properly. It says: "unconfigured" and if you reconfigure, Z-Wave hangs until you reboot. I've got a support ticket for that one.

[Sankotronic 2,370]

Hi @petergebruers,

 

Too late to check anything since it is excluded from system and can't be included back anymore. But why can't be included back? I reset it many times according to Fibaro provided user guide but nothing. It worked after inclusion several months back. It was rarely used but it was working but then suddenly stopped and the rest of the story is told.

 

 

[petergebruers 1,268]

10 minutes ago, Sankotronic said:

Too late to check anything since it is excluded from system and can't be included back anymore. But why can't be included back? (...)

That, my friend, is the crux of the story

 

There's one thing that might explain this kind of behaviour, especially with the ER14250 powered devices.

 

The battery can be good enough to report button presses (because it transmits a very small amount of data in a short time). But the battery can be too week to sustain the inclusion procedure (because it scans the network and exchanges a lot of data).

 

It's not limited to Fibaro devices, I've had it with an Aeon recessed door sensor. LED blink seemed OK. open/close OK. But as soon as I changed a parameter I saw the LED drop in intensity. This battery wasn't really dead, but it wasn't up to spec either. Note: beware of no-brand ER14250 batteries, I give you a 25% change of finding a good one.