Look for this in the driver code. (Or similar)
case 0x03: // Temperature
values += [ Temperature : Integer.parseInt(dataPayload, 16) - 8 ] // Just a guess :)
The '-8' is by how much the temperature will be adjusted by.
If yours is showing -8 in the driver code, but on the device page it is reading 2 degrees low, change -8 to -6. Wait a short period and it should change by 2 degrees.
I'm pretty sure this is what I did. Give it a try.
Thanks @bobbles!!!
I will surely give this a go. Cheers
EDITED: do I have restart hubitat after the change? or just refresh the device should suffice?
EDITED AGAIN: it's working now! thanks
That's good.
The grey cells still have a bit of life in them. 
I'm considering buying the button. It seems like its this or the smartthings one. Can someone deeper in the Aqara world opine on whether its a box worth opening?
The Mijia buttons are nice. Inexpensive and seem to work fine without a compatible repeater if they’re close (within 20 feet or so) of the hub. 5 presses, plus hold.
The Aqara leak sensors I’ve never had a problem with dropping. The Mijia motion sensors seem to hold on longer, and although not impervious to dropping off, less prone to it.
All other Aqara and Miji devices have been problematic when paired directly to Hubitat Elevation, even with compatible repeaters. But when any of the Xiaomi Aqara or Mijia devices are joined to an Aqara or Mijia gateway, they are rock solid and never give me a moment of trouble.
Which driver do we use for the Aqara vibration sensor please?
There is a debug message that I think hardcoded somewhere in the driver, that shows up even if debug is off...
My Aqara leak sensor doesn't seem to know what it is in the Dashboard, am I using the right template? I installed the device driver for this as well as a door sensor which paired perfectly. I made sure it was set to the right driver in devices.
If this is a newly installed device, I think you'll need to trigger an event to give it a state. You do have the correct template. Just set the sensor on a damp paper towel or touch both contacts with wet fingers.
Hi spcat
Feedback as promised. I’ve got another two of these sensors fitted with LCD screen .
Something strange happened with my Blitzwolf not being able to join it to Hubitat despite many attempts and being done by others. Nevertheless, it appear that all these sensors should work with a Konke and Xiaomi community drivers. Also, as said by others and checked by myself the battery level will show up a few hours later. Nevertheless, I found these sensors slower in providing updates ( perhaps to save the battery) and not so accurate as the xiaomi square temperature humidity sensors ( I.e. without screen). Hence, I’ll end up using the non LCD version in most of the cases.
Hi Bogdan,
Thank you for the update! Too bad they weren't good enough, I really liked the fact that they have a screen. Hm, I use the round one from Xiaomi - Aquara line, works well too but I've no idea how accurate it is.
Hi Spcat
No worries. You shouldn’t give up if you need them because it is more likely that I may be doing something wrong since I’ve noticed there are a few people confirming that blitzwolf temperature humidity is working for them.
I personally, have a similar clone of the Blitzwolf one ( as per my previous post) which after some wait worked completely ( including battery status) with Konke driver as advised by others. However the most cost effective, robust, supposedly accurate ( nevertheless it can be calibrated via settings) was the square WSDCGQ11LM temperature/humidity/pressure sensor. So rather than having a visual indication ( which may deplete the batteries quicker) I was thinking to have rules to trigger fans or audio messages if some areas are too humid , cold or hot for instance). Most important, I can see that the square sensor appear to report more often (which I like this) compared with those one fitted with LCD screens.
Could I use the Xiaomi HUB YTC4014CN as repeater or Bridge?
No.
However, you can pair your Xiaomi sensors to the Xiaomi hub and then integrate that with HE.
Edit: lookup mi-connector
And they work brilliantly. 
Hi Bogdan,
I just thought it would be more convenient to have a screen. Didn't really consider the battery depletion rate. I've Grafana set up so the screen is not a necessity. Thanks, I'll check the "WSDCGQ11LM" out 
Any idea when the code for this will be available? It's one of the most affordable smart window treatments in the global market. I plan to have them all around my house. Hubitat driver would be a godsend...
Hi @veeceeoh
I have just had an Aqara motion sensor 'drop off' after only being re-paired earlier today.
It was not reporting motion or checking in.
When I wandered past the sensor the blue LED flashed quickly 3 times. The hub did report that it received a message from the device as it threw an error.
I'm just wondering if this is useful information as to what could be happening and whether it can be resolved.
The driver is : -
The error is this.
Thanks.
Vibration sensor - Cannot find “activityLevel” > or < on aqara sensor - driver limitation?
I need to automatically roll my blinds in when it gets to windy. The acceleration and movement is to sensitive so I need to get the blinds to roll back when the activity level goes above 120. However, I cannot find the > or < in the custom attribute (see picture).
Any advice on how to find this setting?
It looks like the activityLevel attribute is declared in the code as a string rather than a numeric type, so arithmetic operators are not available. That being said, from what I can see in the code, the sensor does indeed report numeric types for this (and the driver even converts them to an Integer when parsing). Until the actual maintainer of the driver has a chance to look at this, my suggestion in the meantime would be to edit the line in the driver that looks like this (on line 43 in the current version but may vary on others):
attribute "activityLevel", "String"
to look like this:
attribute "activityLevel", "Number"
This is assuming there isn't some other reason this is declared as a string. I don't have one of these devices and can't test for sure, but it looks like the assumption elsewhere is that this will always be an integer value from the device.
I don't know nearly as much about these as Keith does, but since you haven't received a reply yet, here's my take on this:
Download the Hubitat app
