Author Topic: Neo Coolcam Motion Sensor not recognized as Motion Sensor neither door/window  (Read 1372 times)

Offline fje

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +0/-0
Hi, I just got a Vera Edge controller and a Neo Coolcam Motion Sensor. Tried to connect it pairing to the Vera Edge but it is not recognized as it should be, a sensor of motion.

It only allows me to define a scene when it is switched ON or OFF, no options about motion detecting.

As it is not in the Vera Edge list of devices, I tried to define it as the ones more similar: Fibaro 4 in 1 and Doom Motion Detector (that, by the way, I found in another topic that worked for another users of it).

But no way, it takes the icon of a "General Z-Wave device" and only accepts ON or OFF

Am I doing anything wrong? Should I give back it to the seller?

Thanks and kind regards.

Javier
« Last Edit: June 09, 2018, 04:31:06 am by fje »

Offline zedrally

  • Hero Member
  • *****
  • Posts: 1124
  • Karma: +11/-5
  • Black Cat Control Systems
Re: Neo Coolcam Motion Sensor not recognized as Motion Sensor
« Reply #1 on: June 08, 2018, 09:08:27 pm »
Occasionally it takes 24 hours for Vera to properly recognise devices, I'd wait for a day and see what happens after a system heal.
Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, Fantem Tec and then some  Black Cat Cat's Eye PIR's & Door-Window Sensors, RFXComm, Broadlink RMPro & Mini plus a Z-UNO or 2.

Offline Don Phillips

  • Hero Member
  • *****
  • Posts: 1326
  • Karma: +35/-32
Re: Neo Coolcam Motion Sensor not recognized as Motion Sensor
« Reply #2 on: June 08, 2018, 09:09:36 pm »
And sometimes, a reboot after a pairing helps as well.
Vera 3, 1.7.1030, CT101, Everspring motion sensor, GE/Jasco switch, Leviton outlet, AeonLabs sensor, NuTone garage door, Blue Iris, Sricam SP011, iPhone locator, APCUPSD, VeraMate, VeraAlerts, PLEG, House Modes, Countdown Timer, DVR, Virtual/Multi Switch, Weatherunderground, LB60Z-1 bulb, Hue, Alexa

Offline sj3fk3

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Neo Coolcam Motion Sensor not recognized as Motion Sensor
« Reply #3 on: June 09, 2018, 02:31:41 am »
For me they work a little, but they are not recognized properly. Can't change very much needed configuration parameters.

Offline fje

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +0/-0
Re: Neo Coolcam Motion Sensor not recognized as Motion Sensor
« Reply #4 on: June 09, 2018, 02:59:41 am »
OK, thanks for your answers. I will do both things and come back with results.

Javier

Offline fje

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +0/-0
Reboot done.... Same situation?. >:(

Waiting for the 24 hours lap time suggested. I will update.

By the way, I have same situation with the Neo Coolcam Door/Window sensor. Also defined as Doom Door/Window sensor because it seems to be, at least externally and internally, identical.

Regards

Javier

Offline cw-kid

  • Hero Member
  • *****
  • Posts: 1560
  • Karma: +16/-2

Offline fje

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +0/-0
Hi, cw-kid.

Thanks for your answer. I follow what wrote in the ref. post and, at least, the devoice is now recognized as it had to be.

Now it is time t work with the push-notifications with pushover.

And to contact support for the door/window sensor....

Thanks.

Javier

Offline cw-kid

  • Hero Member
  • *****
  • Posts: 1560
  • Karma: +16/-2
I don't have any Neo CoolCam door /  window sensors what is the problem with those? Are they also not recognised as the correct device type?

Offline cw-kid

  • Hero Member
  • *****
  • Posts: 1560
  • Karma: +16/-2
It might just be a case of editing the Neo CoolCam door / window device with the correct properties for that type of device:

device_type = urn:schemas-micasaverde-com:device:DoorSensor:1
device_file   = D_DoorSensor1.xml
device_json = D_DoorSensor1.json
category_num = 4
subcategory_num = 1

I had a similar problem with some Heiman HS1DS-Z Door / Window Sensors

See here

« Last Edit: June 10, 2018, 10:30:41 am by cw-kid »

Offline fje

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +0/-0
It might just be a case of editing the Neo CoolCam door / window device with the correct properties for that type of device:

device_type = urn:schemas-micasaverde-com:device:DoorSensor:1
device_file   = D_DoorSensor1.xml
device_json = D_DoorSensor1.xml
category_num = 4
subcategory_num = 1

I had a similar problem with some Heiman HS1DS-Z Door / Window Sensors

See here

Hi, cw-kid, thanks again for your help.

This is exactly what I did, taking the data from the example that comes with the Vera Edge Dashboard, BUT, I feel it doesn't work correctly, it doesn't detect when the magnet is separated from the detector, this is the reason I addressed support too.

BTW, I do believe that the device_json parameter should be D_DoorSensor1.json (not .xml in this one)

Additionally, in the example included in the dashboard, the id_parent and the embedded parameters are used. In the "generic" one to-be-modified it is not and I didn't change it?. Do you know if I should change also them?

Regards

Javier

Offline cw-kid

  • Hero Member
  • *****
  • Posts: 1560
  • Karma: +16/-2
Yes it should be D_DoorSensor1.json was a typo.

For the Heiman HS1DS-Z Door / Window Sensors I have, I had to modify the parent device and then hide the unneeded child device.

Not sure if you need to do the same with the Neo Coolcam door / window sensor device?

Offline fje

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +0/-0
Let me copy here how is MY "Door/Window sensor" defined in the ref. parameters:


id_parent      1

 nobulk
 embedded
 disabled
 restricted

device_file   D_DoorSensor1.xml

id               25

*******

And this how it is defined in the example that comes with the dashboard:


id_parent    25

 nobulk
V embedded (marked)
 disabled
 restricted

device_file   D_DoorSensor1.xml

id             26

**********

Similar differences can be found in my definition of "Motion Sensor" and the one as example in the dashboard. Motion works, Door seems not to work.

Anyway, are you or any other one able to explain what is the meaning of those parameters and/or the importance and influence of their values? Is it normal that the id of my door sensor is at the same time the id_parent of the example? In the case of the motion sensor there is no relation between them.

Thanks and kind regards.

Javier

Offline cw-kid

  • Hero Member
  • *****
  • Posts: 1560
  • Karma: +16/-2
"id" is the device # number.

"id_parent" is the ID number of the parent device, if there is one?

For devices that do not have a parent device the id_parent seems to be populated with "1".

I wouldn't worry too much about these values.

Offline cw-kid

  • Hero Member
  • *****
  • Posts: 1560
  • Karma: +16/-2
So in your case the device with id # 26 is the child device.

The device with id # 25 is the parent device.

I would modify the parent device as discussed and if that then looks correct and works as a door sensor?

Just hide the child device from the UI7 GUI.