Alarm going off without sensor being breached

[FritzB001 0]

Guys... I am really annoyed. As reported many times before (pls. see my posting and bug reports) alarm goes off without sensors being breached. This time it was the fibaro motion sensor. Last time it was the flood sensor and before that the door/window sensor and so on.

Neighbours ask me what they shall do if they hear alarm ring. Actually they mean: stop that f*** sh*** disturbing our night (AND MINE TOO). So I tell them: "oh ah... I am so sorry but I have this cool home automation system THAT IS NOT WORKING AT ALL!".

When will you solve this problem?

[goran 9]

Many users, including myself, are just as angry as you are. We have been told to wait for the next stable release to get the new z-wave engine which supposedly fix these kind of issues (I tried the latest beta but it was too broken to even tell if it was fixed or not).

Seeing how people react to the beta versions it seems like we are not going to see a stable version any time soon.

But hey, Fibaro told us on Facebook about the brand new z-wave engine:

Please login or register to see this link.

That's just as good as... well, actually showing us a new z-wave engine, right?

I feel like I gave someone all my money just to have them rub salt in my wounds.

If I don't see a stable (and I mean STABLE, not just a new major version number), I am going to give up on this system for good because this is completely unacceptable.

Since Fibaro doesn't think these issues are important enough to release a fix, I don't see why things would change much even if we do get a new version. What makes us think that future bugs would be handled differently? I would like to see Fibaro present a strategy and plan about how it's going to handle serious bugs in the future. This should include putting new features on hold while making it the highest priority to fix the bug, and JUST fix the bug, not implement new features at the same time. Otherwise we are going to have the exact same situation when the next serious bug is discovered. "Yeah we know, but you have to wait a few years for version 5.x."

[Dino 0]

Have the same problem. Twoo weeks ago my sirene went on at 11pm and again in the middle of the night. Everybody awake an scrared their was a burglar. Then my flood sensor showed a leakage but their wasn't any. Than my HC2 showed a fire but het their wasn't any. Today my neighbours asked what the blue light strip was.

I am like what do you mean. Oh my ledstrip at the front of the house was on. Not any clue why it was on.

Now and than the doorbell rings (I have it connected) to a Fibaro switch. My wife or kids go the door and nobody is their. Mmmm

My family, my friends, my neighbours they just laugh

Please login or register to see this image.

/emoticons/default_icon_redface.gif" alt=":oops:" /> And I have started doing it as well. And yes I did a reconfigure of the specific devices, did a network refresh and yes support looked at it. By the way no dead nodes since two weeks. I dont have a clue why.

I can return my device but I am just tso tired to move to new system and start all over again.

But I agree the behavior of Fibaro is not changing. believe that somebody mentioned their were 5 bugs closed in five weeks. And indeed why not fix this problem instead of getting a new intercom out. As said it is culture and it is not changing.

And no it is not beta it is version 3.59.....a stable version. But het its my own problem according to Fibaro i did the configuration....I should have hired a professional.

[FritzB001 0]

