Hi guys.. I have several temperature sensors and I started to use them to control the heater at home. I noticed they report every 50-60 minutes, is there a way to short this time or to report on a temperature change?
thanks
They also report if there is a temperature change of 0.5C or 5% in RH change. If I remember right those are the values, there is an official document somewhere, but I've misplaced the link. They can't be changed.
3 Likes
That's my experience as well
1 Like
Hey everyone; I've noticed with my WXKG03LM wireless wall switches (the battery ones) that after a little while of not being used, the first (sometimes second and third) presses are not responded to properly. My log shows this:
dev:48 2020-06-25 11:28:52.449 debugTest WXKG03LM: Creating event [name:battery, value:97, unit:%, descriptionText:Battery level is 97% (3.045 Volts)]
dev:48 2020-06-25 11:28:52.444 infoTest WXKG03LM: Battery level is 97% (3.045 Volts)
dev:48 2020-06-25 11:28:52.439 debugTest WXKG03LM: Battery parse string = 1F0121E50B03281F0421A8430521C20006240100000000082109140A21D435
dev:48 2020-06-25 11:28:52.434 debugTest WXKG03LM: Message payload: 1F0121E50B03281F0421A8430521C20006240100000000082109140A21D435
dev:48 2020-06-25 11:28:52.429 debugTest WXKG03LM: Parsing message: read attr - raw: 772D0100004401FF421F0121E50B03281F0421A8430521C20006240100000000082109140A21D435, dni: 772D, endpoint: 01, cluster: 0000, size: 44, attrId: FF01, encoding: 42, command: 0A, value: 1F0121E50B03281F0421A8430521C20006240100000000082109140A21D435
dev:48 2020-06-25 11:28:51.133 errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 90 (parse)
Subsequent presses usually work okay:
app:24 2020-06-25 11:32:41.095 infoToggle Test Plug when Test WXKG03LM button 1 pushed Toggle
dev:48 2020-06-25 11:32:41.002 debugTest WXKG03LM: Creating event [name:pushed, value:1, isStateChange:true, descriptionText:Left button was pressed (Button 1 pushed)]
dev:48 2020-06-25 11:32:40.996 infoTest WXKG03LM: Left button was pressed (Button 1 pushed)
dev:48 2020-06-25 11:32:40.992 debugTest WXKG03LM: Message payload: 0001
dev:48 2020-06-25 11:32:40.988 debugTest WXKG03LM: Parsing message: read attr - raw: 772D0100120A5500210100, dni: 772D, endpoint: 01, cluster: 0012, size: 0A, attrId: 0055, encoding: 21, command: 0A, value: 0100
dev:48 2020-06-25 11:32:40.978 debugTest WXKG03LM: Data type of payload is little-endian; reversing byte order
Is this just the way of things with these Aqara battery devices?
Could be worth trying my driver instead, I do not have this issue. It is probably not solved only by changing driver, it is a very likely a mesh issue as well, but it can be improved on with the driver.
1 Like
Yes, or using HPM to install it.
2 Likes
Need to investigate HPM. It's on the list!
HPM is a well-written piece of software. If I used more community apps/drivers I would use it. I have written my own drivers for almost everything I use and my build-system do my installs/updates.
Don't forget to run Initialize after switching to my driver.
4 Likes
Yup, all done. It has passed the "still works after 10 minutes" test. 
3 Likes
Hi I have bought these Aqara Smart Led bulbs (lumi.light.aqcn02) a while back and have given up on them responding to the hubitat. As stated somewhere in the community I have chosen the Generic Zigbee CT Bulb (dev) as driver. In the dashboard I have tried the switch and the bulb option but none of them are able to switch the bulbs on or off let alone change the level. Do you have any other suggestions?
In the data section, does the endpoint display as 01? If not, that would explain your issues. Try pairing it closer to the hub and see if you can get it to display 01 there.
The command for on/off is the standard one to cluster 0x0006, so for on/off it should work with basically any generic driver sending that command. If the endpoint is null or undefined however, it will not work unless using a custom driver working around that issue. As for the dimming of this device it is not really that standard, it kind of is, so you should be able to make it to work with a generic driver as long as the endpoint is set properly when pairing, but I remember it having some limitations in range with generic drivers. I have a not complete and not really tested driver for these unreleased, not sure when I will release it, could be a while before I get around to it, but PM me if you want to try it.
My Aqara Motion Sensor doesn't report any illuminance.
It is 0 all the time even if I shine directly on the sensor.
Any ideas what can be wrong?
Mine only report when it detect a movement, then the illuminance will be reported. I think this is the expected behavior. Try to trigger a movement and see whether the illuminance get updated. I do not think it is continuously monitored.
What are you trying to do?
2 Likes
Yeah you are right. It detects illuminance only once when it detects movement and then the value of illuminance is stored until next movement detection.
Thanks 
I just realised that mine doesn't seem to have reported illuminance - ever. I checked in the Events tab and there aren't any illuminance figures at all. Anyone able to point me in the direction of what I should do to get it to report on this?
I noticed in the Device Details section that the model is reporting as null. Do I need to reinstall the driver?? Let me know what other info might be needed.
EDIT: model RTCGQ01LM
That’s the Mijia version, which doesn’t do illuminance. Only the Aqara version does.
Ah, that would explain it. Thanks.
EDIT: swapped it out for a spare Aqara one I had here, so I can now use it better in a lighting rule. Thanks for the heads up.
1 Like
Since the driver falls back to it being model RTCGQ01LM, re-pairing is not needed in this case. In general though, if the model is reported as null in any of these drivers, best is to re-pair the device WITHOUT first deleting the device. That way the code that needs to run on pairing is guaranteed to run, when relying on the right driver being found during pairing it can take to long before the driver is loaded and some installation steps can be skipped due to this. This is due to how the system works together with these devices, not anything that can be fixed in the driver, but the fix is easy, pair again. 
1 Like
