It's main attraction over other PIR's is its compact form factor - about the size of a table tennis ball - and it is claimed to be available in US, EU and JP models
I have been able to include the device, and synch it to Indigo with some difficulty - I think as the need to keep it awake during the process! However Indigo does not recognize the device, and I would like to request its support. The reported details are:
- Code: Select all
Z-Wave Indigo Device "016 - Black Cat Sensor" Z-Wave Properties:
Indigo Z-Wave Version: 2.0.68
Node ID: 16
Model: Notification Sensor
Model ID: 00036083
Manufacturer: Unknown
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 31v7 5Av1 5Ev1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 1, 4, 5, 8
Associations: 1:[1] 2:[] 3:[] 4:[]
Config Values: - none -
With ZWave debug on, the device reports the following status:
- Code: Select all
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 10 0A 71 05 00 00 00 FF 07 08 00 00 75
Z-Wave Debug . . requestAlarmSensorStatus: node 016, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 10 04 30 03 FF 0C 25
Z-Wave Debug . . requestBinarySensorStatus: node 016, endpoint None, type 12, value 255
As reported in other posts, there is a whole range of Neo stuff that needs to be suported by Indigo if possible.
Thanks,
mclass