How do you connect this and where is the driver?
I don't see it listed in the list of compatible devices - List of Compatible Devices - Hubitat Documentation
That likely indicates it is not yet supported with a "built-in" driver. It may be supported with a community driver.
This device works for me using the
"Generic Z-Wave Motion Sensor" driver
You will have to set the sensitivity manually using the button on the unit.
@bart1 Did you have any issue with adding it to Hubitat. Mine get to initializing but never gets any further.
I moved it from wink but I did do a factory reset on it when I moved it. I don’t recall doing anything special for hubitat to add it in.
When I added this device, it came in with the incorrect device type/driver. I had to manually change the driver Generic Zwave Motion and then it worked, rather well.
I believe there's a humidity and/or thermostat in this device that we cannot access with the generic driver. If I could get a driver for this device it would probably be my favorite motion sensor based on performance/speed and additional sensors.
Sorry for bringing this old post back up, but I got a good deal on these sensors and having issues getting them to work.
By default, it comes up as "Device" and doesn't have a device driver associated it.
I switched it to Generic Z-Wave Motion Sensor and it doesn't detect motion, changed it to Jasco Smart Motion Sensor and still nothing. I reset the device, etc. Still no luck.
Has anybody successfully set this device up recently, or are currently using them? Any tips/tricks would be appreciated.
Log:
dev:18962022-09-13 12:25:49.269 pm warndescription logging is: true
dev:18962022-09-13 12:25:49.268 pm warndebug logging is: true
dev:18962022-09-13 12:25:49.267 pm infoupdated...
dev:18962022-09-13 12:25:23.954 pm infoZ-Wave command:WakeUpNotification()
dev:18962022-09-13 12:25:17.975 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 12:25:15.532 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 12:25:15.513 pm infoZ-Wave command:BatteryReport(batteryLevel:85)
dev:18962022-09-13 12:25:08.641 pm infofingerprint mfr:"0063", prod:"4953", deviceId:"3133", inClusters:"0x5E,0x86,0x72,0x59,0x85,0x73,0x71,0x84,0x80,0x30,0x70,0x7A,0x5A"
dev:18962022-09-13 12:25:08.639 pm debugbuilding fingerprint for unknown Z-Wave device...
dev:18962022-09-13 12:25:08.278 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 12:25:07.437 pm infoZ-Wave command:BatteryReport(batteryLevel:85)
dev:18962022-09-13 12:25:06.628 pm debugconfigure() called...
Switch back to the Generic driver, turn on all logging options. Set it off a couple of time and get a SCREENSHOT of the logs generated from that.
If you are not getting good logs with that driver, you could also switch to the "Device" driver which should log every incoming event from the device.
1 Like
Swapped to Generic and it worked for a couple active/inactive and then no longer detected motion, etc.
dev:18962022-09-13 01:05:26.062 pm debugparsed 'zw device: 3B, command: 7105, payload: 00 00 00 FF 07 08 00 00 , isMulticast: false' to [[name:motion, value:active, descriptionText:X's Z-Wave Motion Sensor is active]]
dev:18962022-09-13 01:05:26.060 pm infoX's Z-Wave Motion Sensor is active
dev:18962022-09-13 01:05:26.059 pm debugNotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 01:01:17.026 pm debugparsed 'zw device: 3B, command: 7105, payload: 00 00 00 FF 07 00 00 00 , isMulticast: false' to [[name:motion, value:inactive, descriptionText:X's Z-Wave Motion Sensor is inactive]]
dev:18962022-09-13 01:01:17.025 pm infoX's Z-Wave Motion Sensor is inactive
dev:18962022-09-13 01:01:17.021 pm debugNotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 12:57:05.756 pm debugparsed 'zw device: 3B, command: 7105, payload: 00 00 00 FF 07 08 00 00 , isMulticast: false' to [[name:motion, value:active, descriptionText:X's Z-Wave Motion Sensor is active]]
dev:18962022-09-13 12:57:05.755 pm infoX's Z-Wave Motion Sensor is active
dev:18962022-09-13 12:57:05.753 pm debugNotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 12:56:19.051 pm debugparsed 'zw device: 3B, command: 7105, payload: 00 00 00 FF 07 00 00 00 , isMulticast: false' to [[name:motion, value:inactive, descriptionText:X's Z-Wave Motion Sensor is inactive]]
dev:18962022-09-13 12:56:19.050 pm infoX's Z-Wave Motion Sensor is inactive
dev:18962022-09-13 12:56:19.043 pm debugNotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 12:51:07.947 pm debugparsed 'zw device: 3B, command: 8003, payload: 55 , isMulticast: false' to [[name:battery, unit:%, value:85, descriptionText:X's Z-Wave Motion Sensor battery is 85%], 8408]
dev:18962022-09-13 12:51:07.946 pm infoX's Z-Wave Motion Sensor battery is 85%
dev:18962022-09-13 12:51:07.305 pm debugparsed 'zw device: 3B, command: 8003, payload: 55 , isMulticast: false' to [[name:battery, unit:%, value:85, descriptionText:X's Z-Wave Motion Sensor battery is 85%], 8408]
dev:18962022-09-13 12:51:07.292 pm infoX's Z-Wave Motion Sensor battery is 85%
dev:18962022-09-13 12:51:06.991 pm debugparsed 'zw device: 3B, command: 7205, payload: 00 63 49 53 31 33 , isMulticast: false' to [8002]
dev:18962022-09-13 12:51:06.988 pm debugmsr: 0063-4953-3133
dev:18962022-09-13 12:51:03.125 pm warnconfigure...
dev:18962022-09-13 12:41:53.209 pm warndescription logging is: true
dev:18962022-09-13 12:41:53.208 pm warndebug logging is: true
dev:18962022-09-13 12:41:53.207 pm infoupdated...
Swapped to Device and it seems detected a couple active/inactives and then stopped, looks like it was then woken up by Hubitat
dev:18962022-09-13 02:17:11.497 pm infoZ-Wave command:WakeUpNotification()
dev:18962022-09-13 01:43:28.524 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 01:42:49.443 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:18962022-09-13 01:35:09.869 pm infofingerprint mfr:"0063", prod:"4953", deviceId:"3133", inClusters:"0x5E,0x86,0x72,0x59,0x85,0x73,0x71,0x84,0x80,0x30,0x70,0x7A,0x5A"
dev:18962022-09-13 01:35:09.866 pm debugbuilding fingerprint for unknown Z-Wave device...
dev:18962022-09-13 01:35:07.855 pm debugconfigure() called...
The logs would be much easier to read if it was a screenshot as I requested.
The wakeup is the device waking up on its own and telling the hub it is awake, in case the hub needs to send any pending configuration changes to it.
You may just be having issues with the zwave mesh itself. It is possible it sends a few alerts and then one gets delayed, so it starts trying to find a better route which would then delay any subsequent notifications, or they can just get lost all together if it has problems finding a good route to the hub.
May be good to just leave it on the generic driver and let it settle for a day.
Also, you could post a screenshot of your Settings > ZWave details page (may need multiple screenshots). And let us know which device is the one in question here.
1 Like
