Aqara Contact Sensor error using new built in HE Driver

About a month ago, I switched the driver for my Aqara contact sensor to the new native built in Aqara driver. I just noticed that I'm getting hourly and sometimes more frequent error messages in the log for this device. What does this mean, and more importantly, how do I resolve it to stop the error from occuring?

Mike might be interested in this.... [edit] or not, per other comments below, so removing the ping. :slight_smile:

This is not a problem with the built-in driver; rather, you must have previously been using a different driver with this device. This is a scheduled job a third-party driver must have created that the built-in driver does not use (there is nothing in the built-in code that creates or handles this scheduled job).

It is harmless if you want to ignore, but to get rid of it, an easy way is:

  1. Go to Logs > Scheduled Jobs
  2. Find a job called "checkEventInterval" for this device (in the "App/Driver Name" column)
  3. Select the delete (trash can) icon in the "Actions" column for this job to remove it.
3 Likes

Looks like a Presence error with a Contact sensor, first thing to try is changing to the built-in Device driver and clearing everything.

Device

Then > Save Device > Configure

Click the Delete buttons:

Delete

And finally, restore the correct driver: > Save Device > Configure

Edit: Since it took so long for me actually post this. It looks like this is the hard way compared to Bert's... :wink:

1 Like

@bertabcd1234 Thank you!
I did as instructed. Will report back tomorrow if it has stopped.

1 Like

You can scroll to the bottom of the device page and look for any scheduled jobs.
If there are none then it's a good bet you've nailed it,

2 Likes

@bobbles :
The bottom of the device page lists a scheduled job. Handler name is "checkPresence" and it is scheduled to run in about 3 hours...

I didn't see you had two different errors in the log. You'll need the repeat this process for that job name, too.

1 Like

Yes, from the log I posted above it looks like it was also checking presence about once every 3 hours. I've done as directed.

1 Like