Fibaro Motion Sensor paramter 3 and 4 - question

[U5tabil 2]

I just have a question around paramtert 3 and 4 on the sensor.

 

I want the sensor to be more responsive. And i find the information a bit odd.

 

Paramter 3:

Says the lower the less sensetive. But isnt it oposite? the less moves required makes it more sensetive? so 0 should make it really sensetive? but will that make it so sensetive that it might sense to much giving false motion?

 

3. PIR sensor’s “PULSE COUNTER”

Sets the number of moves required for the PIR sensor to report

motion. The lower the value, the less sensitive the PIR sensor. It’s

not recommended to modify this parameter settings.

Available settings: 0 - 3

Formula to calculate the number of pulses: pulses = (value + 1)

Default setting: 1 (2 pulses)

Parameter size: 1 [byte]

 

 

Paramtert 4:

So default here is 2, which results in 12 seconds. thats a long time. i dont see how it can become more sensetive by adding more time here? even 1 here (6 sec) should be enought time for a sensor to detect moves. 

 

4. PIR sensor’s “WINDOW TIME”

Period of time during which the number of moves set in parameter 3

must be detected in order for the PIR sensor to report motion. The

higher the value, the more sensitive the PIR sensor. It’s not

recommended to modify this parameter setting.

Available settings: 0 - 3

Formula to calculate the time: time = 4 x (value + 1)

Default setting: 2 (12 seconds)

Parameter size: 1 [byte]

 

 

 

[j.nowacki 5]

Parameter 3 description has an error in English version, of course it becomes less sensitive when you increase this parameter. It was already corrected in future version for the print.

Parameter 4 is strictly connected with no 3, if there are many pulses needed to breach sensor, longer time may be needed. Maybe calling the effect 'increase' in matter of sensitivity is not strict, but it helps detect more movement indeed.

[U5tabil 2]

Parameter 3 description has an error in English version, of course it becomes less sensitive when you increase this parameter. It was already corrected in future version for the print.

Parameter 4 is strictly connected with no 3, if there are many pulses needed to breach sensor, longer time may be needed. Maybe calling the effect 'increase' in matter of sensitivity is not strict, but it helps detect more movement indeed.

 

Thanks. But will say 0 in parameter 3 make it to sensetive, giving me possible false motion?

 

Any other recommendations to get the sensor to become a bit faster? i feel it taske a good second or two before moton is sensed in system.

 

would it maybe be possible to edit paramtert 1 bellow 8? or would this just crash the sensor?

[j.nowacki 5]

It is not possible to set it below 8. Lower values of parameter 3 may cause false breaches indeed. To make it react faster you should also consider adjusting placement of the Motion Sensor to detect movement as soon as possible.

[Stephan Smit 3]

These parameters are not available on my Fibaro Motion Sensor in HCL v 3.594? See screenshot

Please login or register to see this attachment.

[wienog 107]

These parameters are not available on my Fibaro Motion Sensor in HCL v 3.594? See screenshot

SCS,

 

If you don't see these parameters then that means the device has not been properly included and Fibaro HC2 has not got all the information about the device. try to remove the device and add it again and enable: use template for settings"