# Neo coolcam PIR v1 added as v2

**URL:** <https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570>\
**Category:** Questions & Help\
**Created:** [April 7, 2019, 4:51pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570 "2019-04-07T16:51:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Freddie\_Welvering](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/freddie_welvering/32/12623_2.png) [@Freddie\_Welvering](https://community.homey.app/u/Freddie_Welvering)\
**Post date:** [April 7, 2019, 4:51pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/1 "2019-04-07T16:51:17Z")

</div>

Yesterday my NeoCoolcam Pir V1 arrived.  
Added it today to homey but it is added as PIR V2 when selecting V1 in the add menu.

Anyone else had this problem or has a solution?  
When trying to disable the led in won’t disable it (sending the wrong parameters when viewing debug on developer)

Homey Firmware Version: 2.1.1-rc1  
NeoCoolcam app version: 2.0.19

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![Canedje](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/canedje/32/8324_2.png) [@Canedje](https://community.homey.app/u/Canedje)\
**Post date:** [April 7, 2019, 5:17pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/2 "2019-04-07T17:17:54Z")

</div>

It looks like you have a V2  
Not activatiecode the LED is a known bug  
Do you have temp meassuring?

---

<div class="post-metadata">

**Author:** ![Freddie\_Welvering](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/freddie_welvering/32/12623_2.png) [@Freddie\_Welvering](https://community.homey.app/u/Freddie_Welvering)\
**Post date:** [April 7, 2019, 5:27pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/3 "2019-04-07T17:27:15Z")

</div>

Yes i do have an temperature reading.

Giving a RAW command can set the led config.  
It seems none of the advanced config items is set correctly. In the box was a little manual with the correct parameters wich work on the raw config item.

Hope this will be fixed in the app. (Release notes indicate it was already fixed)

---

<div class="post-metadata">

**Author:** ![Canedje](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/canedje/32/8324_2.png) [@Canedje](https://community.homey.app/u/Canedje)\
**Post date:** [April 7, 2019, 6:26pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/4 "2019-04-07T18:26:13Z")

</div>

> [@Freddie\_Welvering](#):
>
> Yes i do have an temperature reading

Then it must be a V2  
You are happy a V2 for the price of a V1 😜

---

<div class="post-metadata">

**Author:** ![Anton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anton/32/10134_2.png) [@Anton](https://community.homey.app/u/Anton)\
**Post date:** [August 3, 2019, 7:15am UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/5 "2019-08-03T07:15:44Z")

</div>

> [@Freddie\_Welvering](#):
>
> Giving a RAW command can set the led config.

How did you do that?  
I have the same problem.

---

<div class="post-metadata">

**Author:** ![Anton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anton/32/10134_2.png) [@Anton](https://community.homey.app/u/Anton)\
**Post date:** [August 5, 2019, 11:56am UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/6 "2019-08-05T11:56:43Z")

</div>

never mind, I’ve already found it.

 ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/b/b8e06eb6fd7ac449d6ce91b98ff3e9f5baf7477d.png)

---

<div class="post-metadata">

**Author:** ![ArnoP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnop/32/13709_2.png) [@ArnoP](https://community.homey.app/u/ArnoP)\
**Post date:** [August 5, 2019, 2:27pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/7 "2019-08-05T14:27:53Z")

</div>

11,1,0 what does that exactly mean? If I look in the manual parameter 10 should be a byte set to 0 or 1, so I would expect 10,1,0 (10 for the parameter, 1 for a byte, 0 for the actual value).

Maybe I am mistaken and it means something completely different. Paramater 11 (which I think is 11,1,0) is MotionEventReportOneTimeEnable.

---

<div class="post-metadata">

**Author:** ![Anton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anton/32/10134_2.png) [@Anton](https://community.homey.app/u/Anton)\
**Post date:** [August 5, 2019, 2:59pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/8 "2019-08-05T14:59:15Z")

</div>

My manual says something else

 ![20190805_164515](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/8/8ba3fdd1ace4a75b12cc09ea7bf5507d86e99bed.jpeg)

---

<div class="post-metadata">

**Author:** ![ArnoP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnop/32/13709_2.png) [@ArnoP](https://community.homey.app/u/ArnoP)\
**Post date:** [August 5, 2019, 3:23pm UTC](https://community.homey.app/t/neo-coolcam-pir-v1-added-as-v2/11570/9 "2019-08-05T15:23:04Z")

</div>

Strange, mine says parameter 10, looked it up in several of my sensors’ manuals and all are the same, but most importantly: I now know how it works.
