This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Fibaro Motion Sensor movement (sometimes) not processed by Homey
I have created a flow which switches on the lights when the Fibaro Motion Sensor sees movement and it's dark. It also starts a countdown timer of 15 minutes, which is reset every time there is movement. This is used to turn off the lights after 15 minutes of no movement. Homey then first says it believes the room is empty and, after 10 seconds of no movement, switches off the lights.
These flows work perfectly! Most of the time...
Last saturday, Homey suddenly said it believed the room was empty. Although we were with 5 people in the room, I thought it just missed us because we were too far away. So I waved and saw the motion sensor light up, indicating it noticed my movement. Unfortunately, after 10 seconds it just switched off the lights and we were all sitting in the dark. This happend again after I switched on the lights using the app.
I have had this one time before and exactly the same way. After a reboot of Homey, everything seems to be working fine again.
It looks like for some reason, either the sensor is unable to send the movement signal to Homey or Homey is not processing it correctly. And this occurs after running for several days without an issue. The sensor seems to be working fine, since it does light up when I move.
Does anyone else have had this issue as well? And is there something I can do to fix this?
These flows work perfectly! Most of the time...
Last saturday, Homey suddenly said it believed the room was empty. Although we were with 5 people in the room, I thought it just missed us because we were too far away. So I waved and saw the motion sensor light up, indicating it noticed my movement. Unfortunately, after 10 seconds it just switched off the lights and we were all sitting in the dark. This happend again after I switched on the lights using the app.
I have had this one time before and exactly the same way. After a reboot of Homey, everything seems to be working fine again.
It looks like for some reason, either the sensor is unable to send the movement signal to Homey or Homey is not processing it correctly. And this occurs after running for several days without an issue. The sensor seems to be working fine, since it does light up when I move.
Does anyone else have had this issue as well? And is there something I can do to fix this?
Comments
After a reboot of Homey, the same flows were working fine for days.
I have also a Aeotec MultiSensor 6 - (Gen5), and the Aeotec MultiSensor 6 works very well. No problems and the Aeotec is at a larger distance from homey than my fibaro multisensor.
So i don't think the radios in homey is the problem.
I am also having this (or similar) problem.
The first detection of the sensor (confirmed by LED): no reaction of Homey.
When the Fibaro is back in the “No movement” state and is activated (movement) again, Homey reacts as it should.
After that Homey is working properly, until 15-30 min of no detection and the issue reappears.
(All the latest updates applied and rebooted)
The sensor is used to turn on the light in the morning and to sense movement. IF there is no movement for 24 hours THEN a preset holliday is set.
I don't have it in the livingroom but on the stairway, so you can say that it is not so intensive activated as for you.
But what i have is two wall plugs (fibare Z-wave+) in my livingroom one on the first floor and one on the attic.
One wallplug in the livingroom is about 1 meter from the Homey away. Maybe for using these wall-plugs it helps to get a more stable network between the sensors.
Hope it helps to solve your problem.
[edit]
If you change the settings in the motion sensor this was said in an other topic. I think/know some settings will be saved better if u used the method here under:
I'm not sure what settings would be of influence for this issie. It looks more of an issue in Homey or the app instead of the sensor itself. Maybe a memory issue or something?
Most of the time the sensor is running fine and notices all movements immediately. The problem only occured after a few weeks without a reboot. After the reboot, it was fine again.
I use the same sensors for notification of movement in the house and they do that perfectly . Could it be that settings of "blindtime" and or "annuleringsperiode" are interfering with the countdown timer?
This is wat happend in your case and maybe will happen again when your livingroom is more populated.
The fibaro sees motion and the timer will be triggerd. With the settings you maybe now have, the timer will never triggerd again. Altough your motion sensor sees all the time motion. If the motion sensor doesn't stop seeing motion then the timer will never triggerd again and will end. This will trigger in your case the lights off.
In normal situation when less poeple are in your livingroom the motion sees sometimes no movement. When there is movement again then your timer will be triggert and is reset again.
How is this possible. Because of your settings of your fibaro motion sensor ( Well it could be) let me explain.
If you add the fibaro motion sensor then standard settings are set like that the sensor movement will stop at after 30 seconds of movement. See pic below the 2 i changed. It was first 30 seconds
these 30 seconds movement will be active in homey and if you move, the 30 seconds are set again. So if you have a populated house, it is possible that your motion sensor will be triggered multiple times in less then 30 sec Although there could be no movement for maybe 10 seconds, the 30 sec delay will be seen as movement in homey. If this goes on all evening(15 min) then your Timer will never reset and your lights will switch off.
So i changed the 30 seconds in 2 second. I also made sure that the lbindtime (See pic below) is greater then the 2 sec delay. (4 sec)--> number 7
In this time the sensor will not react on new motion and therefor the motion sensor always triggers . In your case the Timer.
In normal situations where there are not alot movements the standard setup will work because there will be no movement in 30 sec.
This is how i believe it works and how i have mine sensor setup in populated situations for HOMEY.
It is all about triggering
I hope i made myself a little bit clear
The reason am asking is it's all working like it should over here. With + and non+ sensors. So maybe it's something in ur settings or flows we do different.
My bathroom lights go out after 60 seconds no matter what movement it detects. You can see my flow for triggering the lights and the timer flow that should keep the lights on until there is no movement detected anymore.
Anything wrong with these?
did you first wake up the motion sensor before you saved the new settings.
stop movement-------start timer
timer empty-------kill lights
https://forum.athom.com/discussion/comment/42524/#Comment_42524
Will try the example you point out. Thanks