# Neo Coolcam PIR not (?) switching on when the room is crowded

**URL:** <https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279>\
**Category:** Questions & Help\
**Tags:** zigbee, flow, homey-pro\
**Created:** [May 3, 2022, 3:12pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279 "2022-05-03T15:12:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frank\_van\_de\_Schuur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frank_van_de_schuur/32/35882_2.png) [@Frank\_van\_de\_Schuur](https://community.homey.app/u/Frank_van_de_Schuur)\
**Post date:** [May 3, 2022, 3:12pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/1 "2022-05-03T15:12:51Z")

</div>

I have flows that are triggered by a neo coolcam detecting motion. The flows then start a down counter with value 1800 and when that counter is at zero (meaning no motion has been detected the last 30 mins) everything is switched off, including lights, radio etc etc.  
Now this normally works fine, but it happened already a few times when I had the room full of people somehow the room goes dark and music switches of. 😩

My theory is that the PIR is detecting motion all the time and thus it stays in the state _motion detected_’. So the transition from _no-motion_ to _motion_ never happens and thus the flows are not triggered. BUT…  
Wouldn’t the blind time prevent the the PIR from staying in that state forever?

Has anyone experienced the same problem as I have? If so how did you solve it?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [May 3, 2022, 4:23pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/2 "2022-05-03T16:23:47Z")

</div>

If you longpress the device tile, you can view the motion:true and motion:false events timestamps, by pressing the `=` icon

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [May 3, 2022, 4:27pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/3 "2022-05-03T16:27:46Z")

</div>

Can’t you trigger on the transition from motion to no-motion?

---

<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:** [May 3, 2022, 4:40pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/4 "2022-05-03T16:40:02Z")

</div>

That seems like it was fixed by many, many people now by thinking the other way around like [**this topic**](https://community.homey.app/t/simple-lights-turning-on-off-based-on-motion/10889) explains.

---

<div class="post-metadata">

**Author:** ![Frank\_van\_de\_Schuur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frank_van_de_schuur/32/35882_2.png) [@Frank\_van\_de\_Schuur](https://community.homey.app/u/Frank_van_de_Schuur)\
**Post date:** [May 3, 2022, 5:11pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/5 "2022-05-03T17:11:08Z")

</div>

Yea i can, but as I describe i don’t think that transition is happening. Since there is constantly motion detected.  
Also i just noticed that the ‘blind time’ is always smaller than the ‘on-time’.  
So this probably means that direct after the ‘blind-time’ and before the end of ‘on time’ it detects motion again and just stays on.

---

<div class="post-metadata">

**Author:** ![Frank\_van\_de\_Schuur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frank_van_de_schuur/32/35882_2.png) [@Frank\_van\_de\_Schuur](https://community.homey.app/u/Frank_van_de_Schuur)\
**Post date:** [May 3, 2022, 5:11pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/6 "2022-05-03T17:11:49Z")

</div>

Browsed through your link but didn’t see anything describing my specific problem

---

<div class="post-metadata">

**Author:** ![Frank\_van\_de\_Schuur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frank_van_de_schuur/32/35882_2.png) [@Frank\_van\_de\_Schuur](https://community.homey.app/u/Frank_van_de_Schuur)\
**Post date:** [May 3, 2022, 5:14pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/7 "2022-05-03T17:14:17Z")

</div>

I guess the solution is that when the counter is zero AND the PIR is not in ‘motion detected’ state Then the lights must be switched of. Else the counter is reset again

---

<div class="post-metadata">

**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\
**Post date:** [May 3, 2022, 5:16pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/8 "2022-05-03T17:16:05Z")

</div>

> [@Frank\_van\_de\_Schuur](#):
>
> anything describing my specific problem

The counter in this example is only started when the PIR sends End Of Move !!!

---

<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:** [May 3, 2022, 5:27pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/9 "2022-05-03T17:27:59Z")

</div>

The first post in that topic **is** meant for the same issue as you are describing, _the light turning off while there is still motion_.

It is exactly as you are already describing too, the motion **will stay on** if there is/was motion before it is cancelled, you can lower the “cancel” to something really low (on some brands), but even that well not always catch that when there is a party going on with dancers, or just movement all around.  
The blind time setting is just to save battery on sensors, I believe most brands don’t allow to have it lower then the cancellation time, it will still only cancel when the blind time is also over.

So the topic I shared explains to start the timer on **when the motion turns off** , instead of when it turns on like you are doing now.  
And _stops_ the timer again when there does was a motion sensed again.  
It does take 1 extra flow, but solves 99%+ of all cases where lights turn off when there is still motion going on.

In the end, you could also choose the **“zone becomes inactive for …”** trigger card, as that also has a 30 minute option, that only has the limitation of the limited amount of “inactive” time options.

---

<div class="post-metadata">

**Author:** ![Frank\_van\_de\_Schuur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frank_van_de_schuur/32/35882_2.png) [@Frank\_van\_de\_Schuur](https://community.homey.app/u/Frank_van_de_Schuur)\
**Post date:** [May 3, 2022, 8:41pm UTC](https://community.homey.app/t/neo-coolcam-pir-not-switching-on-when-the-room-is-crowded/63279/10 "2022-05-03T20:41:18Z")

</div>

Ah… on second thought you might be right. My apologies for being a bit stubborn and not reading thoroughly enough.  
I understand now the different way of thinking, have to give that another thought before doing the implementation
