- Code: Select all
Indigo Z-Wave Version: 2.0.111
Node ID: 44
Model: Notification Sensor
Model ID: 00030083
Manufacturer: Dome
Manufacturer ID: 021F
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 31v7 72v1 73v1 71v1 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: - none -
Associations: 1:[1] 2:[] 3:[] 4:[]
Config Values: - none -
Am I missing something in configuring it? I really like its form factor and especially its range. While it is not outdoor rated, because it attaches with a magnet to its base, I can put the sensor itself in a baggie and have it be reasonably weather resistant. And it's talking to Indigo while being a solid 10 m away from the nearest other z-wave device!
Oh, and it reports battery status correctly.
This is what I got when I triggered Motion while running debug.
- Code: Select all
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 2C 09 71 05 00 00 00 FF 07 08 00 55
Z-Wave Debug . . requestAlarmSensorStatus: node 044, 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 2C 04 30 03 FF 0C 19
Z-Wave Debug . . requestBinarySensorStatus: node 044, endpoint None, type 12, value 255
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2A 06 31 05 01 4A 1B C6 79