# Fibaro motion sensor + flow

**URL:** <https://community.homey.app/t/fibaro-motion-sensor-flow/75047>\
**Category:** Devices\
**Tags:** z-wave, flow, homey-pro\
**Created:** [January 13, 2023, 8:53pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047 "2023-01-13T20:53:59Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Damian\_Surma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/damian_surma/32/48817_2.png) [@Damian\_Surma](https://community.homey.app/u/Damian_Surma)\
**Post date:** [January 13, 2023, 8:53pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/1 "2023-01-13T20:53:59Z")

</div>

I have such a problem with fibaro motion sensors. A very simple flow is created. If the sensor detects movement, it is the right time then turn on the lamp at 50% and after 2 minutes turn it off. And in general, the flow works, but after several dozen launches, a strange situation occurs and the lamp turns off after a dozen or so seconds. As if the sensor detected movement and after a while, when it detects movement, because it flashes green again, the lamp turns off.

 ![Opera Zrzut ekranu_2023-01-13_2153301_my.homey.app](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/5/b594563787aae670e4d0fcbb70aac5b19d3353bd.png)  
 ![Opera Zrzut ekranu_2023-01-13_215251_my.homey.app](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/6/c66305d58d0389208359a812fd18faa8c27921dd.png)

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [January 14, 2023, 10:01am UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/2 "2023-01-14T10:01:58Z")

</div>

This is not gonna work as you want probably: You cannot cancel the 2 minute delay. So when the motion is re-activated, it will still disable the light after the first motion-deactivation.

You will need a timer which you can cancel.

Take a look at this (importable) flow:

> [@The Flow Exchange(r) - Exchange Your Flows with Others!](https://community.homey.app/t/the-flow-exchange-r-exchange-your-flows-with-others/68981/24):
>
> Motion activated Light/Device, off after a certain time of no motion This flow uses a motion sensor to turn a device (light) on and after 5 minutes (can be adjusted) if no motion, it turns the device off. Set you device (light) and your motion sensor: Apps used: [Chronograph](https://homey.app/nl-nl/app/nl.fellownet.chronograph) TEF: [TEF:FLOWS:H4sIAAAAAAACA61UTW/bMAz9K4bOUadPS8p1O26n7TYUASVRiYHEDhy3WxHkv49WUqDBWizoeogtRRT9Ht8jjyyz5ZE5n6TGpLh1FrhBRB50VlxiDKpEJ4sLc1zPluxrt95MbMESrbd1fVowG61XzliuhfPcBFt4CJ5W2uoA…

(When you import the flow with the [Device Capabilitites App](https://homey.app/a/nl.qluster-it.DeviceCapabilities/), all flowcards will be in your language or English/Default).

---

<div class="post-metadata">

**Author:** ![Damian\_Surma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/damian_surma/32/48817_2.png) [@Damian\_Surma](https://community.homey.app/u/Damian_Surma)\
**Post date:** [January 14, 2023, 10:21am UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/3 "2023-01-14T10:21:57Z")

</div>

But the point is that when motion is detected, the light will turn on, but it will turn off after, for example, 10 seconds after switching on, despite the delay of 2 minutes.

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [January 14, 2023, 10:42am UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/4 "2023-01-14T10:42:34Z")

</div>

Okay:  
Motion is detected: light is turned on and a delay starts to turn it off.  
You walk out of motion.  
Within a minute, you walk into the motion again.  
The lamp will be turned on (thus: stays on) and another delay is started to turn it off.

But after a few seconds, the first delay to turn the light off, will still be executed.

A delay cannot be stopped, thats why you need a timer app. So you can cancel a turn-off-“delay” when motion is again detected.

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [January 14, 2023, 10:45am UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/5 "2023-01-14T10:45:29Z")

</div>

Your flow will only do what you want if you walk into a room and out of it immediately.

Because everytime the motion is triggered, you will turn the light on and after 2 minutes off, no matter what happens further.  
And you LOG shows that you tested the motion within those 2 minutes.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [January 14, 2023, 12:19pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/6 "2023-01-14T12:19:15Z")

</div>

As Arie said, the flow is restarted with each movement and then the lamp is turned off after 2 minutes each time.  
Some tutorials:

> [@\[Tutorial\] Simple movement-triggered automatic light with zone activity cards (just 2 flows!)](https://community.homey.app/t/tutorial-simple-movement-triggered-automatic-light-with-zone-activity-cards-just-2-flows/39651):
>
> Hi everyone, It’s time to share back what I learned here. I have -in the past- tried several strategies to use lights that automatically trigger when movement is detected. Also, a lot has been written about this topic, for example: [Tutorial - Advanced automatic light control with flows](https://community.homey.app/t/tutorial-advanced-automatic-light-control-with-flows/21877)[[Simple] Lights turning on/off based on motion - #33 by EvR](https://community.homey.app/t/simple-lights-turning-on-off-based-on-motion/10889/33) and many more. All of these either use the CountDown App -or- the Timer App This allows for a lot of flexibility. But it can be tricky to config…

> [@Tutorial - Advanced automatic light control with flows](https://community.homey.app/t/tutorial-advanced-automatic-light-control-with-flows/21877):
>
> Hi guys, I thought it was finally time to share my flows that I use to automatically control my lights. The setup I have is a bit more advanced than the suggestions I have seen on this forum, which is the reason for this tutorial. Some features of my setup: Automatically turn on and off lights based on motion (doh!) Only turn lights on when it’s dark Configuration of various scenes (e.g. Normal scene, Movie scene, Dinner scene, Romantic scene etc) Memory ability that will remember the brightn…

By the way, you can change some parameters in the advanced settings of the Fibaro Motion Sensor and thus influence the detection of movements.

---

<div class="post-metadata">

**Author:** ![Damian\_Surma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/damian_surma/32/48817_2.png) [@Damian\_Surma](https://community.homey.app/u/Damian_Surma)\
**Post date:** [January 14, 2023, 8:13pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/7 "2023-01-14T20:13:28Z")

</div>

But the point is that when motion is detected, the light will turn on, but it will turn off after, for example, 10 seconds after switching on, despite the delay of 2 minutes.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [January 14, 2023, 8:19pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/8 "2023-01-14T20:19:53Z")

</div>

As already mentioned before, the timer will **not reset** or **stop** at all, it will **keep running** no matter if the flow is triggered again.  
If the flow is triggered, and you trigger it a second or even third time, on the 1 minute en 50 second mark to have your responds as example, it will **turn off** the light because the first flow’s time is **still running** , and thus turn off the light 10 seconds after it was turned on thanks to the 2nd flow trigger.

Flow trigger 1 [16:50:00]: Turn on light, start delay  
Flow trigger 2 [16:51:50]: Turn on light (/stay on), start delay  
Flow trigger 1 [16:52:00]: Delay runs out: Turn off light  
Flow trigger 3 [16:53:40]: Turn on light, start delay  
Flow trigger 2 [16:53:50]: Delay runs out: Turn off light  
Flow trigger 3 [16:54:40]: Delay runs out: Turn off light (/stay off)

---

<div class="post-metadata">

**Author:** ![R\_Schumacher](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/r_schumacher/32/3736_2.png) [@R\_Schumacher](https://community.homey.app/u/R_Schumacher)\
**Post date:** [January 15, 2023, 12:12pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/9 "2023-01-15T12:12:01Z")

</div>

Think about using “Zone activation” instead.

Use two flows, one for turning on the light when the zone becomes active (sensor senses movement and time is…).  
Second flow to turn off the light when the zone has been inactive for x time.  
Works perfect for me. I also use luminance in the mix so that the light only goes on when it is dark enough.

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [January 16, 2023, 6:27am UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/10 "2023-01-16T06:27:28Z")

</div>

Indeed!

> [@The Flow Exchange(r) - Exchange Your Flows with Others!](https://community.homey.app/t/the-flow-exchange-r-exchange-your-flows-with-others/68981/5):
>
> Zone activated Light/Device with Lux condition Here is a flow that lets you control a light or other device, based on the lux of a sensor, when a zone detects motion. The light or device are only turned on/off when it’s not yet on/off. Just replace the items with your own: Required App [Chronograph](https://homey.app/nl-nl/app/nl.fellownet.chronograph/Chronograph/) TEF: H4sIAAAAAAACA7VWS5PbNgz+KzuaHJcpnyKpa3vM9NDuqR2PByRBW1Nb8sjyJunW/72gbO/a2abRbNODTVLC4wPwAdRT9Wff4f6h/wV3G4hYNU+VsoBCyZqBs4JpB8B8iJFJGVKSNZdWTnIdbGmtfiMDdz+X/fF4X6XyxgT…

With lux.

> [@The Flow Exchange(r) - Exchange Your Flows with Others!](https://community.homey.app/t/the-flow-exchange-r-exchange-your-flows-with-others/68981/8):
>
> Zone Activity Controlled Light / Device To prevent the light (or other device) from turning off (or on), while there’s still motion detected. It uses Homey’s Zone Activity AND a timer. This way your motion- & contactsensors become exchangeable and expandable, without having to fix the flow. This way, you can add a sensor, remove one (use 1 sensor minimum), use one with another protocol (f.i. zigbee/wifi/z-wave) in a zone. Apps used [Chronograph](https://homey.app/a/nl.fellownet.chronograph/)Flow example:

On zone activity.

---

<div class="post-metadata">

**Author:** ![RogerSt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rogerst/32/12432_2.png) [@RogerSt](https://community.homey.app/u/RogerSt)\
**Post date:** [January 16, 2023, 8:30pm UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/11 "2023-01-16T20:30:51Z")

</div>

And if you want to use timers per se, turn the light on when the motion is detected, and start the timer for turning off the light when the motion is no longer detected.

---

<div class="post-metadata">

**Author:** ![dsdevries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dsdevries/32/80220_2.png) [@dsdevries](https://community.homey.app/u/dsdevries)\
**Post date:** [October 15, 2025, 11:33am UTC](https://community.homey.app/t/fibaro-motion-sensor-flow/75047/12 "2025-10-15T11:33:37Z")

</div>

@Damian_Surma  
I realize that I’m reviving an old post, but I was wondering if you already figured it out, and if you are still having issues with your flows. If so, I recently created a tutorial that should do exactly what you want.  
see:

> [@\[HOW TO\] Gain full control over Zone Activity using Motion Sensors (PIR) and Virtual Motion Triggers](https://community.homey.app/t/how-to-gain-full-control-over-zone-activity-using-motion-sensors-pir-and-virtual-motion-triggers/144082):
>
> Introduction This is not a guide on how to implement a specific use case, but rather a framework that will give you full control over zone activity. Many flows like turning on/off lights could be done much simpler. However, when my personal flows became more complex, I ran into a lot of caveats and quirks that caused me to rethink how I work with motion sensors. I came up with this system which allowed me to solve all the bugs I ran into and I would like to share it with all of you. The problem…
