Thanks for the reply! That driver unfortunately does not seem to work with this wired switch
Hi guys,
I know Markus is not around anymore, but maybe someone has the answer.
My correctly working Xiaomi plug is generating the following log every seven minutes;
dev:7722021-10-17 13:15:31.140 warnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 274901FCC082F700413D6410000328129839000000009539DA10774296390080134597390000000005210D009A201008211601072700000000000000000921000A0B20009B1001, dni: 2749, endpoint: 01, cluster: FCC0, size: 82, attrId: 00F7, encoding: 41, command: 0A, value: 3D6410000328129839000000009539DA10774296390080134597390000000005210D009A201008211601072700000000000000000921000A0B20009B1001 | msgMap:[raw:274901FCC082F700413D6410000328129839000000009539DA10774296390080134597390000000005210D009A201008211601072700000000000000000921000A0B20009B1001, dni:2749, endpoint:01, cluster:FCC0, size:82, attrId:00F7, encoding:41, command:0A, value:6410000328129839000000009539DA10774296390080134597390000000005210D009A201008211601072700000000000000000921000A0B20009B1001, clusterInt:64704, attrInt:247]
Any idea of what this may be and how to solve or avoid it?
ignore that
Done! Hahaha!
1 Like
Hi Guys,
anyone can tell if MCCGQ14LM ( model: lumi.magnet.acn001 ) will be supported? This is newer Aqara sensor that replaces older MCCGQ11LM. It seems to be supported by Zigbee2MQTT for HA etc. link
Thanks
Marku
I'm new to code import and would like to use this for my Aqara Mini Button.
I'm getting this error. Can you help?
Thanks!
You are in "Apps Code," but this is a driver and needs to be in "Drivers Code" instead.
5 Likes
I can't tell you how many times I've done this... 
4 Likes
I've been using this driver from Marcus for a few months now and it works for my temp/humidity sensors better than any others I've tried. I read in post Marcus is no long on this forum, not sure what that means?
Never the less, I was hoping that someone on here could help with my request.
The only problem I experience is sometimes out of the blue, the sensors seem to through out a false reading, then less than a second later return to normal readings. See log image below where the temperature reads 30.00 and returns:
I was wondering if there could be a max/min temperature range setting added so that anything below or above range would be ignored?
Thanks,
Stephen
Enter in the driver code, find zigbee_sensor_parseSendTemperatureEvent function and change the following code line with the values you need:
if(tRaw >= -50 && tRaw < 100) {
It is also opportune to take into consideration the warning I found in the Markus's code:
"Incorrect temperature received from the sensor ($tRaw), it is probably time to change batteries!"
all above should work. It should, not necessarily It Will.
You could also add two min/max parameters instead of raw builtin numbers...
3 Likes
@roberto Thanks for the insight, however that did not work for me. When I changed the parameters to a range between 50 and 90, I kept getting that warning message.
"Incorrect temperature received from the sensor it is probably time to change batteries!"
When I reverted the change to -50,100 it started responding with temperature readings again.
As 30 F degrees are out of 50-90 range, the driver correctly prompt you back with that warning, as It matches the "else" branch of the range check.
If you want filter "dropout" values that are supposed to be fault (because are abnormally different from previous values ) you must keep last value, compare with the new value and decide what to do (e.g. discharge It)
Otherwise if you want simply skip values out of your range, you have to comment also the code line with the log function call.
Hope It can help
The readings before the change were a consistent 70-73 degrees, the extremely abnormal 30 is scarce. So, for it to had occurred the moment I altered the code would had been highly unlikely. Also, it no longer posted any temperature readings for hours after. As well, there is another DHT Aqara sensor which does not have the problem and it too showed in logs with warning message when the driver was changed and no longer posted any temp readings for hours after.
Hi - I just installed an Opple WXCJKG13LM switch using this driver. I was able to pair it, but after clicking Initialize it shows as not present, and the driver does not respond to any button presses. I installed a child device for one of the switches, and that also does not respond. No battery level is shown either. Clicking Refresh, clicking the button on the back of the switch or double-clicking same do not help.
Is there a trick to getting these wireless switches working ?
Thanks
It seems the pairing process was not completed. Make sure you keep the device awake until you can finalize the configuration by short pressing the reset button.
I have a few of those Opple buttons & have experienced the same. It often takes several tries before they pair completely but will do so eventually.
Hi All,
I have the QBKG24LM with netural double rocker switch, I am able to pair the switch with hubitat but no driver is able to turn off and on.
The error in the log show, user_driver_waytotheweb_Xiaomi_Aqara_Mijia_Sensors_and_Switches_572.push() is applicable for argument types
Am i doing something wrong?
Will these Aqara motion and leak sensor drivers work for Iris V2 motion sensors and smartthings leak sensors? I am looking for generic drivers with presence for generic motion and water leak sensors, and wondering if these will work for that purpose
Doubt it.
1 Like
I tried it out for a couple Iris motion sensors and smartthings leak dot and it seem to be working. Are there any disadvantages in using these drivers for non Aqara devices?
