I get reports in the logs as active then inactive. It almost appears as if it is sending an active followed almost immediately by an inactive, kind of like a square wave pulse. When the dryer is started the LED blinks. The device page shows active. But if you hit refresh it goes to inactive. If you tap on it a second time even if the dryer is running the LED will blink again.
So the driver, as it seems, is seeing a pulse which shows as active but how would the event know the dryer was finished if it never sends another inactive command when vibration stops?
It appears that the inactive command is sent at about 10 sec. after the device goes active. The dryer starts and the LED blinks. 10 sec. after the first blink there is another blink. I don't know what it is doing. These logs show it is sending the inactive based on the time I mentioned above.
dev:28032020-01-15 08:21:51.546 am infoAcceleration: inactive
dev:28032020-01-15 08:21:51.544 am traceBasicSet: BasicSet(value:0)
dev:28032020-01-15 08:21:51.542 am debugzwaveEvent(hubitat.zwave.commands.basicv1.BasicSet cmd)
dev:28032020-01-15 08:21:51.539 am debugLast Activity: 01/15/2020 08:21:41 AM
dev:28032020-01-15 08:21:51.532 am traceDescription: zw device: 96, command: 2001, payload: 00 , isMulticast: false
dev:28032020-01-15 08:21:51.530 am debugparse(String description)
dev:28032020-01-15 08:21:41.528 am debugrefresh()
dev:28032020-01-15 08:21:41.380 am traceNotificationReport3: NotificationReport(v1AlarmType:2, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:2, sequence:false, eventParametersLength:0, eventParameter:)
dev:28032020-01-15 08:21:41.376 am debugzwaveEvent(hubitat.zwave.commands.notificationv3.NotificationReport cmd)
dev:28032020-01-15 08:21:41.363 am infoAcceleration: active
I just saw this error in the log.
dev:28032020-01-15 07:39:04.203 am errorgroovy.lang.MissingMethodException: No signature of method: user_driver_codahq_hubitat_Monoprice_Shock_Sensor_1310.logsOff() is applicable for argument types: () values:  Possible solutions: notify() (logsOff)