Error with New Aqara Zigbee Weather Sensor (WSDCGQ11LM) Driver

🛎️ Get Help Devices
1

I have 1 Aqara Temperature Sensor (WSDCGQ11LM) that works with the new driver but another that is throwing this error.

error: org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: aqaraZigbeeWeatherSensor.checkEventInterval() is applicable for argument types: () values: (method checkEventInterval)

Here is the Data they both have.

  • endpointId: 01
  • application: 03
  • driver: v1.0.1.1123
  • hasPressure: True
  • manufacturer:
  • model: lumi.weather
  • modelType: Aqara WSDCGQ11LM

I have tried readding it to the hub with the same results.

2

You must have previously been using a different driver with this device (and "re-adding" it must have just been re-pairing without deletion, keeping the same hub device). This is a scheduled job a third-party driver must have created that the built-in driver does not use. 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.
2 Likes
3

Could they change the device driver to "Device". Clear everything and then go back to the Aqara Sensor Driver?

1 Like
4

Yes, that older technique also works. (I find the above easier since there are no driver changes, but your preferences may vary. :slight_smile: )

2 Likes
5

I only suggested it because this method allows one to delete all the existing installation and state values.

6

Yeah, if you want to clear any values there that may have been set by a previous driver, that is still the way. However, the built-in Aqara Zigbee Weather Sensor driver does not make use of state, so in contrast to the issue above, there is no reason to care about anything the previous driver may have done there.

1 Like
7

I also used a community driver, the started rearranging the sensors and noticed they come up as aqara instead xiaomi. Also, on the first one i noticed it because it asked me about a treashold when to report temp changes. I did set it to lowest. For the rest i just changed the driver from their device page, but i see now they seem set to some default value that is too high for me. Now i get few changes on my graph instead of one every 10minutes or so.

Where can i set this up to avoid reading devices?

8

The community drivers typically provide much more advanced features. The stock drivers focus on the simplicity and the easy of use.

Was there any reason for changing the driver?

9

So, for the past 3 years my C5 hub freezes 24h after any platform update. And if not after an update, then after a week. I did not have much time over the years, but i tried in the last months to switch to Home Assistant and i found out that i am just used to thinking in a Hubitat way, so giving it a last chance.

To do that, i wanted to remove everything unofficial, and re-pair one device per type to see how it goes.

I did not expect to see the aqara driver, so when i confirmed it is official, i went for it.

So far it looks ok, the only thing i miss is those setting that seem to only be settable at initialization time.

Hence my question, if i don't want to recreate devices and change all the dashboards and automations, just to be able to set the temp sensors to trigger hubitat events everytime the sensor itself fires an event.

10

1000010928
10000109281000×600 35.6 KB

Here's an example, on the left i miss data because the hub had frozen up, on the right side you can see that the granularity went down since i switched to the official driver, and i believe that unless the temp changes by 0.25C, the event from the sensor is not fired as a hubitat event