Aqara TVOC sensor (VOCKQJK11LM) stops updating

[JDrewes]

What happened

I have 3 Aqara TVOC devices (VOCKQJK11LM). At first, all three worked fine for about a week. Then, no more updates were reported for one device through Z2M, a few days later also for another.
Re-pairing devices worked - but only at the cost of one of the other three randomly "falling of the network" (stopping to update and LQI being marked as unavailable). While working, LQI is usually from 80 to 110.

I have done many repairings (sometimes close to a zigbee router, sometimes at the coordinator), and I cannot get all three devices to keep updating at the same time for longer than a day. I don't know if they would all stop if I just waited long enough, or if they are somehow in conflict with each other?

Sometimes, when pressing the single button on the device for a long time to reconnect, it actually won't do so unless I do one of the following:
unplug/replug the zigbee coordinator and retart zigbee2mqtt
or
repair next to a different device (if it was connected through the router before, re-pair at the coordinator and vice versa).

I have a total of 8-9 devices connected, all Aqara (except for the coordinator, which is a CC2531 Sonoff-type USB stick). None of them have ever "gone off the network" or stopped reporting, only the TVOCs do that.

I found that changing the channel of my 2.4GHz wifi has changed things a little (it now takes a bit longer for the first device to stop updating), but the problem still persists. I don't believe it is simply related to interference because the other Aqara-zigbees have no problems.

Thanks for reading and thanks for Z2M in the first place!

What did you expect to happen

devices should keep updating

How to reproduce it (minimal and precise)

just pair and wait a few days

Debug info

