Fibaro Motion detector: alarm cancellation delay

[Ericv]

Hi,

I have a Fibaro FGMS-001 motion sensor in my network. Works fine.

What I try to understand is the time that elapses between the moment of triggering the motion alarm and the moment the alarm is cancelled.

in the present situation this time frame is about 5 minutes. Whereas I would expect it to be about 30 seconds (in case there is no movement in the sensor area). The 'Motion detection - alarm cancellation delay' setting is 30. Which corresponds to 30 seconds, says the manual.

Any thoughts? Suggestions are welcome.

Eric

[emme]

before continuing let me explain that there are 2 keys parameters:
Motion cancellation delay and Motion window (usually 12 secs)
the secon parameters determinates the min secs between one motion and another within considering it as the sme movement and do not send a second alarm frame.
it works like this:
1st trigger start, send Alarm framce, start counting 12secs
if a movement is detected within 12 there will be no Alarm, but countdown resets.
after 12 secs if a movement is detected a new alarm frame will be send... start counting
If no movement detected within12 secs then it starts the reset counter, after 5 mins the ALARM end frame is sent.

5 mins is a big window... 30secs are enough...

Please also note that changes are reflected to the device NOT immediately but in the wake-up timer (last parameter) or if you push 3 times the button after issuing the changes in the OZWCP.

ciao
M

[Ericv]

Thanks for the feedback and explanation.

This is exactly my confusion: the cancellation setting is 30 (corresponds to seconds, says the manual), but the actual time an alarm is active is 5 minutes.

So: how to reduce this 5 minute period?

[emme]

if you do not have any action related to the alarm frame... that value is pretty useless and if so, it's a matter about balancing the battery life: the more communication you have, faster the battery will drain.

My example.. I use 30secs delay on the alarm cancellation delay, I do use to intercept the event in my scripts in case the security panel is armed... I do need that value...
my batteries last about 6 months...
moving to 5 mins probably they will last 7 or 8 month.

Other issue: remember to DISABLE the reaction on alarm frames to ANY OTHER DEVICES.... last time I didn't for a simple passage I had a house shutdown by default with lights and shutters going on and off like a mad house

[Ericv]

I still do not understand this.
My sensor cancellation delay setting is 30 seconds, but the alarm stays active for 5 minutes.

[emme]

what about the wakup window?

[Ericv]

12 seconds.

Sensor has all settings as per default settings.

[Ericv]

The only other thing I can think of: I have used a Blockly script to switch on a light on a movement alarm, with a timer to leave the light on for 5 minutes. The script is not active currently, however.
But I would not expect to see any relation between a script and the behavior of the motion sensor

[emme]

mmh... the main thing is to ensure WHEN the device ALARM TYPE change state... that is the information we need.
device PIR will move to close state after 12secs window

[Ericv]

What I see in the Domoticz log is that "Burglar" becomes active ('on'), of course when movement is detected. And then after 5 minutes "burglar" again changes state, to 'off'.

[emme]

burglar is the tamper signal, not the movement one.

[Ericv]

The movement signal reacts identical to 'Burglar'. Also 5 minutes active

[Ericv]

Finally i decided to remove the sensor from the network. Reconnect, and now the sensor works as it is supposed to work.

Don't know why; it is the result that counts