I am speechless (and a bit happy that I am not alone with my problem... sorry guys

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />-

FIBARO NEEDS TO GIVE A STATEMENT HERE though its a MAJOR PROBLEM!

[elmips 4]

same issue here, reported many times and many times...

and no answer / no delay / from Fibaro...

Fibaro alarm is soo buggy that it's totally useless actually.

I am personally less and less confident from software side of Fibaro product.

I'm really thinking to give up.

too much promises, too much delay and soo many disturbing results. :s

[deanrparry 19]

Use stable 3.590 and your life will be perfect!

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" /> that will be the answer!

[Starbug 0]

Anyone know if you have had your HC2 less than 12 months if its possible to still return it and get a refund from a well known UK supplier based on all these Software issues? wonder if there is a sale of goods act which covers this or if the process is going to be a massive pain!

[fergalmccarthy 5]

Anyone know if you have had your HC2 less than 12 months if its possible to still return it and get a refund from a well known UK supplier based on all these Software issues? wonder if there is a sale of goods act which covers this or if the process is going to be a massive pain!

Starbug, i have just tried this. Initially was told no because I bought it through a 3rd party. So went back to them, and they went through there distributor and was told no, because Fibaro do not believe that there is anything wrong with the firmware.

Quote from my vendor on response from Fibaro

"The issue is that your unit does not have a hardware or firmware fault – replacing the unit wont resolve your issue. Fibaro are not accepting that the firmware is ‘broken’."

[Starbug 0]

Quote from my vendor on response from Fibaro

"The issue is that your unit does not have a hardware or firmware fault – replacing the unit wont resolve your issue. Fibaro are not accepting that the firmware is ‘broken’."

Thanks for the info

I thought as much, very hard to prove things without going down the legal route and you would spend a lot more then you would recoup.

[FritzB001 0]

As usual WE are writing, thinking and so on an no official statement from Fibaro. Its a shame.

[goran 9]

Use stable 3.590 and your life will be perfect!

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" /> that will be the answer!

I AM on 3.590 and life is miserable. And life was miserable with every single other version I have ever tested. Well, maybe even a bit more miserable with the 4.x betas because it was so full of brand new bugs that I couldn't even tell if the old bugs where still there or not.

[deanrparry 19]

I was being sarcastic

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

[akatar 208]

/sarcasm mode on

there are rumours that you need a degree in electronics and another one in automatics to know how it works

eeh to know where you should place the devices

/sarcasm mode off

[j.nowacki 5]

Dear Users, we understand your irritation. False alarms can drastically lessen experience of using any smart home installation. However it is just impossible to address all your concerns at once, since every installation is different. In our installations (and it is quite a number by now) we encountered such problem sporadically and it always occurred to be result of accidental moving the device (Flood Sensor) or undesirable tamper activation (e.g. Motion Sensor). We do not want to belittle your issues, but the only way we can investigate them is checking your systems one by one. So please contact [email protected] so we can help you with this issue.

[fergalmccarthy 5]

/sarcasm mode on

there are rumours that you need a degree in electronics and another one in automatics to know how it works

eeh to know where you should place the devices

/sarcasm mode off

Classic, love it.

[goran 9]

It must be a ghost walking around at night in my house in locked rooms and trigger the tamper alarms on flood sensors and smoke sensors. Even though I've disabled the tamper alarms on all my devices. Perhaps it's the same ghost that's walking around and turning my motion sensors into temperature sensors? The same ghost is also putting up a magic shield that randomly makes HC2 mark devices as dead, even those that are placed 2 meters from the HC2. He is also configuring my devices with random parameter values when including them, for example disabling audio alarm on the smoke sensors, etc. Having read these forums and the constant flood of users reporting the same kind of issues, I conclude that the ghost is visiting them as well. Good to know that it's not because of a bug in the software at least.

[j.nowacki 5]

goran, if you have dead nodes 2m away it probably means that z-wave network is busy all the time, which can lead to unpredictable behavior of all devices. Please contact support, they will take a look at it.

[JanJoh 1]

Perhaps it's the same ghost that's walking around and turning my motion sensors into temperature sensors?

That is one of the things that 4.x software actually seem to have fixed completely.

[Dino 0]

goran, if you have dead nodes 2m away it probably means that z-wave network is busy all the time, which can lead to unpredictable behavior of all devices. Please contact support, they will take a look at it.

Good to see that Fibaro now finally admits that HC2 can lead to "unpredictable behavior of devices". I can think of refunds but lets not do that. Lets start working on fixing it now Fibaro finally seems to get the point.

Now how are we going to solve it!!

Weel at first I am looking for a fix which will do the following:

1. give me functionality which will never ever can trigger a device to go on whateverit is caused by, as not being ment to by the user (local, scene activation).

2. give me functionality which gives a very clear notion that my z-wave network is to busy whathever it has been caused by

3. give me functionality which can point out which device code or whatever has cause the network overlaad

This Fibaro gehost gas been talked about for a while

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

Please login or register to see this link.

[JanJoh 1]

goran, if you have dead nodes 2m away it probably means that z-wave network is busy all the time, which can lead to unpredictable behavior of all devices. Please contact support, they will take a look at it.

Good to see that Fibaro now finally admits that HC2 can lead to "unpredictable behavior of devices". I can think of refunds but lets not do that. Lets start working on fixing it now Fibaro finally seems to get the point.

Now how are we going to solve it!!

Weel at first I am looking for a fix which will do the following:

1. give me functionality which will never ever can trigger a device to go on whateverit is caused by, as not being ment to by the user (local, scene activation).

2. give me functionality which gives a very clear notion that my z-wave network is to busy whathever it has been caused by

3. give me functionality which can point out which device code or whatever has cause the network overlaad

This Fibaro gehost gas been talked about for a while

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

Please login or register to see this link.

In all fairness , there is a yet-to-be-enabled Zwave-tab under diagnostics. I am curiously awaiting.

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[Dino 0]

In all fairness , there is a yet-to-be-enabled Zwave-tab under diagnostics. I am curiously awaiting.

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

Mmm I am sorry I only use stable software. Cant't find it in 3.59.