Neo CoolCam Door/Window Sensor

Forum rules

Questions about hardware that can be controlled by Indigo (but not through the interfaces and plugins listed). If Indigo doesn't support some bit of hardware you're interested in, and you don't find a 3rd Party Plugin for it, add it to this forum. Be sure to include links to as much information as you can find about it.

Note: adding it here does not mean we're going to add it - in fact it's possible one of our 3rd party developers may decide to write a plugin for it. We add hardware/features based on a lot of different factors beyond just having a request for it.

Posted on
Sun Jul 09, 2017 12:06 pm
CliveS offline
Posts: 761
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Neo CoolCam Door/Window Sensor

bluefightingcat wrote:
Just tested this out. Works great so far.


I have just ordered two of these from Ali Express, seems a great price at £15.50 each (plus vat if they are stopped at customs) when compared to the £40 pounds plus for the Fibaro/Aeotec/Philio varieties.

Have you had any problems with them so far apart from Indigo support?

Has anyone tried the other Neo Coolcam devices yet like the NAS-PD01Z Z-wave PIR Motion Sensor, NAS-WS01Z Z wave Flood Water Leak Alarm Sensor and 1/2CH EU Wall Switch Sensor all around the £20 to £25 price range.

CliveS

CliveS

Indigo 2023.2.0 : macOS Ventura 13.6.3 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Tue Oct 17, 2017 9:22 am
Lucardos offline
Posts: 17
Joined: Aug 31, 2012
Location: Netherlands

Re: Neo CoolCam Door/Window Sensor

received today the Neo water sensor, WS01Z

unfortunately this does not work with indigo. Battery indication works, but the on/off does not.

here is the log of the water sensor " node 60" :

on:
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 3C 09 71 05 00 00 00 FF 05 02 00 4D
Z-Wave Debug . . requestAlarmSensorStatus: node 060, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 5, valueExt 2, classSubKeyExt 7100000502
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 3C 04 30 03 FF 06 03
Z-Wave Debug . . requestBinarySensorStatus: node 060, endpoint None, type 6, value 255

off:
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 3C 0A 71 05 00 00 00 FF 05 00 01 02 50
Z-Wave Debug . . requestAlarmSensorStatus: node 060, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 5, valueExt 0, classSubKeyExt 7100000500
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 3C 04 30 03 00 06 FC
Z-Wave Debug . . requestBinarySensorStatus: node 060, endpoint None, type 6, value 0

battery level:
Z-Wave Debug RCVD nodeAwake: 01 08 00 04 00 3C 02 84 07 4E
Z-Wave Debug . . nodeAwake: node 060
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 3C 02 80 02 25 07 7B
Z-Wave Debug . . nodeAwake: inhibit count++ to 1
Z-Wave Debug . . nodeAwake: started inhibit sleep timer
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 3C 03 80 03 64 2A
Z-Wave Debug . . requestBatteryLevel: node 060, level 100
Z-Wave received "060 - water sensor” status update battery level 100%

Posted on
Tue Oct 17, 2017 10:00 am
CliveS offline
Posts: 761
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Neo CoolCam Door/Window Sensor

Click on 'Write Device Information to Event log' in the device config dialog and also the 'Define and Sync' and post them here.

Look at the beginning of this thread about either using raw commands to trigger your Neo Water Sensor before the profile is incorporated into Indigo ( I used them on the Neo Motion Sensor when I first got it without Indigo support)

jay (support) wrote:
You might be able to catch specific incoming messages from it using the Match Raw Packet message in the Incoming Command Received from Device Z-Wave trigger event.

or as I see 01 0F 00 04 00 3C 09 71 05 00 00 00 FF 05 02 00 4D so it may be possible to use the Zwave Lock Manager plugin
howartp wrote:
Just glancing at that log, you should be able to use my Zwave Lock Manager plugin to monitor that device.
71 05 alarm status commands are implemented so off top of my head it should work.

howartp wrote:
http://forums.indigodomo.com/viewtopic.php?f=210&t=17185&p=140487

Create a dummy door lock device (everything in this plugin is currently called a Lock even if it isn't!) and point it at your door/window sensor.

Create a trigger for your dummy lock with trigger event of ZWave Lock Manager Plugin > Door Opened.

Peter


CliveS (and welcome to the Neo club :) )

CliveS

