Generic Zigbee Vibration?

@mike.maxwell Generic Zigbee Vibration? I didn't see one on the list, is there such a thing? I am just trying out a couple ThirdReality Vibration Sensors, they look pretty cool with DIP switches to set sensitivity and an alarm. AAA batteries for power. They joined right up to HE and showed up as "Device", but I don't see any driver to use with them. I tried the Generic Zigbee Motion Sensor (no temp) Driver and reports are working active / inactive. That should be fine to use eh?

Would be nice if other uses join it, it directs to a driver though, I left the fingerprint below.


Fingerprint...

dev:17892024-04-30 10:43:00.771 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0500,FFF1", outClusters:"0019", model:"3RVS01031Z", manufacturer:"Third Reality, Inc"

dev:17892024-04-30 10:42:59.767 AMtraceZCL version:03

dev:17892024-04-30 10:42:59.764 AMtraceSoftware Build Id:v1.00.40

dev:17892024-04-30 10:42:59.760 AMtraceModel:3RVS01031Z

dev:17892024-04-30 10:42:59.757 AMtraceManufacturer:Third Reality, Inc

dev:17892024-04-30 10:42:59.529 AMinfoZigbee parsed:[raw:4E0801FFF1280000290100010029E803020029490603002930F8, dni:4E08, endpoint:01, cluster:FFF1, size:28, attrId:0000, encoding:29, command:0A, value:0001, clusterInt:65521, attrInt:0, additionalAttrs:[[value:03E8, encoding:29, attrId:0001, consumedBytes:5, attrInt:1], [value:0649, encoding:29, attrId:0002, consumedBytes:5, attrInt:2], [value:F830, encoding:29, attrId:0003, consumedBytes:5, attrInt:3]]]

dev:17892024-04-30 10:42:59.379 AMdebuggetting info for unknown Zigbee device...

1 Like

I've had one of these going for about a year now, and mine works really awesome. Plus original batteries are still going strong -- I've been very pleased with this device.

The Hubitat setup instructions are in its accompanying manual -- as it suggests, the "Generic Zigbee Motion Sensor" driver is the correct choice for this device, although I use the "no temp" version too.

3 Likes

Thanks! That's what I was hoping, slowly changing my devices to regular AAA batteries and getting great life out of them. I'll admit I didn't read the manual, lol. Maybe the HE Team will add the fingerprint to the Generic Zigbee Motion Sensor driver. I am liking the TR line of sensors, they just work and are pretty cost effective. Now if we can only get the battery reporting working properly. Seems to be an issue across multiple sensors.

My vibration sensor seems to be reporting battery OK -- battery changes are rare, I'm currently at 66% with the batteries it came with. I've fortunately never had the "battery status off by an order of magnitude" issue with this device.

IIRC from the time I've it, it went from 100 down to 80-something, and then went to 66. So, a bit jagged, but totally good enough for me. Though I admit I rarely check battery status - I just rely on my low-battery notifications to get my attention.

Mine is set up on our shower head as one of the sensors used to trigger our bath fan (long story!), so it gets daily use -- it's been a completely reliable rockstar.

Third reality is sending me one of these for integration testing, I'll either asign it to generic contact of make a new driver for it, whichever makes more sense for the device.

4 Likes

Currently, the generic Motion (no temp) driver works like a champ.

3 Likes

Now that's a cool idea. I was toying with a humidity sensor but it was too delayed or it would go off with out the shower on.

