This object is in archive!
Fibaro Motion sensor detects motion wrong during night time
Need Answer
Hello,
I am using 3 Fibaro motion sensors to switch lights. Since a couple weeks, the lights are turning automatically on during night time. I have no pets or kids to trigger a motion sensor. I went to the event log and found out, that all 3 sensors got motion events. What is wrong in this case? See attached config and events. Could this be related to temperature/luminance?
Thanks
Files:
Motion Detectio...
The same question 
No connection
Real-time notifications may not work
I have something very similar. I experienced this with 3 Fibaro motion sensors (out of 4), one of which I sent back.
In my case, the "ghost" motion signals seem connected with the wake-up intervals of the sensors. A few seconds after they have woken up and reported "no motion" they report "motion". Fibaro support was most unhelpful. In one instance, it seemed tonhave helped to set the sensitivity from the defaul 8 to 10. I will try the same with the other one that is acting up currently (just have to get the ladder for that ...) and see if that works as well.
I have something very similar. I experienced this with 3 Fibaro motion sensors (out of 4), one of which I sent back.
In my case, the "ghost" motion signals seem connected with the wake-up intervals of the sensors. A few seconds after they have woken up and reported "no motion" they report "motion". Fibaro support was most unhelpful. In one instance, it seemed tonhave helped to set the sensitivity from the defaul 8 to 10. I will try the same with the other one that is acting up currently (just have to get the ladder for that ...) and see if that works as well.
I have had the same problem with one of mine fibaro motion sensors
By changing the sensitivity the problem seems to go away.
Sometimes it get stuck on "motion", but is reverted to "no motion" when waked up.
This is what Fibaro wrote back to me after contactin support (but i still think it's the sensitivity):
I believe the problem is not directly connected with the sensitivity of the sensor, but lack of so called “blind time”.
Please set parameter 2 to value 15 (8 seconds of blind time) and 6 to value of 15 seconds.
This would extend the battery life and also reduce number of useless z-wave traffic as the sensor may keep on reporting on the time in case of a lot movement in a room.
This setting also is a good option in case Motion is to report movement and then turn ON/OFF some associated device (for example light).
I have had the same problem with one of mine fibaro motion sensors
By changing the sensitivity the problem seems to go away.
Sometimes it get stuck on "motion", but is reverted to "no motion" when waked up.
This is what Fibaro wrote back to me after contactin support (but i still think it's the sensitivity):
I believe the problem is not directly connected with the sensitivity of the sensor, but lack of so called “blind time”.
Please set parameter 2 to value 15 (8 seconds of blind time) and 6 to value of 15 seconds.
This would extend the battery life and also reduce number of useless z-wave traffic as the sensor may keep on reporting on the time in case of a lot movement in a room.
This setting also is a good option in case Motion is to report movement and then turn ON/OFF some associated device (for example light).
Hi there,
will be fixed soon. Please open a ticket for that problem.
regards Helle
Hi there,
will be fixed soon. Please open a ticket for that problem.
regards Helle
Well I've had it for more than a year. It's been mounted in the same place. All of a sudden it starts acting up!?
Ok....device broken.... Crap HW supplier.... Well i'll deal with the with it when I have time.
Then this thread comes along..... Conclusion changes to: it's software related. But of course, it could still be broken, who knows..
Well I've had it for more than a year. It's been mounted in the same place. All of a sudden it starts acting up!?
Ok....device broken.... Crap HW supplier.... Well i'll deal with the with it when I have time.
Then this thread comes along..... Conclusion changes to: it's software related. But of course, it could still be broken, who knows..
few off my fibaro sensors have started to act up aswell. (never have hade problems with them before and have not changed anything)
problem 1: i can see the reaction of moment from the detector, but status is not updated in zipabox
problem 2: zipato seams to miss the no moment message, so the device looks like its stuck in moment untill new moment is detected and next no moment is sent
few off my fibaro sensors have started to act up aswell. (never have hade problems with them before and have not changed anything)
problem 1: i can see the reaction of moment from the detector, but status is not updated in zipabox
problem 2: zipato seams to miss the no moment message, so the device looks like its stuck in moment untill new moment is detected and next no moment is sent
I got an answer from support. They said I have to remove/add the sensor. It seems that the sensor is using old descriptor and there is new descriptor available. I have to try and let you know if it works. I also told them, that it is a no go to remove/add sensors all the time when they changed something.
Not sure if this is related to this issue, but since yesterday my z-wave dimmer is dead.
I got an answer from support. They said I have to remove/add the sensor. It seems that the sensor is using old descriptor and there is new descriptor available. I have to try and let you know if it works. I also told them, that it is a no go to remove/add sensors all the time when they changed something.
Not sure if this is related to this issue, but since yesterday my z-wave dimmer is dead.
Did your problem went away by excluding/including your devices, I recently started to have issues since last firmware update (1.2.15) and I notice this two sensors are different regarding descriptors than the others, in these parameter #24 is not shown as default.
Did your problem went away by excluding/including your devices, I recently started to have issues since last firmware update (1.2.15) and I notice this two sensors are different regarding descriptors than the others, in these parameter #24 is not shown as default.
I'm about the same problem. After updating to 1.2.21h Fibaro motion sensor reacts badly. Remains for several hours as motion. I have 10 sensors, and every day it makes another sensor. What should I do to correct?
I'm about the same problem. After updating to 1.2.21h Fibaro motion sensor reacts badly. Remains for several hours as motion. I have 10 sensors, and every day it makes another sensor. What should I do to correct?
Well, firstly upgrade to latest version. Mine is right now 1.2.22i. Also try doing a Network heal on these devices using the ZWNTUT topology update located in the Zwave network settings in Device manager.
You can also try to go to the root level setting of the problematic device and use the following 2 functions:
General settings - reapply device descriptors
Advanced - configure node
Well, firstly upgrade to latest version. Mine is right now 1.2.22i. Also try doing a Network heal on these devices using the ZWNTUT topology update located in the Zwave network settings in Device manager.
You can also try to go to the root level setting of the problematic device and use the following 2 functions:
General settings - reapply device descriptors
Advanced - configure node
I have contacted support and adviced me to upgrade to the latest firmware and exclude/include the sensor once in the latest firmware. I did it for one of them and I noticed it did improve its performance, at least my alarm is not tripping every time I arm it AWAY. Try do the same and let us know if it worked.
I have contacted support and adviced me to upgrade to the latest firmware and exclude/include the sensor once in the latest firmware. I did it for one of them and I noticed it did improve its performance, at least my alarm is not tripping every time I arm it AWAY. Try do the same and let us know if it worked.
Replies have been locked on this page!