Indigo 2023.2.0 : macOS Ventura 13.6.3 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Tue Oct 17, 2017 10:48 am
Lucardos offline
Posts: 17
Joined: Aug 31, 2012
Location: Netherlands

Re: Neo CoolCam Door/Window Sensor

thanks CliveS

see below event log.
For me this is new ( always worked with compatible z-wave devices) and im struggling with the match Raw packet and door lock plugin.
will need some time to play with this.


Indigo Z-Wave Version: 2.0.68
Node ID: 60
Model: Notification Sensor
Model ID: 00031085
Manufacturer: Unknown
Manufacturer ID: 0258
Protocol Version: 4.05
Application Version: 2.54
Model Definition Version: 0
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 4, 15, 16, 17, 24, 25, 27, 28, 50, 52
Associations: 1:[1] 2:[] 3:[] 4:[]
Config Values: - none -


Z-Wave Syncing - started for "060 - water sensor"
Z-Wave Syncing - retrieved module neighbors list: 4, 15, 16, 17, 24, 25, 27, 28, 50, 52
Z-Wave Syncing - assigning return route to "060 - water sensor"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Unknown - 0258, Notification Sensor - 00031085
Z-Wave Syncing - retrieved protocol version 4.05, app version 2.54
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Syncing - retrieved wake interval of 60 minutes
Z-Wave Syncing - device "060 - water sensor" wake interval changed to 60 minutes
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - complete

Posted on
Tue Oct 17, 2017 11:39 am
Lucardos offline
Posts: 17
Joined: Aug 31, 2012
Location: Netherlands

Re: Neo CoolCam Door/Window Sensor

CliveS

thanks for your help.
It worked with the Match Raw packet.

hopefully Indigo will support all Noe products in the near future.

Lucardos

Posted on
Tue Oct 17, 2017 12:19 pm
CliveS offline
Posts: 761
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Neo CoolCam Door/Window Sensor

Lucardos wrote:
CliveS

thanks for your help.
It worked with the Match Raw packet.

hopefully Indigo will support all Noe products in the near future.

Lucardos


Great, well done, I also had trouble working out the Raw Packets initially but this forum does help so much.

We just need to sort out our problem with the EU plug power readout failing, I have been trying to find another home automation software that runs on either Windows or Pi that does not need a PhD in Nuclear Physics to install so I can try it out on another setup as the feedback from AliExpress says that the Power readings work with several other HA systems without error.

No luck so far and it makes me realise just how easy Indigo is to setup and run!

I will add the Water Sensor to it's own thread as it is lost in this thread at present.

CliveS

Indigo 2023.2.0 : macOS Ventura 13.6.3 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Tue Oct 17, 2017 12:46 pm
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Neo CoolCam Door/Window Sensor

Can you link me to thread about EU plug Power readout?


Sent from my iPhone using Tapatalk Pro

Posted on
Tue Oct 17, 2017 12:57 pm
CliveS offline
Posts: 761
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Neo CoolCam Door/Window Sensor

howartp wrote:
Can you link me to thread about EU plug Power readout?


Certainly :) , I would love to get this working as Domoticz users say they have no problem yet I have 2 and @Lucardos has 1 and all 3 have the same problem of constantly resetting the power reading.

http://forums.indigodomo.com/viewtopic.php?f=58&t=19010&p=146281&hilit=neo+eu+power#p146281

CliveS

Indigo 2023.2.0 : macOS Ventura 13.6.3 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Thu Nov 09, 2017 11:21 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Neo CoolCam Door/Window Sensor

Indigo 7.1.1 is now available for download and supports the Neo CoolCam door/window sensor.

Image

Posted on
Thu Oct 17, 2019 5:35 am
Eagleye offline
Posts: 82
Joined: Jan 14, 2019

Re: Neo CoolCam Door/Window Sensor

Have recently purchased a number of Neo CoolCam Door/Window sensor, but I'm facing the current operating issues.

I can successfully include & synchronise the device with Indigo. The state of the device reads "off", but when I move the "deputy body" towards the main body and the light blinks red, the state changes to "Pending change" and then continously wats for acknowledgement. I need to press the inclusion button on the device multiple time, together with the Send Status Request" button in Indigo for it the re-establish connection.

When connection is reestablished, I get the following message:
Z-Wave - received "109 - Window Sensor - East Window" status update battery level 100%
Z-Wave Debug - SENT requestAlarmSensorStatus: 01 09 00 13 6D 02 71 04 25 C3 19

At no stage does the State ever change to "on" when I move the "Deputy body" to /from the main body, which means that the sensor is not delivering any changed state to Indigo.

Are you able to assist with this?

John

Posted on
Thu Oct 17, 2019 12:19 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Neo CoolCam Door/Window Sensor

Hi John,

I don't believe the pending state should show unless you are trying to send the module a message from Indigo. In this case I think the pending may be coming from you pressing the Status Request button (Indigo cannot query out the state until the module wakes up). Is that possibly what happened? That is, the pending message didn't occur until after you pressed the Status Request button?

With Debug logging turned on (looks like you had it on for the log snippet above) you are not seeing any messages arrive (debug logging) when you move the magnet too/from the module? I'd expect it to send something, even if Indigo wasn't routing it to the correct internal device state.

Also, can you include the Event Log result of the sync with the module in a reply? I'd like to see exactly how it is identifying itself and its capabilities to Indigo.

Image

Posted on
Thu Oct 17, 2019 2:50 pm
Eagleye offline
Posts: 82
Joined: Jan 14, 2019

Re: Neo CoolCam Door/Window Sensor

Please see be below as requested, I have also add a screen shot of the configure on/off sensor mould setting dialogue, and a device detail from the event log.
I hope this is what you are after.

Sync Log
Z-Wave Syncing - started for "Window Sensor - East Window"
Z-Wave Debug RCVD multiEndPointPacket: 01 12 00 04 00 3C 0C 60 0D 01 01 32 02 21 32 00 00 00 00 97
Z-Wave Debug . . multiEndPointPacket: node 060, endPoint 1
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 3C 08 32 02 21 32 00 00 00 00 FF
Z-Wave Debug . . requestMeterLevel: node 060, endpoint 1, meterType 01, raw value 3200...
Z-Wave Debug . . requestMeterLevel: 0.0 W (float: 0.000000)
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 6D 01 01 14
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 36 00 00 00 00 08 02 00 A4 02 D2 00 86 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90
Z-Wave Debug . . getNodeNeighbors: nodeId 109, neighbors: 2, 3, 5, 6, 44, 50, 67, 70, 72, 74, 82, 85, 87, 88, 98, 99, 104
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 5, 6, 44, 50, 67, 70, 72, 74, 82, 85, 87, 88, 98, 99, 104
Z-Wave Syncing - assigning return route to "109 - Window Sensor - East Window"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 6D 01 D0
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 109, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 6D 24 B6 66
Z-Wave Debug RCVD nodeInfoFrame: 01 15 00 49 84 6D 0F 04 07 01 5E 86 72 5A 73 80 71 30 85 59 84 70 2D
Z-Wave Debug . . nodeInfoFrame: node 109, combined class list: 20v1 80v1 84v1 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 6D 02 72 04 25 B7 6E
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 6D 08 72 05 02 58 00 03 60 82 5C
Z-Wave Debug . . requestManufactureInfo: node 109, manufacturerId 0258, productId 00036082
Z-Wave Debug . . requestManufactureInfo: Neo, Notification Sensor
Z-Wave Syncing - retrieved manufacture and model names: Neo - 0258, Notification Sensor - 00036082
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 6D 02 86 11 25 B8 80
Z-Wave Debug RCVD requestVersInfoGen: 01 0F 00 04 00 6D 09 86 12 06 04 05 03 50 41 00 11
Z-Wave Debug . . requestVersInfoGen: node 109, protoVers 4.05, appVers 3.80
Z-Wave Syncing - retrieved protocol version 4.05, app version 3.80
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 6D 03 86 13 84 25 B9 05
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 6D 04 86 14 84 02 8C
Z-Wave Debug . . requestVersInfoCmdClass: node 109, class command 84 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 109, combined class list: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Debug SENT requestWakeInterval: 01 09 00 13 6D 02 84 05 25 BA 94
Z-Wave Debug RCVD requestWakeInterval: 01 0C 00 04 00 6D 06 84 06 00 01 2C 01 32
Z-Wave Debug . . requestWakeInterval: node 109, interval 5 minutes, wakeTarget 001
Z-Wave Syncing - retrieved wake interval of 5 minutes
Z-Wave Debug SENT setWakeInterval: 01 0D 00 13 6D 06 84 04 00 01 2C 01 25 BB B8
Z-Wave Syncing - device "109 - Window Sensor - East Window" wake interval changed to 5 minutes
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 6D 02 85 05 25 BC 93
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 6D 03 85 06 04 1B
Z-Wave Debug . . requestAssociationGroupCount: node 109, group count: 4
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 6D 03 85 02 01 25 BD 96
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 6D 06 85 03 01 05 00 01 1F
Z-Wave Debug . . requestAssociations: node 109, group: 1, num associations: 1, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 109, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 6D 03 85 02 02 25 BE 96
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 6D 05 85 03 02 05 00 19
Z-Wave Debug . . requestAssociations: node 109, group: 2, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 109, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 6D 03 85 02 03 25 BF 96
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 6D 05 85 03 03 05 00 18
Z-Wave Debug . . requestAssociations: node 109, group: 3, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 109, group: 3, associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 6D 03 85 02 04 25 C0 EE
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 6D 05 85 03 04 05 00 1F
Z-Wave Debug . . requestAssociations: node 109, group: 4, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 109, group: 4, associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 6D 02 80 02 25 C1 EC
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 6D 03 80 03 64 7B
Z-Wave Debug . . requestBatteryLevel: node 109, level 100
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - complete
Z-Wave Debug SENT requestAlarmSensorStatus: 01 09 00 13 6D 02 71 04 25 C2 18
Z-Wave Debug terminatingSyncUI
Z-Wave sent "Window Sensor - East Window" status request
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 6D 02 80 02 25 C3 EE
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 6D 03 80 03 64 7B
Z-Wave Debug . . requestBatteryLevel: node 109, level 100
Z-Wave received "109 - Window Sensor - East Window" status update battery level 100%
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 6D 03 80 03 64 7B
Z-Wave Debug . . requestBatteryLevel: node 109, level 100
Z-Wave received "109 - Window Sensor - East Window" status update battery level 100%
Z-Wave Debug SENT goToSleep: 01 09 00 13 6D 02 84 08 24 C4 E6
Z-Wave Debug RCVD packet: 01 07 00 13 C4 00 00 02 2D (hex)
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 14 06 31 05 01 22 00 A1 53
Z-Wave Debug . . requestVarSensorStatus: node 020, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 16.1 °C (float: 16.100000)

