Fibaro Motion Sensor reliable by now?

[goran 9]

But, the most annoying thing is the random errors in temperature reading; you may find that suddenly the temperature reported by one of the sensors jumps from +21C to -1256C or +798C. In the last case Fibaro will trigger an alert of a possible fire. And that in turn makes these devices useless for use as a fire detection mechanism...

I suspect that this issue has more to do with bugs in HC2 rather than in the Fibaro motion sensor because I sometimes get such false readings from the Fibaro flood sensor and other devices as well as the motion sensors. If I was a programmer and I was about to handle a temperature reading that was -1256C or +798C, or humidity that is -583%, this would be a little hint that maybe, just maybe something was wrong and the error should be handled and logged. HC2 does not seem to think that such readings are anything unusual though. Since Fibaro denies that there is any problem in hardware or software, I guess we will never know for sure.

[1152 33]

...Since Fibaro denies that there is any problem in hardware or software, I guess we will never know for sure.

A good indication would be if someone could reporte their experiences witk the fibaro motion sensors with a different controller/gateway.

[alex88 71]

But, the most annoying thing is the random errors in temperature reading; you may find that suddenly the temperature reported by one of the sensors jumps from +21C to -1256C or +798C. In the last case Fibaro will trigger an alert of a possible fire. And that in turn makes these devices useless for use as a fire detection mechanism...

I suspect that this issue has more to do with bugs in HC2 rather than in the Fibaro motion sensor because I sometimes get such false readings from the Fibaro flood sensor and other devices as well as the motion sensors. If I was a programmer and I was about to handle a temperature reading that was -1256C or +798C, or humidity that is -583%, this would be a little hint that maybe, just maybe something was wrong and the error should be handled and logged. HC2 does not seem to think that such readings are anything unusual though. Since Fibaro denies that there is any problem in hardware or software, I guess we will never know for sure.

I raised this bug, which kind of covers your issue. Hopefully if/when this bug is resolved they will cover all the bases:

Please login or register to see this link.

[baran 1]

i have 3 of them. Really a pain!

they stop working, false trigger, change to temp sensor, burnout battery..

Totaly useless.

Support and bug reporting didn't help.

I just remove and read a sensor 12h ago... and now is not reporting anymore...

every time they sey "remove and reinsert", "should be work in v4"..

they also say that is a problem of network.. but i have Fibaro Relay at 2 meters in lineOfSight with it....

[djesko 1]

i have 3 of them. Really a pain!

they stop working, false trigger, change to temp sensor, burnout battery..

Totaly useless.

Support and bug reporting didn't help.

I just remove and read a sensor 12h ago... and now is not reporting anymore...

every time they sey "remove and reinsert", "should be work in v4"..

they also say that is a problem of network.. but i have Fibaro Relay at 2 meters in lineOfSight with it....

I did turn off the "shake/earthquake" sensor and after that my sensor has been working , 4 month now and no problem.

Running latest 3.xxxx

Br Niklas

[baran 1]

I did turn off the "shake/earthquake" sensor and after that my sensor has been working , 4 month now and no problem.

Running latest 3.xxxx

Br Niklas

how?

[j.nowacki 5]

baran, parameter no. 20 to 0