Skip to content
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

Aqara TVOC sensor OTA completes but datecode not updating #13200

Closed
ptr727 opened this issue Jul 18, 2022 · 3 comments
Closed

Aqara TVOC sensor OTA completes but datecode not updating #13200

ptr727 opened this issue Jul 18, 2022 · 3 comments
Labels
problem Something isn't working stale Stale issues

Comments

@ptr727
Copy link

ptr727 commented Jul 18, 2022

What happened?

On 14 May 2022 I deployed an Aquara TVOC VOCKQJK11LM and updated the firmware using built in OTA to "dateCode": "20220222".

Yesterday (17 July 2022) I deployed a second VOCKQJK11LM, again did an OTA update, but this device still reports "dateCode": "20210204".

OTA reports no update available.

I removed and repaired the device, same.

I downloaded the OTA file and placed in local OTA index file, still reports no update.

wget --directory-prefix=/data/appdata/zigbee2mqtt/config 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
ota:
    zigbee_ota_override_index_location: ota_index.json
[
    {
        "url": "20220222202427_OTA_lumi.airmonitor.acn01_0.0.0_0029_20220222_17EC2C.ota"
    }
]
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

First device state:

{
    "battery": 100,
    "device_temperature": 25,
    "humidity": 69.86,
    "last_seen": "2022-07-18T19:54:05.517Z",
    "linkquality": 94,
    "power_outage_count": 34,
    "temperature": 25.65,
    "update": {
        "state": "idle"
    },
    "update_available": false,
    "voc": 135,
    "voltage": 3090,
    "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
    }
}

Second device state:

{
    "battery": 100,
    "device_temperature": 25,
    "humidity": 69.83,
    "last_seen": "2022-07-18T20:15:11.628Z",
    "linkquality": 54,
    "power_outage_count": 13,
    "temperature": 25.88,
    "update": {
        "state": "idle"
    },
    "update_available": false,
    "voc": 60,
    "voltage": 3145,
    "device": {
        "applicationVersion": 29,
        "dateCode": "20210204",
        "friendlyName": "Aqara-Air-2A6E9E",
        "hardwareVersion": 1,
        "ieeeAddr": "0x54ef4410002a6e9e",
        "manufacturerID": 4447,
        "manufacturerName": "LUMI",
        "model": "VOCKQJK11LM",
        "networkAddress": 21623,
        "powerSource": "Battery",
        "softwareBuildID": "2020\u0000www.",
        "stackVersion": 2,
        "type": "EndDevice",
        "zclVersion": 3
    }
}

I followed troubleshooting steps from here with no solution.

What did you expect to happen?

I expected both devices to update to "dateCode": "20220222", and both devices to behave the same.

How to reproduce it (minimal and precise)

  • Acquire VOCKQJK11LM.
  • Enable pairing in Z2M.
  • Pull battery isolation tabs from device.
  • Pair success.
  • Verify firmware date code.
  • Click device button to wake it.
  • Start OTA process.
  • Complete OTA.
  • Confirm firmware date code updated.

Zigbee2MQTT version

1.26.0 commit: cd23aea

Adapter firmware version

20220219

Adapter

Tubes cc2652p2 zStack3x0

Debug log

z2mlog.log

@ptr727 ptr727 added the problem Something isn't working label Jul 18, 2022
@ptr727
Copy link
Author

ptr727 commented Aug 8, 2022

I experimented and updated another new sensor using the M2 hub and the Aquara app.
As expected the datecode and application version updated.

"applicationVersion": 29,
"dateCode": "20220222",
{
    "battery": 0,
    "device": {
        "applicationVersion": 29,
        "dateCode": "20220222",
        "friendlyName": "Aqara-Air-2A6585",
        "hardwareVersion": 1,
        "ieeeAddr": "0x54ef4410002a6585",
        "manufacturerID": 4447,
        "manufacturerName": "LUMI",
        "model": "VOCKQJK11LM",
        "networkAddress": 1867,
        "powerSource": "Battery",
        "softwareBuildID": "2020\u0000www.",
        "stackVersion": 2,
        "type": "EndDevice",
        "zclVersion": 3
    },
    "device_temperature": 26,
    "humidity": 58.87,
    "last_seen": "2022-08-08T20:25:00.107Z",
    "linkquality": 65,
    "temperature": 26.92,
    "update": {
        "state": null
    },
    "update_available": null,
    "voc": 135,
    "voltage": 2795,
    "power_outage_count": 11
}

@github-actions
Copy link
Contributor

github-actions bot commented Sep 8, 2022

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

@github-actions github-actions bot added the stale Stale issues label Sep 8, 2022
@ptr727
Copy link
Author

ptr727 commented Sep 16, 2022

Some more info.

  • Datecode will only update after removing device from network, and then re-adding.
  • The application version never updates, stays on 24, vs. M2 hub updated devices show app version 29, matching firmware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests

1 participant