Zigbee2MQTT version: 1.21.0 (commit #70891eec)
Adapter hardware: CC2531
Adapter firmware version: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"}'

[JDrewes]

See also discussion #9171 Aqara TVOC does not publish changes

[ocso]

I can confirm the same issue with my device.

[Fafitude]

J'ai le même problème avec une conbee 2 et en version 1.22.0.
Une idée du problème ?

[hb020]

Voting up here, same issue.
On CC2652RB from slaesh, with 88 average link quality.
Zigbee2MQTT version 1.21.2 commit: 4492212
Coordinator type zStack3x0
Coordinator revision 20210120
Frontend version 0.6.12.

Often, when the sensor is no longer reporting, it is also unresponsive to button presses. I need to do a long press for it to reboot, after which it gains contact again.

What seems to matter:

• setting Zigbee2MQTT to "enable join" keeps the connection a bit longer.
• the problem started when I moved the sensor from a position when I had an LQI average at 60, to a position where LQI average is better (88), and messed with reporting intervals (made them shorter). Will experiment some more.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[kovacsbalu]

I can confirm the same issue with my device also
I have slaesh CC2652 coordinator and 30+ device which works perfectly.

[Bobbyhax]

There is a firmware update for the VOCKQJK11LM. I updated from 0024 to 0026, that addresses this issue.
To get the update, I connected the sensor to a Aqara G2H camera, and sign in with a Aqara account in the app, then I could update (didn't get the update in Homekit mode)

After the update was done, I reconnected the sensor to my Z2M, and it works fine for now

[hb020]

now I'm not used to aqara/mijia/xiaomi devices in general, but that seems to indicate that the various other aqara hub devices (Camera G3, E1, M2, M1S, Camera G2H and Aqara Hub) could also work. But I don't have any. Anyone care to confirm? I feel more like getting a E1 or M2 if needed.

[gyver]

I have the same model and unfortunately the same problems with updates stopping very quickly. It is usually a matter of minutes or around 1 hour after adding it to the network before all updates stop.

I tried letting the network decide the router used to connect or forcing 3 different ones and get the same result : usually I get updates for some of the 3 main attributes (humidity, temperature, voc). The updated attributes are not always the same ones but until now there was never a try were all of them were reported and on all tries eventually all of them stop being updated altogether.

I don't have any Aqara hub/account to update the firmware like @Bobbyhax. Is there a workaround to get this device working or a way to update it without an Aqara hub/account ?

[gyver]

Note for reference : I use the git master version of zigbee2mqtt (recently updated, just checked and it is in sync with this repository) on pi4 with a pizigate+ managing 49 devices among them 15 routers from various manufacturers. The only non default configurations are for the pizigate, compatibility with homeassistant and choosing channel 25 to avoid nearby Wifi networks interference.

[MansM]

I wonder if it should be removed from the supported list or at least have a note... as the current situation has made it useless (I wouldn't have bought it if I knew about this issue before)

[Bobbyhax]

Here is an update: They day after the firmware updated, I lost connection to the sensor again, and I needed to press on the button to get it connected. I do not recommend this sensor, and would buy it again!
I read on Reddit that it is many others that have the same problems as we have. Someone suggests that the sensor have bad connection to the battery, and have placed cardboard between the battery and lid, and has solved the issue for them.

https://www.reddit.com/r/Aqara/comments/p03684/no_response_on_my_brand_new_tvoc_sensor/

[patrykwojtynski]

Unfortunately I also experience missing values after pairing (nothing in logs) and I can't find a way of updating it without Aqara hub.

I tried with TuYa ethernet hub, no luck so far.

[leoluk]

It should be possible for someone with an Aqara hub to sniff the upgrade and dump the OTA file. Would be greatly appreciated!

[Fafitude]

Bonjour, ça serait top en effet de pouvoir le mettre à jour par OTA via Z2M.
Est-ce possible ?

[gyver]

I've had what seemed initially like a totaly separate problem with a SonOff SNZB-02 temperature/humidity sensor. It suddenly stopped updating and I couldn't make it work by either :

• simple repair,
• let it sit 30 minutes with its battery out before pairing,
• smashing the button just after pairing while configuring,
• force-remove it before repairing
  (various workarounds found around the initial configuring failure)...

When I looked at the logs I saw problems with the reporting configuration of the temperature measure (I can dig up logs on demand if needed).

Until I found a procedure that worked, which is :

• force-remove it,
• restart zigbee2mqtt,
• repair the device.

Restarting zigbee2mqtt is mandatory so there's something done on restart that solves the configuration step of the interview to fail. I verified that adding the restart is the key by testing the procedure again with another SonOff SNZB-02 that was outside (and believed to have been damaged months ago by the weather as they are not rated for outside use) and it worked, this other device came back properly on the first try.

Finally I remembered my problems with the Aqara TVOC sensor and the force-remove, z2m restart, repair seems to work with it too ! At least it is working correctly for more than 9 hours now (at least 9x more uptime than anything I got before and with all values reported instead of at best 2 out of 3).

Hope it can help others and maybe point to at least one source of the problem.

[patrykwojtynski]

Thanks @gyver. I was sceptical about it but I gave it a try and followed your instructions right after I saw them.

And... It's working. What a surprise, so far 12h.

Previously I also added cardboard on battery because it felt loose, but it didn't change anything.

[gyver]

Unfortunately it might not have been a complete fix for me @patrykwojtynski. I just checked, my SonOff are still working as expected, but the Aqara TVOC didn't update for 9 hours now. It worked correctly for 16-17 hours.

I have a very small hope that it might be "normal" as the display shows nearly the same values as the one last reported (so it could be a case of nothing new to report, but 9 hours is very surprising and I know from another sensor that at least humidity and temperature had small changes over the last 9 hours only one meter from it in the same room). Current display vs last report 9 hours ago :

• 15 ppb on display instead of 16 ppb reported,
• 21.6°C both on display and reported,
• 51% humidity on display, 51.7% reported.

I'll let it sit like that to find out more.
At least if it is a fail the failure symptoms are totally different so there might be several underlying causes to our problems with the Aqara.

[Fafitude]

Bonjour,

quand ça se bloque comme dit ci dessus, j'appuie sur le bouton qui se trouve au dessus de l'appareil et c'est reparti pour plusieurs jours (ou heures ...).
Suite à la mise à la dernière mise à jour de Z2M, il ne captait plus rien. J'ai fait une manipulation similaire à Gyver et c'est reparti. Je suis vraiment déçu de cet appareil

[maximilian1001]

Bonjour,

quand ça se bloque comme dit ci dessus, j'appuie sur le bouton qui se trouve au dessus de l'appareil et c'est reparti pour plusieurs jours (ou heures ...). Suite à la mise à la dernière mise à jour de Z2M, il ne captait plus rien. J'ai fait une manipulation similaire à Gyver et c'est reparti. Je suis vraiment déçu de cet appareil

@Fafitude
Hello,

when it hangs as said above, I press the button on the top of the device and it's gone for several days (or hours ...).
Following the update of the last Z2M update, it no longer received anything. I did a similar manipulation to Gyver and it's off again. I am really disappointed with this device

[gyver]

I can confirm that pressing the button on top of the device unfreezes it in my case (after force unpair/z2m restart/pair which led to a freeze ~16 hours later).

When I pressed the button, it forced an e-ink display refresh (blinking full black/white for people not familiar with e-ink displays), and immediately refreshed the values both on display and to zigbee2mqtt.

Note that the TVOC values where largely overestimated just after the refresh (6000+ instead of the usual 15-100 range) and went down relatively quickly after : seems like a bug in the TVOC estimation on the device. One probable explanation for that bug is that it uses a low energy accumulator that it periodically fetch and reset (waking a microcontroller to do it that needs more energy and is sleeping most of the time), dividing the value by time spent since last evaluation. When the device freezes I suspect the clock freezes too but not the accumulator...

[gyver]

Follow-up: my sensor is working fine for 5 days straight now. So since the re-pairing procedure (see my earlier messages) I had to press the button on top one time over ~6 days to keep it working.

It is a bother to not know if/when it will fail to send updates again and need manual intervention but at least it has been useful for nearly a week.

[leoluk]

I bought two of these recently to give it a try, and they've been working perfectly for more than a week now! (with ZHA, but that shouldn't make much of a difference).

• The battery issue is real - both devices would randomly stop working and show "low battery" until I put a piece of cardboard on top of both batteries to apply more pressure.
• When pairing or reconfiguring, pressing the button repeatedly to make sure that reporting for all attributes was configured.

The temperature readings are accurate down to 0.1 °C, it's a very nice device.

[nicjansma]

I've had a similar issue with 3x VOCKQJK11LM devices not reliably reporting. After upgrading them to the 0026 firmware with a Aqara hub, I switched them back to my Conbee II.

At that point I could not reliably get them to send updates beyond the initial join. They might send a few updates, then nothing more, no matter how often I pushed the button or had them rejoin.

I've finally found one issue that may be affecting others, so I thought I'd share. In the Reporting tab in Z2M, I found the Min rep change interval for Temp and Humidity had been set to 100, which my understanding means 10*C.

After I changed these down to 0 (with a 60 second min interval), I'm now reliably getting data from them each minute. (I may bump them up to 5 mins or something soon).

I'm not sure if the Min rep change of 100 came from the factory, or firmware update to 0026, or something with Z2M, but all 3 devices had this issue and I had to fix it.

Might not be an issue for anyone else here! But since this pops up in Google for VOCKQJK11LM maybe others will see this and this could be a fix.

[gyver]

My device has now being working for 8 days with the same settings @nicjansma had before adjusting. So they are probably the defaults for at least our firmware versions.

I don't think the min rep change is in 1/10th of a °C or humidity %. The unit used is more probably 1/1000th to match the precision that can be selected up to 1/1000th. I'd guess this is something documented in the Zigbee protocol and common across all temp/humidity sensors.

@nicjansma : note that simply changing the values triggers a reconfiguration that might have helped unrelated to the values used (my problems were clearly linked to failures in the device reporting configuration), you can check this by reverting your change or trying other values to find out if you need these values or simply to change them once. If the min rep change is low, this probably means that the device will need to wake up more often and it will probably negatively affect the battery life so you might want to be less aggressive.

For reference, my device has :

• firmware build date : 20210204.
• firmware version : 2020?www. (seems mangled somehow with an unprintable character between 2020 and www.)

[Anonymenet77]

Hello,

I tried this method it worked for 5 days then nothing

force-remove it,
restart zigbee2mqtt,
repair the device.

[leroyloren]

v0.0.0_0027

http://cdn.aqara.com/cdn/opencloud-product/mainland/product-firmware/prd/lumi.airmonitor.acn01/20211223104612_OTA_lumi.airmonitor.acn01_0.0.0_0027_20211222_3BA1AA.ota

20211223104612_OTA_lumi.airmonitor.acn01_0.0.0_0027_20211222_3BA1AA.zip (rename ".ZIP" to ".OTA")

[ptr727]

Just hitting the button did not work for me, I repaired it, and then started OTA, and it is now updating.
Build date updated, but version remains the same, I assume this ok?

"dateCode": "20220222",
"softwareBuildID": "2020\u0000www.",

[selvent12]

How can I force OTA?
I managed once to start OTA, the file was uploaded to 100%, but the firmware version remained the same.
From that moment I can not start OTA again. I tried with button on the top site directly before hitting OTA, I also remove it from Zigbee2MQTT and rejoin it without success.

The real voltage of the batteries is 2,95V. The reported value by software is a mess : from 0% to 100%.
If I try to set some setting in "Reporting" every time I get an error.
The temperature and humidity is displayed ok for 24 hours in Home Assistant, but after that it will freeze.

The firmware date is : 20210204 and firmware version 2020www.

I use Sonoff zigbee 3.0 usb dongle plus with the latest firmware.

[JDrewes]

I second the question. From pushing the button to re-pairing to changing batteries to changing routers or connecting to the coordinator directly, I have not managed to get either of my 3 TVOCs to do an OTA, I always get "device did not respond to OTA request". Also Sonoff zigbee 3.0 usb, but not the latest firmware, and the same firmware version as the previous poster on the TVOCs.

On 05.06.22 16:03, selvent12 wrote: How can I force OTA? I managed once to start OTA, the file was uploaded to 100%, but the firmware version remained the same. From that moment I can not start OTA again. I tried with button on the top site directly before hitting OTA, I also remove it from Zigbee2MQTT and rejoin it without success. The real voltage of the batteries is 2,95V. The reported value by software is a mess : from 0% to 100%. If I try to set some setting in "Reporting" every time I get an error. The temperature and humidity is displayed ok for 24 hours in Home Assistant, but after that it will freeze. The firmware date is : 20210204 and firmware version 2020www. I use Sonoff zigbee 3.0 usb dongle plus with the latest firmware. — Reply to this email directly, view it on GitHub <#9454 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEJBXZIT6EXFJ2XOYCTWJVDVNRNNTANCNFSM5HFNCBHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Dr. Jan Drewes +86 182 13940202 ***@***.***

[hb020]

Make sure that:

1. you have a good, new battery that fits tight. Loose fitting batteries will not do. Uploading might work, but the flashing pulls more power and will fail if battery contact is bad.
2. you are next to the coordinator.
3. that the delays between following steps are all very short :
   • device full reset (pull batteries, let it bleed down for a minute, then put the batteries back in --and maybe pressing the button while doing so, forgot--)
   • re-pairing (to the coordinator)
   • the OTA command from zigbee2mqtt

In the zigbee2mqtt logs, look for messages about the device. You should see logs showing upload progress (after some time).

[leoluk]

Might be worth trying the update with a lab PSU hooked up to the battery clips instead of a battery

(I have yet to try this, but I see no reason why it wouldn't work with the right voltage)

[Fafitude]

Hello,
Since Z2M 1.25.2 update, my device is not working. I haven't heard back at all since it was working "not too badly" before.
Do you have the same problem ?
Thanks in advance.

[hb020]

Build date updated, but version remains the same, I assume this ok?

"dateCode": "20220222",
"softwareBuildID": "2020\u0000www.",

Yes, that is OK.

Trying out Z2M 1.25.2 now. Maybe you have this issue #12732 ?

[Triskelen]

http://cdn.aqara.com/cdn/opencloud-product/mainland/product-firmware/prd/lumi.airmonitor.acn01/20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota

20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota.zip (remove .zip)

says download link is invalid or damaged or corrupte

[hb020]

Both links work for me, and give the same file. For the second link, just remove the ".zip" from the file name. It is not a zip file.

[Triskelen]

okay got the file now i only need to figure out how to apply it

[hb020]

can be done straight from Z2M, no need to have downloaded it. If you use Z2M, look some posts above on how to do the steps. Timing and battery contact is important.

[Triskelen]

yeah got it to update now 👍

[NickJLange]

As a point of warning - So after flashing using this OTA firmware via ZHA / zigpy/ HA, the device is longer speaking the same language as zigpy and I'm seeing all sort of strange errors like:

2022-07-05 00:31:16 DEBUG (MainThread) [zigpy.device] Ignoring message (b'1c5f11d50a29012001') on cluster 64704: unknown endpoint or cluster id: 'No cluster ID 0xfcc0 on ($redacted, 1)'
2022-07-05 00:31:16 DEBUG (MainThread) [zigpy.device] Ignoring message (b'18d60a55003900009642') on cluster 12: unknown endpoint or cluster id: 'No cluster ID 0x000c on ($redacted, 1)'

Raw Tasmota can't decode either. Power drains / repairing to no avail. Reading a bit deeper - perhaps the developer changed all the codes for this rev and we need to wait for decoders to catch up? Anyone else seeing this (if there is a better place to discuss / raise - please advise - will target comment more to be a FYI)

[ptr727]

Installing a second TVOC, first one updated to 20220222, second one update available, and updated, but reports 20210204, and now says no update available.
Was the firmware version reverted from 20220222 to 20210204, or am I missing something?

New device, OTA reports no update available:

{
    "battery": 100,
    "device": {
        "applicationVersion": 29,
        "dateCode": "20210204",
        "friendlyName": "Aqara-Air-2A6E9E",
        "hardwareVersion": 1,
        "ieeeAddr": "0x54ef4410002a6e9e",
        "manufacturerID": 4447,
        "manufacturerName": "LUMI",
        "model": "VOCKQJK11LM",
        "networkAddress": 24353,
        "powerSource": "Battery",
        "softwareBuildID": "2020\u0000www.",
        "stackVersion": 2,
        "type": "EndDevice",
        "zclVersion": 3
    },
    "device_temperature": 24,
    "humidity": 70.56,
    "last_seen": "2022-07-18T03:54:40.525Z",
    "linkquality": 83,
    "temperature": 24.45,
    "update": {
        "state": "idle"
    },
    "update_available": false,
    "voc": 127,
    "voltage": 3003,
    "power_outage_count": 11
}

Older device with update applied:

{
    "battery": 100,
    "device_temperature": 24,
    "humidity": 70.01,
    "last_seen": "2022-07-18T04:21:20.835Z",
    "linkquality": 98,
    "power_outage_count": 34,
    "temperature": 24.13,
    "update": {
        "state": "idle"
    },
    "update_available": false,
    "voc": 73,
    "voltage": 3075,
    "device": {
        "applicationVersion": 24,
        "dateCode": "20220222",
        "friendlyName": "Aqara-Air-1A0E11",
        "hardwareVersion": 1,
        "ieeeAddr": "0x54ef4410001a0e11",
        "manufacturerID": 4447,
        "manufacturerName": "LUMI",
        "model": "VOCKQJK11LM",
        "networkAddress": 38064,
        "powerSource": "Battery",
        "softwareBuildID": "2020\u0000www.",
        "stackVersion": 2,
        "type": "EndDevice",
        "zclVersion": 3
    }
}

Log file:

Info 2022-07-18 07:25:12MQTT publish: topic 'zigbee2mqtt/Aqara-Air-2A6E9E', payload '{"battery":100,"device":{"applicationVersion":29,"dateCode":"20210204","friendlyName":"Aqara-Air-2A6E9E","hardwareVersion":1,"ieeeAddr":"0x54ef4410002a6e9e","manufacturerID":4447,"manufacturerName":"LUMI","model":"VOCKQJK11LM","networkAddress":24353,"powerSource":"Battery","softwareBuildID":"2020\u0000www.","stackVersion":2,"type":"EndDevice","zclVersion":3},"device_temperature":24,"humidity":71.11,"last_seen":"2022-07-18T14:25:09.476Z","linkquality":76,"power_outage_count":11,"temperature":24.08,"update":{"state":"idle"},"update_available":false,"voc":31,"voltage":3170}'
Info 2022-07-18 07:25:12MQTT publish: topic 'zigbee2mqtt/Aqara-Air-2A6E9E', payload '{"battery":100,"device":{"applicationVersion":29,"dateCode":"20210204","friendlyName":"Aqara-Air-2A6E9E","hardwareVersion":1,"ieeeAddr":"0x54ef4410002a6e9e","manufacturerID":4447,"manufacturerName":"LUMI","model":"VOCKQJK11LM","networkAddress":24353,"powerSource":"Battery","softwareBuildID":"2020\u0000www.","stackVersion":2,"type":"EndDevice","zclVersion":3},"device_temperature":24,"humidity":72.16,"last_seen":"2022-07-18T14:25:09.483Z","linkquality":76,"power_outage_count":11,"temperature":24.26,"update":{"state":"idle"},"update_available":false,"voc":31,"voltage":3170}'
Info 2022-07-18 07:25:13Checking if update available for 'Aqara-Air-2A6E9E'
Info 2022-07-18 07:25:13MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Checking if update available for 'Aqara-Air-2A6E9E'","meta":{"device":"Aqara-Air-2A6E9E","status":"checking_if_available"},"type":"ota_update"}'
Info 2022-07-18 07:25:13MQTT publish: topic 'zigbee2mqtt/Aqara-Air-2A6E9E', payload '{"battery":100,"device":{"applicationVersion":29,"dateCode":"20210204","friendlyName":"Aqara-Air-2A6E9E","hardwareVersion":1,"ieeeAddr":"0x54ef4410002a6e9e","manufacturerID":4447,"manufacturerName":"LUMI","model":"VOCKQJK11LM","networkAddress":24353,"powerSource":"Battery","softwareBuildID":"2020\u0000www.","stackVersion":2,"type":"EndDevice","zclVersion":3},"device_temperature":24,"humidity":72.16,"last_seen":"2022-07-18T14:25:10.786Z","linkquality":80,"power_outage_count":11,"temperature":24.26,"update":{"state":"idle"},"update_available":false,"voc":31,"voltage":3170}'
Info 2022-07-18 07:25:13No update available for 'Aqara-Air-2A6E9E'
Info 2022-07-18 07:25:13MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"No update available for 'Aqara-Air-2A6E9E'","meta":{"device":"Aqara-Air-2A6E9E","status":"not_available"},"type":"ota_update"}'
Info 2022-07-18 07:25:13MQTT publish: topic 'zigbee2mqtt/Aqara-Air-2A6E9E', payload '{"battery":100,"device":{"applicationVersion":29,"dateCode":"20210204","friendlyName":"Aqara-Air-2A6E9E","hardwareVersion":1,"ieeeAddr":"0x54ef4410002a6e9e","manufacturerID":4447,"manufacturerName":"LUMI","model":"VOCKQJK11LM","networkAddress":24353,"powerSource":"Battery","softwareBuildID":"2020\u0000www.","stackVersion":2,"type":"EndDevice","zclVersion":3},"device_temperature":24,"humidity":72.16,"last_seen":"2022-07-18T14:25:10.786Z","linkquality":80,"power_outage_count":11,"temperature":24.26,"update":{"state":"idle"},"update_available":false,"voc":31,"voltage":3170}'
Info 2022-07-18 07:25:13MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"Aqara-Air-2A6E9E","updateAvailable":false},"status":"ok","transaction":"9dbj2-1"}'

