-
Notifications
You must be signed in to change notification settings - Fork 505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Aqara TVOC Air Quality Monitor (VOCKQJK11LM) #5213
Conversation
been testing this for a while... today the VOC sensor seemed to have dropped out and is no longer receiving updates:
|
Same thing happened again, after restarting the unit. Roughly ~3 hours after reset:
|
Nevermind, it's actually working. Seems like the device does not push update out to Zigbee for a long long time unless values change significantly. |
@sieren Nice to see that they continue to implement that behavior. The multi sensors do the same. |
I've taken the liberty of making HomeKit support available for this unit including emulating it as an Eve Room 2 device, which was non-trivial:
|
@Mimiix im still wondering if the voc sensor needs additional polling though,compared to the temperature and humidity sensor in this unit it seems extremely slow to update. Notice especially the peaks. |
Hi guys! |
+1 looking forward for this. I try pairing them with Deconz (COnbee 2, latest version), but it won't work. I try pairing by holding down the button for a few seconds until a logo appears, then releasing and the small icon on the screen is supposedly looking fo ra network. |
@SwoopX I did some research about the lack of updates and according to Koenkk/zigbee2mqtt#6872 (comment) (I'm not a Zigbee2mqtt user) we also need to configure reporting for the VOC values for this device. Now sadly I'm not super familiar with the deCONZ codebase, but looking at what's happening for the DEVLCO Air Quality sensor (L2381 in bindings.cpp):
I assume we need something similar for the LUMI device?
which I've just added to my local build, pending verification. Not sure the attributeId is correct though, but maybe this helps? |
Regular attribute reporting, even with the newer Xiaomi devices, is still gambling I'm afraid. In the original device support issue, I already mentioned that it might be possible to influence the frequency of updates for the VOC values by changing/setting the attribute reporting values. For that, it's not really necessary to modify any code, it can be done in deconz GUI directly by double clicking on the attribute in question (given the cluster binding has been done previously, see here and below https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/How-to...#manually-bind-server-clusters). In case that should indeed work, just let me know. |
Cool! Thanks for the input @SwoopX . I'll give this a shot, but I side with your findings. The code hasnt really changed the reqporting frequency at all (it only seems to report with more frequency if there are massive changes). Overall the sensor seems far less reactive than an Eve Room for example. I still wonder why the Aqara App seems to report a lot more details. |
@SwoopX nice one, that did the trick! |
@SwoopX I tried it in a second home with another sensor, but had a hard time getting it up and running. |
@sieren Are you sure the reporting configuration is working? I'm just asking because in the initial device request, the data type for present value of the analog input cluster is float, and your code it's using uint16. Did the cherypicking already but haven't released the commit yet before confirmation. |
@SwoopX it is definitely not. Only after doing it through the UI. I couldn't find the key for float in any of the other exampel or the codebase, any pointers? happy to try it out. |
The corresponding data type would be What actually happens in the GUi I cannot tell you since this is deconz core functionality we don't have access to. |
Short question: on my side the sensor seems to be hanging. I mean the physical device - the values are stuck on screen and do not change (if i hold it in my hand the temperature does not increase). Do any of you experience this? The device becomes responsive again if i press the physical button for about 1-2 seconds. Is there anything i need to do "to keep it awake" or is it just a broken unit? |
I think what you're describing is what @SwoopX and I have been discussing. |
@leonardpitzu Mines have exactly the same behavior. |
Can we please not turn this issue in a "me too" issue? There's some work on the device, so until the PR is fully merged and released keep it on-topic :) |
Thanks @Mimiix for intervening. I haven't had time to look into the proposed changes by @SwoopX yet and try them out on my local builds yet. |
Hi @sieren "config": { |
Seems to work, here is the sniffer log of the joining process: Network key: cccccccccccccccccccccccccccccccc Note the reporting starts even before bindings are created, later in DDF we might not even to have to specify them. |
thanks for all your work. i can see the devices now in conbee app. but it is not showing up in openhab for an import. |
@f04ly you need to re-pair them probably |
i did @Mimiix i think the openhab deconz binding also needs an update, but i dont know whether this is deconz job or openhab job. dont know |
If the RestAPI Shows them correctly, than this PR is correctly implemented. |
I am able to read out all data (except the correct battery percentage, but I get the battery voltage) manually. I have problems with getting the data regularly. As mentioned in this thread I tried to change the report interval/change, but I only get the temperature regularly. I only get Humidity and Air Quality when requesting it manually. I put in 60 (min interval) and 600 (max interval) for humidity and air quality. The reportable change is 1 for humidity. For air quality I am not able to set the change (after reading it out the field is always empty). Any suggestions? |
Im having the same issue as apper13 on 2.13.2. Ive reset the TVOC sensor and gone through the process a few times, Humidity is always reported, sometimes Temp comes through, other times not, but the AQ is always null. Mimiix link works to get all of sensor outputs listed in deCONZ, but doesn't seem to solve the reporting of the values. |
This is what we see with xiaomi sensors: they report every hour (somewhere around that I think?) or on large changes (0.5degree for the multisensor). I think this sensor is no different on that. |
If the sensor would report every hour this would be great. The problem is that it basically never reports humidity and air quality - only when requesting it via Deconz IDE manually. For Temperature frequent updates can be seen. |
You can change the reporting interval by going to the "Analog Input Cluster" in deconz GUI, then chose "Presented Value", write the following reporting values: Press "Write Config" and press down on the button of the TVOC device once. You should get "Writing done" as a message in deCON GUI. if not, wait a few seconds until the write failed and try again, first clicking on "Write" and then pressing the button on the device. |
You guys having issues might want to make sure the latest firmware is installed (26720700). Eventually, the missing TVOC reports are the result of an older firmware running. After upgrade, make sure to reset and re-pair the sensor. |
@SwoopX im guessing an Aqara hub is required to update the firmware? I didn't see any fw sources with a quick google search Updating the intervals as sieren posted above has helped send all of the sensor values through, although I'm seeing two issues...
|
@anciltech I believe @SwoopX meant the Conbee Firmware. |
Gotcha, just updated and battery is now showing, but is shown incorrectly as 1%. Issue 2 above has remained the same |
Updating firmware was a good hint. I have a ConBee I (are there reasons to go to ConBee II?) and updated from 26390500 to 26400500. For now I got everything (including battery which is already at 73% after 1 day ?!?!). I will test until tomorrow if I now get the data regularly. Thank you! |
The battery status was 100% the next day, so the 73% were wrong. Also the Humidity and Temperature are sent regularly. Still not regular updates of air quality. After three days by chance one update happened... As written I have the latest firmware and set the update interval to 60/3600/1. |
Not a big difference between conbee 1 and 2. |
I know how to update the firmware on the conbee, but where can I find the 2.13.02-beta GCF firmware file? |
Follow the link in my post above |
Thank you so much for your great work guys! Really looking forward to get these sensors set up. I'm running the latest FW on Conbee 2, but I can't seem to figure out how to update the version to 2.13.02-beta GCF. I'm running Hassos on RPi 3b+, latest core-2021.11.5, latest supervisor-2021.10.8. I tried through remote terminal, with the instructions @anciltech posted, but no luck. And not through the HA addon either, I think the FW updater in the GUI never worked as good, so I guess the beta version won't work there either. Grateful for any help! |
Hi guys, i have add my aqara tvoc sensor to the z2m but the homebridge give alweays this error, `28/07/2022, |
See #4704.