Fibaro motion Sensors issue: keeps detecting motion

Hi All,
I hope someone can help me. I have several Fibaro motion detectors (3 in 1) and most of the time they all work great. But I have some issues:

  1. Battery status stays at 100% (when the battery is empty I receive the “can’t detect device” message.
  2. Sometimes my motion detectors keeps “detecting motion” while there is no motion at all. In my Vera the ‘Red Motion icon’ is visible but it doesn’t turn off (after 30 secs as normal).
    To fix this I only have to trigger the motion detector (walk in front of it) and than 30 sec’s later the red icon disappeared and the motion detector is working fine again.
    I experience this issue for all my motion detectors, sometimes it happens two days in a row and sometimes it works perfect for two weeks. It can happen for one sensor but also for 3 at once.
    I hope someone know how I can fix this (especially the second issue) as you can imagine, with this issue, I can’t use my system as a burglary alarm because I don’t want to check every night if all sensors are working properly (or walk around the house so that they are working)
    Personally I think it’s a Vera bug but I am not sure. I hope someone can help me with this or can confirm this bug.

Jeroen

Hey JJ,

I don’t think the battery is empty. My Fibaro sensors last about a year on a charge. Can’t detect message is most likely due to the range, interference or imperfect mesh. Which can be improved with careful repositioning of some critical hardwired devices or adding some more repeater nodes.

Same thing on the fact that sensor show’s as tripped, even when it isn’t. Most likely, due to communication reliability, the sensor sends to Vera the first signal that it’s tripped, and the un-tripping command is lost on the way.

Let’s see what other people have experienced with these. Nonetheless, I advise logging a ticket with our Customer Care team, so they can have a look a this as well, if you continue to have these issues.

I too see the behavior you described.
In the past this happend once in a while, but as of FW25 this is happening quite frequently, now also on many of my Fibaro Door sensors and binary sensors.
I remember reading about this lately from someone else, but can’t seem to find the thread.
Btw, you don’t have to walk by to untrip the sensor, you can also set the variable “triggered” to 0

[quote=“Sorin M., post:2, topic:198454”]Hey JJ,

I don’t think the battery is empty. My Fibaro sensors last about a year on a charge. Can’t detect message is most likely due to the range, interference or imperfect mesh. Which can be improved with careful repositioning of some critical hardwired devices or adding some more repeater nodes.[/quote]

Hi Sorin,
I am sure the battery is empty when I receive the message. I know this because the Motion LED isn’t working any more when I walk in front of it. And after changing the battery the device is working again (also for almost a year).

Same thing on the fact that sensor show's as tripped, even when it isn't. Most likely, due to communication reliability, the sensor sends to Vera the first signal that it's tripped, and the un-tripping command is lost on the way.

Communication reliability could theoretically be the case but I don’t think so. One of the motion sensor’s is just 3 meters from my Vera plus. Further I have several dimmers placed more than 50 meters from the controller and they work perfect

Let's see what other people have experienced with these. Nonetheless, I advise logging a ticket with our Customer Care team, so they can have a look a this as well, if you continue to have these issues.

I will log a ticket, thanks for your response

[quote=“pls90, post:3, topic:198454”]I too see the behavior you described.
In the past this happend once in a while, but as of FW25 this is happening quite frequently, now also on many of my Fibaro Door sensors and binary sensors.
I remember reading about this lately from someone else, but can’t seem to find the thread.
Btw, you don’t have to walk by to untrip the sensor, you can also set the variable “triggered” to 0[/quote]

Hi pls90,
Thanks for your response and your tip about changing the variable, I will try this and see if I can run a code or scene to reset all the variable “triggered” to 0 before I go to bed???
If you find the thread again, please let me know. I will follow the advice of Sorin to log a ticket, maybe you can log a ticket as well so!

Thx again

I have bought 10 such units and am very disappointed - I have all those reported issues which to my believe represent a very poor connectivity to Vera.
It is a known issue that Fibaro is not cooperating with any other controller (my mistake to buy those units) and probably Vera didn’t do a good enough job in trying to have it compatible with its controllers. Until there is a major improvement those can not establish a reliable security system. Very dissatisfying.

The mentioned thread is here:
http://forum.micasaverde.com/index.php/topic,51884.0.html

I’m still having the same issues too.

Same issues, and no, it’s not because Vera it restarting while sensor is tripped.