Looking at the OTA images, looks like update 29 is not listed, just 27?
Search for lumi.airmonitor.acn01 at images:
https://github.com/Koenkk/zigbee-OTA/blob/master/images/Xiaomi/20211223104612_OTA_lumi.airmonitor.acn01_0.0.0_0027_20211222_3BA1AA.ota

Expecting to find v29 per Koenkk/zigbee-OTA#86

From index.json:

    {
        "fileVersion": 29,
        "fileSize": 244350,
        "manufacturerCode": 4447,
        "imageType": 9480,
        "sha512": "6810b06a486f7689c87186e593dfdd6f5e0900ac9da154d515c6dd8881c6688ffbaac82e370940ebf133098f26c9a2df1aaf81b6fe0bc2815ee6ac2958b424d5",
        "modelId": "lumi.airmonitor.acn01",
        "url": "http://cdn.aqara.com/cdn/opencloud-product/mainland/product-firmware/prd/lumi.airmonitor.acn01/20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota"
    },

v29 seems to pull from Aqara not from images, and I verified that I can download it.

I created a local indiex file with the OTA file local, and it still reports no update:

debug 2022-07-18 13:02:02: Got OTA request '{"fieldControl":0,"manufacturerCode":4447,"imageType":9480,"fileVersion":29}'
debug 2022-07-18 13:02:02: ZigbeeOTA: downloaded main index
debug 2022-07-18 13:02:02: ZigbeeOTA: Loading override index /app/data/ota_index.json
debug 2022-07-18 13:02:02: ZigbeeOTA: getting local firmware file /app/data/20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota
debug 2022-07-18 13:02:02: Is new image available for '0x54ef4410002a6e9e', current '{"fieldControl":0,"manufacturerCode":4447,"imageType":9480,"fileVersion":29}', latest meta '{"fileVersion":29,"url":"20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota"}'
debug 2022-07-18 13:02:02: Update available for '0x54ef4410002a6e9e': NO

