I found the INT-ZWAV-MTD Inteset Motion/Light/Temp sensor for under $16. Great price! You can find it if you use goo gle to search for it. But on amaz, for some reason you can't find it by searching. Looking at the reviews, one user posted that he was able to add it to his Hubitat. Unfortunately, he didn't elaborate on what built in device driver he used since for some reason there are no Inteset devices supported with built in drivers.
Well, I purchased four due to the great price!! Once received, I realized they must be a rebranded Dome product since they are the exact same size, design, etc to my 3 existing Dome motion sensors. However, my Dome sensors only provide motion and light (no temp).
Anyway..... after attempting several different drivers, the only one that I can get anything working on is the Dome motion sensor driver. However, even with this driver, I cannot get this device to do anything more than join, and report it's condition when it joins. After that its motion status stays on "active". When looking at the logs, I see communication stops with a 'warning' of "configure...".
The device state variables show are the same as the Dome (which I think is expected since that is the driver I chose), and many of the values are the same, but on different config values.
My working Dome device:
- configVal1 : 28
- configVal2 : 30
- configVal6 : 8
- configVal7 : 180
- configVal9 : 49
- pendingRefresh : false
- configVal10 : 0
My non working Inteset device:
- configVal1 : 28
- configVal2 : 2
- configVal6 : 30
- configVal7 : 1
- configVal9 : 49
- pendingRefresh : true
- configVal10 : 180
At any rate, I think the key is that the device log just keeps repeating "Config" whenever I wake the device up using the button on the device. Not much else in the logs.
dev:1952023-02-04 12:59:57.545 pm warn configure...
dev:1952023-02-04 12:20:58.897 pm warn configure...
dev:1952023-02-04 12:14:19.089 pm warn configure...
dev:1952023-02-04 12:13:06.411 pm infoZ-Wave command:SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[0, 113], size:2, scaledSensorValue:113)
dev:1952023-02-04 12:10:52.402 pm infoZ-Wave command:WakeUpIntervalReport(nodeid:1, seconds:43200)
dev:1952023-02-04 12:10:52.366 pm infoZ-Wave command:WakeUpNotification()
dev:1952023-02-04 12:09:08.461 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: , sequenceNumber: 0)
dev:1952023-02-04 12:08:59.956 pm infoZ-Wave command:WakeUpNotification()
dev:1952023-02-04 12:08:57.484 pm infoZ-Wave command:WakeUpIntervalReport(nodeid:1, seconds:43200)
dev:1952023-02-04 12:08:57.377 pm infoZ-Wave command:SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[0, 22], size:2, scaledSensorValue:22)
dev:1952023-02-04 12:08:57.315 pm infoZ-Wave command:BatteryReport(batteryLevel:91)
dev:1952023-02-04 12:08:57.307 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 1, eventParameter: , sequenceNumber: 0)
dev:1952023-02-04 12:08:34.494 pm infofingerprint mfr:"039A", prod:"0003", deviceId:"0106", inClusters:"0x5E,0x9F,0x55,0x86,0x73,0x85,0x8E,0x59,0x72,0x5A,0x80,0x84,0x30,0x71,0x31,0x70,0x6C"
dev:1952023-02-04 12:08:34.490 pm debugbuilding fingerprint for unknown Z-Wave device...
dev:1952023-02-04 12:08:32.459 pm debugconfigure() called...
I'm hopeful that someone with much more experience than I with this type of behavior might recognize it and be able to help me get these working. Thanks to anyone in advance!!