Right on - I wanted to keep fan activation to showers only, so a humidity rise only triggers the fan if the vibration sensor is also active (either one alone won't do anything).

I used a Tuya vibration sensor initially and although it worked fine, Tuya stuff kinda skeeves me out in general, so I gave this 3R sensor a shot...

I thought its bulk would be an issue, but I just use a command strip to secure it on top of shower head, and it's held up perfectly fine there. The whole setup has well exceeded my expectations, no doubt.

3 Likes

I'm trying to use the "Better Laundry Monitor" with a vibration sensor.
I have the ThirdReality Vibration Sensors but currently with using a "generic motion" driver as mentioned, it does not show up as eligible to use in the app.
Anyone come up with a real driver that shows vibration?

Until Mike comes with a native HE driver, you can try the Tuya ZigBee Vibration Sensor (available for installation via HPM).

2 Likes

I can report that your driver does work with the ThirdReality Vibration Sensor.

1 Like

Is anyone using a sensor with three-axis values in an RM5 automation?

I am stuck in an attempt to understand what these acceleration values mean, the conversion of the raw data to something useful - as an example to determine whether a door is open or closed... ?

https://wiki.dfrobot.com/How_to_Use_a_Three-Axis_Accelerometer_for_Tilt_Sensing

I am trying to use the acceleration sensor data coming from TR sensor now ..

These are the debug logs as a result of multiple rotations +/- 90 degrees of the TR sensor placed on a table :

dev:51322024-05-17 00:33:10.619infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 83.6°, Phi = 4.1°, Theta = -4.9° Raw accelerometer XYZ axis values = 1078, 78, -93

dev:51322024-05-17 00:33:09.617infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 86.6°, Phi = 3.1°, Theta = -1.5° Raw accelerometer XYZ axis values = 1156, 62, -31

dev:51322024-05-17 00:33:08.612infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 64.2°, Phi = -17.4°, Theta = 18.4° Raw accelerometer XYZ axis values = 937, -312, 328

dev:51322024-05-17 00:33:07.460infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 77.7°, Phi = 5.7°, Theta = -10.9° Raw accelerometer XYZ axis values = 1375, 140, -265

dev:51322024-05-17 00:33:06.453infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 82.6°, Phi = 3.3°, Theta = 6.6° Raw accelerometer XYZ axis values = 1078, 62, 125

dev:51322024-05-17 00:33:05.145infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 87.5°, Phi = 0.8°, Theta = -2.4° Raw accelerometer XYZ axis values = 1093, 15, -46

dev:51322024-05-17 00:33:04.143infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 74.9°, Phi = 4.0°, Theta = -14.6° Raw accelerometer XYZ axis values = 1078, 78, -281

dev:51322024-05-17 00:33:03.142infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 87.1°, Phi = 1.6°, Theta = -2.4° Raw accelerometer XYZ axis values = 1109, 31, -46

dev:51322024-05-17 00:33:02.140infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 57.0°, Phi = 30.5°, Theta = -11.4° Raw accelerometer XYZ axis values = 593, 359, -140

dev:51322024-05-17 00:33:01.138infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 78.8°, Phi = -5.7°, Theta = 9.6° Raw accelerometer XYZ axis values = 921, -93, 156

dev:51322024-05-17 00:32:59.102infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 88.6°, Phi = 0.0°, Theta = -1.4° Raw accelerometer XYZ axis values = 1250, 0, -31

dev:51322024-05-17 00:32:58.097infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 86.4°, Phi = 3.6°, Theta = 0.0° Raw accelerometer XYZ axis values = 984, 62, 0

dev:51322024-05-17 00:32:56.424infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 56.6°, Phi = 20.7°, Theta = -24.9° Raw accelerometer XYZ axis values = 1515, 640, -765

dev:51322024-05-17 00:32:55.420infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 51.6°, Phi = -3.7°, Theta = -38.1° Raw accelerometer XYZ axis values = 953, -78, -750

dev:51322024-05-17 00:32:54.031infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 73.8°, Phi = -10.8°, Theta = -11.8° Raw accelerometer XYZ axis values = 875, -171, -187

dev:51322024-05-17 00:32:53.028infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 42.9°, Phi = 24.9°, Theta = -36.9° Raw accelerometer XYZ axis values = 531, 328, -468

dev:51322024-05-17 00:32:52.025infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 77.9°, Phi = 8.9°, Theta = -8.1° Raw accelerometer XYZ axis values = 1078, 171, -156

dev:51322024-05-17 00:32:51.023infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 76.8°, Phi = 4.4°, Theta = -12.5° Raw accelerometer XYZ axis values = 984, 78, -218

dev:51322024-05-17 00:32:50.030infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 81.6°, Phi = 5.9°, Theta = 5.9° Raw accelerometer XYZ axis values = 1500, 156, 156

dev:51322024-05-17 00:32:48.706infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 84.0°, Phi = -1.6°, Theta = -5.8° Raw accelerometer XYZ axis values = 1078, -31, -109

dev:51322024-05-17 00:32:47.704infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 68.3°, Phi = 19.5°, Theta = -9.1° Raw accelerometer XYZ axis values = 1562, 562, -265

dev:51322024-05-17 00:32:46.704infoThirdReality Vibration Sensor 3RVS01031Z: Calculated angles are Psi = 86.5°, Phi = 3.4°, Theta = -0.8° Raw accelerometer XYZ axis values = 1046, 62, -15


And these are the formulas used for converting the raw x,y,x data :

        BigDecimal psi = new BigDecimal(Math.atan(x.div(Math.sqrt(z * z + y * y))) * 180 / Math.PI).setScale(1, BigDecimal.ROUND_HALF_UP)
        BigDecimal phi = new BigDecimal(Math.atan(y.div(Math.sqrt(x * x + z * z))) * 180 / Math.PI).setScale(1, BigDecimal.ROUND_HALF_UP)
        BigDecimal theta = new BigDecimal(Math.atan(z.div(Math.sqrt(x * x + y * y))) * 180 / Math.PI).setScale(1, BigDecimal.ROUND_HALF_UP)

The results don't make much sense ... :frowning: