Closed ptr727 closed 1 year ago
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
}
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
Some more info.
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.
First device state:
Second device state:
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)
Zigbee2MQTT version
1.26.0 commit: cd23aea
Adapter firmware version
20220219
Adapter
Tubes cc2652p2 zStack3x0
Debug log
z2mlog.log