It seems to me that the OTA process believes the device is on 29, but the device firmware build date did not change.
Any ideas?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[ptr727]

@leroyloren

http://cdn.aqara.com/cdn/opencloud-product/mainland/product-firmware/prd/lumi.airmonitor.acn01/20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota

20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota.zip (remove .zip)

How do you capture the OTA information?
I have configured a CC2531 sniffer, and I'd like to learn how to capture OTA, and also how to capture changing degF to degC as can be done with hub app.
E.g. what channel does hub work on, do you sniff network traffic or zigbee traffic for OTA?

[leroyloren]

Need to sniff network traffic from Aqara Hub, not Zigbee.

[ptr727]

Ok, I can try that, I assume it is not SSL, or are you intercepting SSL?

[leroyloren]

Yes, it's HTTP.

[psi-4ward]

Any news her? I've to reset my device every week ;(

Is new image available for '0x54ef4410004ca3bc', current 
{
  "fieldControl":0,
  "manufacturerCode":4447,
  "imageType":9480,
  "fileVersion":29
}
latest meta {
  "fileVersion":29,
  "fileSize":244350,
  "url":"https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota",
  "sha512":"6810b06a486f7689c87186e593dfdd6f5e0900ac9da154d515c6dd8881c6688ffbaac82e370940ebf133098f26c9a2df1aaf81b6fe0bc2815ee6ac2958b424d5"
}

