Fibaro Motion sensor gets breached and remains breached

[Acho 2]

Hi,

    recently I bought 2 fibaro motion sensors and once per couple of days ( mostly if they are not breached for those days ) they get breached themselfs and remain breached until I "breach" them by walking arround - is this a known bug ( Im on HC2 3.6 ) ? Any solution ?

 

Thanks

[j.nowacki 5]

Turn off tamper (parameter 20 to 0) to make sure it was not caused by tamper alarm - since they are not cancelled by default motion seems to be stuck on breached.

[Acho 2]

Tried as adviced and no change, again false alarm in the middle of the night without being breached and remained breached untill I walked by... Any advise pls ?

[j.nowacki 5]

Have you woken up the devices manually after saving this parameter?

[Acho 2]

Sure I did it first close to HC2, later also on the final location where the signal is hopped via Fibaro 2x1,5kW switch

[j.nowacki 5]

If it is located in place without drafts, rapid temperature changes etc, and this behavior continues, please decrease sensitivity a little. Also set parameter 24 to 1.

[Acho 2]

Parameter 21 is set to 1, I dont want do decrease sensitivity - should not be the case - If it would be about sensitivity, it would not remain breached untill someone walks really by... Im considering returning both sensors back and go for Aeon I have mostly allready - they work 100%... ( of course on v3.6 )

[j.nowacki 5]

You can always return module for warranty if you suspect inappropriate operation.

[Acho 2]

allready agreed with the dealer, still wondering how come 2 of 2 Fibaro motion sensors having the same issue - if not breached by walking arround for a 1,5 days app, they get reached themselves and remaine breached  so looks like an general issue not only single sensor...

[Guest matie]

Getting the motion sensors configured is not very easy and straight forward. Don't know why, but with all my 3 motion sensor I ran into problems, which took me hours. At first the web interface is not being updated and logs are not showing parameter configuration. this took me half an hour to find out... This makes it hard to see if any of your changes have been pushed. Even when wake up interval set to 10 seconds, this is still the case. And when you change something you need to change all settings again... if not, you will push old /default settings for all parameters not changed.

 

Anyway. Don't change the hidden device settings. Your motion sensor will start showing strange behaviour. My last one (just installed during last few hours) reported motion every 24 - 40 seconds, but no one was even in sight. I've resetted it (only possible by putting it next to the HC2... although the distance is no more than around 12 meters with 1 wall) and now it is working, but the temp and lux not. They are waiting for the thing to awake. It awakes every 15 seconds, (checked by reading the awake variable from the sensor), but still it is waiting. 

 

I think it would be a good idea for the Fibaro team to test, retest, etc. the motion sensor module in HC2. It is quite frustrating and feels buggy. 

 

Cheers,

Mathijs.

[wienog 107]

Getting the motion sensors configured is not very easy and straight forward. Don't know why, but with all my 3 motion sensor I ran into problems, which took me hours. At first the web interface is not being updated and logs are not showing parameter configuration. this took me half an hour to find out... This makes it hard to see if any of your changes have been pushed. Even when wake up interval set to 10 seconds, this is still the case. And when you change something you need to change all settings again... if not, you will push old /default settings for all parameters not changed.

 

Anyway. Don't change the hidden device settings. Your motion sensor will start showing strange behaviour. My last one (just installed during last few hours) reported motion every 24 - 40 seconds, but no one was even in sight. I've resetted it (only possible by putting it next to the HC2... although the distance is no more than around 12 meters with 1 wall) and now it is working, but the temp and lux not. They are waiting for the thing to awake. It awakes every 15 seconds, (checked by reading the awake variable from the sensor), but still it is waiting. 

 

I think it would be a good idea for the Fibaro team to test, retest, etc. the motion sensor module in HC2. It is quite frustrating and feels buggy. 

 

Cheers,

Mathijs.

As I said in earlier posts, I'm often surprised when I read this kind of posts.

I have now 12 Fibaro Motion sensors and they are included in some 192 scenes amidst 112 other (physical) devices attached to the HC2 running 4.056 and I have never had any problems with heme, not with their functioning right out of the box, not with changing parameters on them, not even with positioning them outside where they get rained under several times a month.

Again this makes me think that it must be that there are different hardware configurations of the HC2 that work/react differently to the FGMS and other devices.

(On the other hand the Aeon motion sensors never really worked for me...)

[fi-bar-oh 47]

Range or traffic issues 99% of the time!

[fi-bar-oh 47]

Did have one module that triggered itself got it replaced 6 months ago...