Device details
Indigo Z-Wave Version: 7.4.0
Node ID: 109
Model: Notification Sensor
Model ID: 00036082
Manufacturer: Neo
Manufacturer ID: 0258
Protocol Version: 4.05
Application Version: 3.80
Model Definition Version: 0
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 30v1 70v1 71v1 72v1 73v1 59v1 5Av1 5Ev1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 2, 3, 5, 6, 44, 50, 67, 70, 72, 74, 82, 85, 87, 88, 98, 99, 104
Associations: 1:[1] 2:[] 3:[] 4:[]
Config Values: - none -
Attachments
Screen Shot 2019-10-18 at 7.45.34 am.png
Screen Shot 2019-10-18 at 7.45.34 am.png (217.6 KiB) Viewed 3390 times

Posted on
Thu Oct 17, 2019 3:41 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Neo CoolCam Door/Window Sensor

That shows the sync but no other messages coming from the module. Did you move the magnet to and from the module several times with the debug logging enabled and nothing came through?

Also, what specific model number is on the module (either the module, or its box/instructions)? The particular model ID you have isn't in Indigo device definition list yet.

Image

Posted on
Fri Oct 18, 2019 8:47 pm
Eagleye offline
Posts: 82
Joined: Jan 14, 2019

Re: Neo CoolCam Door/Window Sensor

Matt,

Correct, I moved the magnet to and from the module several times with the debug logging enabled and nothing came through.

The model # is DZ2879-02B. If this model is not yet in the Indigo device definition list, do you know when you plan to include this?, as I have a number of these devices I'm looking at installing.

Posted on
Sat Oct 19, 2019 4:31 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Neo CoolCam Door/Window Sensor

I've added a device definition to the next version of Indigo (v7.4.1) for this module.

However, something else is going wrong if the module is not sending out any commands at all when you trip it (move the magnet to/fro). Because there is no definition I wouldn't expect Indigo to update its device state value, but with the debug logging enabled it should be receiving and logging a command every time the magnet is moved.

You might want to try excluding it, re-including, then re-syncing and testing it again (with debug logging on) to see if you can get any message to send from the module to the Z-Stick. Unfortunately, even with the device definition I added it isn't going to work if Indigo isn't receiving any commands from the module.

Image

Who is online

Users browsing this forum: No registered users and 4 guests