Update available for '0x54ef4410004ca3bc': NO

[ptr727]

I run 29 20220222 on 7 devices, upgraded from 27, then replaced battery as update drains battery, no issues, maybe something else?

[liquidbrains]

Firmware build date: 20220222
Firmware version: 2020�www.

Above firmware hangs. I have to remove the battery to get it to work again

[elupus]

Anybody that have run the TVOCs with official aqara hubs? Do they work without hang there?

[freeDom-]

I bought two of these recently to give it a try, and they've been working perfectly for more than a week now! (with ZHA, but that shouldn't make much of a difference).

* The battery issue is real - both devices would randomly stop working and show "low battery" until I put a piece of cardboard on top of both batteries to apply more pressure.

* When pairing or reconfiguring, pressing the button repeatedly to make sure that reporting for all attributes was configured.

The temperature readings are accurate down to 0.1 °C, it's a very nice device.

I can confirm that this also did the trick for me.
I just bought my device a weeks ago and initially it stopped updating and had a weird behavior.
The device reported low batteries and I realized that the batteries were kind of loose and almost falling out by themself when opening the device.
I managed to fix the problem (so far) by putting some cardboard behind the batteries to increase pressure.
At the point of writing the device is working for 6 days without issues. I will update if I encounter any more problems.

Update: Running for 7 month now without any problems... Thanks to the cardboard!

