Hi!
I have this recurrent erro in the log of my devices Zooz ZSE18, The device work, but this recurrent erro is not good. Can you review the native drive inside the Hubitat and solve the problem?
dev:18532025-05-28 11:21:29.043 PMerror
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: zoozMotionSensorZSE18.recoveryEvent() is applicable for argument types: () values: [] (method recoveryEvent)
Thanks.
Sounds like you might have a scheduled job left over from another driver?
You can check the Scheduled Jobs tabs on the device page to confirm.
Then you can go to the main Logs page (on left side bar), then Scheduled Jobs.
Find that job in the lists and delete it.
Hi!
The activities scheduled on the device are, I believe, from apps that monitor devices, such as Device Health Status (@kkossev ) and Hubitat Z-Wave Mesh Details (@tfletcher61 .
And that for the Zooz ZSE18 device, they generate this error.
2025-05-29 09:08:18.037 AMerror
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: zoozMotionSensorZSE18.recoveryEvent() is applicable for argument types: () values: [] (method recoveryEvent)
dev:5462025-05-29 09:08:03.044 AMerror
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: zoozMotionSensorZSE18.recoveryEvent() is applicable for argument types: () values: [] (method recoveryEvent)
We could think that it is a problem with the apps, but I disagree if these apps apply their validation task to ALL devices (I have over 300, of various types Z-Wave and Zigbee), and not exclusively to the Zooz ZSE18, which is the only one that generates the error log.
Therefore, I understand that this should be the focus of the work: reviewing the behavior of this drive so that it does not generate this error, which, as I mentioned, does not happen with other devices.
Thank you.
If the apps are creating those scheduled jobs then they would only work with drivers specially designed to work with them. Those are not standard functions that system drivers or any custom drivers are expected to have. I am not even sure if apps can create scheduled jobs on devices. I still suspect those jobs were created by a different driver, not an app.
Do other devices you are using in those apps have these same scheduled jobs?
My driver does not have any of those functions so all those scheduled jobs will throw errors. If you want the errors to stop you need to remove them as I detailed above.
Hi Jeff,
As I mentioned, I have a large number of devices installed, including other types of motion sensors from other brands, other devices such as contacts, relays, switches, buttons, all accompanied by these two apps to report status, whether they are failing, and their characteristics, and only the Zooz ZSE18 shows this error in the log.
Importantly, even with the error, the devices work perfectly.
Thanks
Ok well not sure what else you want me to tell you. I explained it all above. What I stated is facts. You can chose to fix it or you can chose to keep having the errors in your logs.
You also did not answer this simple question
You should just remove those scheduled jobs as described above. IF THEY ARE REQUIRED, they will be recreated.
Errors will go away.
Hi, I understand your comment @TArman, and removing this schedule that was created by some app is indeed a way to avoid the error message.
However, this is one of the things I don't like about Hubitat's development: errors are ignored. If they don't affect anything, they are not addressed. To me, this shows a disregard for the quality of the solution's code.
An error is an error, and it must be addressed.
So I would like the Hubitat developers to consider this situation and fix the native drive for the Zooz ZSE18.
Yes, by you, using one of the above methods. This is not a problem with the platform or your current driver, and it's completely unrelated to any apps you're using. There is nothing the platform can do about it (at least that wouldn't break legitimate uses). It is something a previous driver did that you will need to undo.
It is also worth noting that the only effect of this "error" is the log entry itself, so it's not really a big problem other than that (this kind of thing is just incredibly helpful to have if you're developing a driver, or things like typos would take much longer to figure out) -- but the solution is easy if it bothers you as it does many.
Confusingly, it also sounds now like you’re using the system driver and not the custom driver whose topic you posted in. But the solution is the same regardless.
I have 5 ZSE18 devices, and I cannot reproduce the error you have posted. The error must be related to something else on the system. The device driver itself does not seem to create any scheduled tasks if it's own, therefore it is not responsible for the scheduled task or the error that is being caused.
There are 2 possible issues:
you have tried multiple device drivers for this device without clearing out the previous drivers scheduled jobs between driver changes, and those jobs are still running but this driver didn't create them or understand what to do with them.
one of the apps you are using to monitor the device is trying to perform an action on the device that it isn't designed to deal with.
I have 13 of the LR variety. They've been great.
Thank you all for your interest in helping. I think the issue is that I am using the native Zooz Motion Sensor ZSE18 drive, and it seems that you are already using an upgraded drive.
Is that what is happening? If so, could you please provide me with the link to download the drive?
Thank you.
No. What is happening is that you used a different driver the past and need to perform one of the solutions above if you want the error to stop appearing. If you know the exact driver you use when this began (the only ones I can think of with a job name like this are Zigbee, which you shouldn't use with these, but any developer can choose any name, so there are no constraints on what this could have been), switching back to it can help, but if the built-in driver meets your needs, I'd suggest the above instead. It will also be much easier since you won't have to remember or guess (or use the wrong driver if you did the past).
Note that the driver linked to in the post just above mine does not use this scheduled job and so will not address the issue, either. You will need to do what has been offered as the solution above with either this or the built-in driver.
Logs:
dev:18542025-06-04 10:37:59.557 AMinfo
MBathroom Jr motion is active
dev:18542025-06-04 10:37:59.553 AMdebug
Parse: zw device: B7, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:18542025-06-04 10:37:51.064 AMerror
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_custom_Zooz_Motion_Sensor_ZSE18_Custom_2361.deviceHealthCheck() is applicable for argument types: () values: [] (method deviceHealthCheck)
dev:18542025-06-04 10:35:39.375 AMinfo
Refreshing MBathroom Jr
dev:18542025-06-04 10:35:39.369 AMinfo
Driver Zooz Motion Sensor ZSE18 Custom version 1.0.7 initialized
dev:18542025-06-04 10:35:39.338 AMdebug
Device updated
Change the drive, but happened 
Right, as mentioned above, there are only certain specific steps that will address this. Please perform those steps and follow up if the problem persists (but spoiler alert: it won't 
).
Here is one such post:
This will make the errors go away, it is a simple fix. Not sure why you refuse to do it?
If you cannot find the scheduled jobs using the above method, the other way to remove the scheduled jobs is to change the Type/Driver to "Device" and then run the command to remove all scheduled jobs. Then switch back to the system ZSE18 driver if thats what you want to use.
Run the command
Scheduled Jobs should now be blank
Okay, steps I took just now: I changed the device drive to Device, reset everything (variables, status, children), and then reinstalled the @jtp10181 drive. Now I don't see any errors. Below is the log.
dev:18542025-06-04 10:47:20.564 AMinfo
MBathroom Jr motion reset to inactive
dev:18542025-06-04 10:46:51.559 AMinfo
MBathroom Jr battery is 100%
dev:18542025-06-04 10:46:51.551 AMdebug
Parse: zw device: B7, command: 8003, payload: 64 , isMulticast: false
dev:18542025-06-04 10:46:50.540 AMinfo
MBathroom Jr motion is active
dev:18542025-06-04 10:46:50.536 AMdebug
Parse: zw device: B7, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:18542025-06-04 10:46:49.805 AMinfo
MBathroom Jr motion is active
dev:18542025-06-04 10:46:49.802 AMdebug
Parse: zw device: B7, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:18542025-06-04 10:46:47.578 AMinfo
MBathroom Jr motion is active
dev:18542025-06-04 10:46:47.575 AMdebug
Parse: zw device: B7, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:18542025-06-04 10:46:19.369 AMinfo
Refreshing MBathroom Jr
dev:18542025-06-04 10:45:12.051 AMinfo
Z-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 1, eventParameter: [3], sequenceNumber: 0)
dev:18542025-06-04 10:45:09.073 AMinfo
Z-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 3, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
THANKS ALL!!!
Hi, I have a Zooz ZSE29 (ZSE29 Outdoor Motion Sensor FAQs - Zooz Support Center) outdoor motion sensor that has battery report and communication failure issues.
Is there a custom driver for this device?
I am currently using the native Zooz Outdoor Motion Sensor driver.
Thank you.
What is the specific problem with the battery reports?
And what are the "communication failure issues"? A driver isn't going to a fix a problem with your Z-Wave mesh, which seems like a more likely explanation for the problem, but more details about what it is would help someone give better advice.
The article you linked to in your post has a link for Hubitat directions, including an "advanced settings" driver you can download if you want to. I would suggest reading their documentation for more information.
But I also wouldn't start there, as the driver again is not a likely culprit for what sounds like the biggest problem here.
Download the Hubitat app
