fibaro motion sensor, false alarm and stay breach

[elmips 4]

Hello all,

a strange behavior from one of my fibaro motion sensor tonight.

Got a false alarm at 3AM (no motion, nobody home, no pet).

i saw that the motion sensor stay breach since this time (6 hours ago !

Please login or register to see this image.

/emoticons/default_icon_eek.gif" alt=":shock:" /> ) and i can not swith it to unbreach.

I had a look at my parameter but didn't see anything that can explain that behavior.

parameter 1 = 100

parameter 2 = 15

parameter 6 = 30s

really don't understand why it has been breached and why it stay breach....

Please login or register to see this image.

/emoticons/default_icon_question.gif" alt=":?:" />

Please login or register to see this attachment.

[murnko 0]

elmips,

Please check if there is no association or scene that triggers that.

Check if parameter 3 is set to 2 impulses.

Also try reconfiguring it to the default and/or re-adding module.

Regards

[elmips 4]

elmips,

Please check if there is no association or scene that triggers that.

Check if parameter 3 is set to 2 impulses.

Also try reconfiguring it to the default and/or re-adding module.

Regards

hi Murnko,

no association has been set.

I got just one scene that turn on a light if motion sensor is breach and variable "night" is set to "1".

yes, parameter 3 is allready set to 2 impulses.

i pushed "reconfigure to default value".

waiting for device to wake up.

[murnko 0]

elmips,

If problem still exists after reconfiguration, You can also try changing parameters 22 - tamper alarm cancellation, 20 - tamper sensitivity. As last resort try also turning tamper off, maybe something is wrong with it.

It would help if You can tell where Your MS is located, maybe there is some source of outside motion etc.

Regards

[m.roszak 763]

By default tamper cancellation report is disabled (parameter 24) - if tamper has been activated somehow it will stay breached until next motion cancellation report.

You can turn on tamper cancellation reports by setting parameter 24 to 1. Then parameter 22 defines time period, in seconds, after which the tamper alarm is cancelled so you can adjust this parameter as well.

[dw89 8]

I had lots of problems with these. Try the following...they seem (mostly) to work although I still get the odd one going breached. Walking by a stuck sensor re-sets it by the way:

Set

24 to 1

40 to 200

42 to 1800

60 to 1

62 to 1800

64 to 0

See if it helps

Dave

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

[ Added: 2014-08-04, 19:27 ]

M. Roszak,

Apart from what I just suggested...is there anything else one can do to stop the false trigger/stuck on breach? i.e. apart from what I said I still get the odd time (at moment) under 3.591 where no one in room and yet it happens and then gets stuck. Any other suggestions?

I assume LUA sees the device state as breached ('1), so could one assume that we could use LUA in a scene to put it back to '0' (safe) after, say, a certain time if no other triggers are shown anywhere else or on same motion unit? I'm trying to think of a good way not to cause alarm issues in house (especially over night). Any suggestions welcome.

KR, David

[elmips 4]

By default tamper cancellation report is disabled (parameter 24) - if tamper has been activated somehow it will stay breached until next motion cancellation report.

You can turn on tamper cancellation reports by setting parameter 24 to 1. Then parameter 22 defines time period, in seconds, after which the tamper alarm is cancelled so you can adjust this parameter as well.

M.roszak, parameter 24 has been set to 1 by default, no changed has been applied.

parameter 22 has been set to 30s, so the breach should be canceled for a while.

I tryed to "reconfigure by default" this device but it stay in a "waiting for wake up" state (for 9 hours ago...

Please login or register to see this image.

/emoticons/default_icon_eek.gif" alt=":shock:" /> ).

it seems that the device is frost and do not answer to anything since I wake it up manually...

Actually I'm in holyday, so i'm not able to be physically at my home to wake up this device...

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

dw89, i agree with you, this is an importante issue because if only one of our sensor make false alarm, the whole alarm system is useless.

i'll try your setup when i would have acces to this sensor again.

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

[m.roszak 763]

elmips, first position in parameter 24 means that this parameter is set to 0.

From manual:

Please login or register to see this code.

So default setting is 0.

Please make sure that you have set parameter 24 to 1 by selecting this option:

Tamper alarm is reported in Sensor Alarm command class /

Cancellation is reported in Sensor Alarm commad class after the

time period set in parameter 22 (Tamper Alarm Cancellation Delay)

[dawiinci 5]

These sensors - or the HC2 - is not capable of getting too much sensor data at once. Therefore if you disable tamper and light intensity you won't encounter any problems.

Fibaro knows that problem and is hopefully fixing it in 4.0 but they don't really communicate that their devices FAIL in the latest version.

[elmips 4]

ok, back to home from holiday.

I try wake up manually the motion sensor who stay breach but it didn't work. (nothing change in the HC2, led of the motion sensor stay blue for env 10 sec, and goes off))

I try to reconfigure parameter 24 to 1 but devices stay at state "waiting for wake up"

I try to reconfigure other devices (all type, not only motion sensor) and i realize they all stay at state "waiting for wake up"

so, it seems to be an issue form the zwave stack of the HC2.

I reboot the HC2 and everything goes well after that.

m.roszak, I change all of my motion sensor's parameter 24 to 1, we'll see if it's better this way when using the Fibaro alarm.

dawiinci, ok, good to know. in wich case this issue appen ? i mean, is it if you too frequently refresh the module data ?

@Fibaro group, it seems to be a serious issue with the Zwave stack in FW 3,591 as the Fibaro alarm is totaly useless when this appen.

[MalvinYNJ 4]

Correct me if I'm wrong.

Last breached was stated 6hrs and 43mins ago.

Which means the last breach timing was 6hrs and 43mins ago where you were sleeping.

When you screenshot the motion sensor, it shows it's breached. Did you/whoever walk over the motion sensor to breach it?

or perhaps you were saying the last breach time does not update anymore?

[elmips 4]

Correct me if I'm wrong.

Last breached was stated 6hrs and 43mins ago.

Which means the last breach timing was 6hrs and 43mins ago where you were sleeping.

When you screenshot the motion sensor, it shows it's breached. Did you/whoever walk over the motion sensor to breach it?

or perhaps you were saying the last breach time does not update anymore?

Last breached was started 6hrs and 43mins ago where I was out for holiday.

I saw the breach because the Fibaro alarme was activated.

When i came home, i try to "walk in front", "wake up manually" or "reconfigure" this motion sensor with no result : stay breached and didn't change. (for 5 days, when I came home, the screenshot was made using remote acces 6h43 after the first breached)

I also try to reconfigure some other device and saw that the whole device of my house aren't able to be reconfigure anymore. (for exemple my horztmann didn't update anymore)

So I reboot my HC2 and everything worked again.

this story tell me that using the Fibaro motion sensor with Fibaro alarme made the whole system useless because it let my house without alarme for 5 days while I was at holiday... not very usefull for a "smart house" to be honest...

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

[dawiinci 5]

dawiinci, ok, good to know. in wich case this issue appen ? i mean, is it if you too frequently refresh the module data ?

@Fibaro group, it seems to be a serious issue with the Zwave stack in FW 3,591 as the Fibaro alarm is totaly useless when this appen.

I have 4 sensors wich updated every 333, 222, 300 and 444 seconds and every few days I had false alarms. Now I only have two sensors (lux) active, disabled tamper and have no issues anymore. But of course this depends on how much traffic is on your network already.

Will be fixed in 4.0...

Please login or register to see this image.

/emoticons/default_icon_rolleyes.gif" alt=":roll:" />

[goran 9]

It's a known issue that has been reported many times. But if it's just stuck in breached mode you can still feel pretty lucky, because many of our motion sensors have been turned into temperature sensors in HC2 (see other bug reports). We have been told to wait for the next stable release. We have been waiting for a long time and we are still waiting. And we probably have to wait a lot more...

[elmips 4]

Again, another false alarm this morning with another motion sensor... (nobody at home, no pet) Parameter 24 has been set to 1 and nothing change...

Fibaro alarm is totally usless with these false breach... More important : with the time, you didn't thrust the alarm came from your system... what happen if it's a real alarm ? ...

@Fibaro, sorry to tell but it's not very serious to keep a critical service like an alarm working with this confidence.

Please login or register to see this image.

/emoticons/default_icon_mad.gif" alt=":-x" />

[j.nowacki 5]

elmips, are sensors placed inside? Are they exposed for high humidity, radical temperature or light changes? You can also try to check if its tamper which causes problems, by changing param. 20 to 0.

[elmips 4]

Hi all,

to give a feedback to @j.nowacki and the community,

false positive breach has stopped when I desactivate tamper function (parameter 20 set to 0).

so thanks @j.nowacki this solve the issue by desactivating the tamper.

I don't know why because I don't live in a earthquake zone. but anyway this make the alarm has new reliable. and thanks for that.

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

[ Added: 2014-09-03, 15:40 ]

one week it run with no false breach.

[ Added: 2014-09-11, 17:22 ]

unfortunatly, again a false positive breached yesterday.

this time it wasn't a FGMS-001 but a FGK-101...

well, it mean the issue seams to be against the whole system (not depending of a small part like one module)

anyway, an old issue has comeback when trying to switch off the alarm :

when an alarm is breached, all the light of my house are switch on.

using the IPAD app, i clicked to the switch OFF button of the whole house.

at this point, all the light switch off correctly but, just after, the zwave network didn't response anymore. I can acces to my HC2 using http, but I still see the lights ON, and i can't switch them OFF again, and at all, nothing work in my Zwave network.

I had to reboot my HC2 to have the zwave back again.

@Fibaro, you have a very serious issue running the Fibaro alarm and we must admit at this time, it is totally unusuable...

PS : i notice my RGB show on after the reboot, i can not switch it off with the interface, neither the ipad or iphone app. I had to physically swith it off with the S1 to make it work again. strange...