[Stawrit]

https://smarthomescene.com/guides/how-to-setup-zigbee2mqtt-local-ota-index/

Is it not possible to update OTA with the steps in this link? How can I update the OTA file with zigbee2mqtt? Is there a tutorial page for this? I would be very grateful if you could guide me.

[diegoflyer]

I've had a similar issue with 3x VOCKQJK11LM devices not reliably reporting. After upgrading them to the 0026 firmware with a Aqara hub, I switched them back to my Conbee II.

At that point I could not reliably get them to send updates beyond the initial join. They might send a few updates, then nothing more, no matter how often I pushed the button or had them rejoin.

I've finally found one issue that may be affecting others, so I thought I'd share. In the Reporting tab in Z2M, I found the Min rep change interval for Temp and Humidity had been set to 100, which my understanding means 10*C.

After I changed these down to 0 (with a 60 second min interval), I'm now reliably getting data from them each minute. (I may bump them up to 5 mins or something soon).

I'm not sure if the Min rep change of 100 came from the factory, or firmware update to 0026, or something with Z2M, but all 3 devices had this issue and I had to fix it.

Might not be an issue for anyone else here! But since this pops up in Google for VOCKQJK11LM maybe others will see this and this could be a fix.

Hi!
how have you changed the data? If I try to change them I have always an error: