OTA fro lumi.sensor_smoke.acn03 v21

[nickgoh]

Extracted from Aqara Gateway during a live update for lumi.sensor_smoke.acn03.

Not yet tested via Zigbee2MQTT OTA.

[github-actions]

Merging this pull request will add these changes in a following commit:

diff --git a/index.json b/index.json
index 61d57df..0a68a75 100644
--- a/index.json
+++ b/index.json
@@ -8911,5 +8911,15 @@
     "manufacturerCode": 4447,
     "sha512": "783bc2f63337b6e4c62b2c344cb748ea56e67a05c731c72b942bb3ad45b791220b69513f79eba492e91526f55994006297f952f7b5a0470f07fcf1490334dee9",
     "otaHeaderString": "Aqara OTA Image"
+  },
+  {
+    "fileName": "lumi.sensor_smoke.acn03.ota",
+    "fileVersion": 21,
+    "fileSize": 226126,
+    "url": "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Lumi/lumi.sensor_smoke.acn03.ota",
+    "imageType": 9728,
+    "manufacturerCode": 4447,
+    "sha512": "f18deefc12bf8acd3994f7dffe38cb0e3b0e04547980fe1d02206070ec277704006adde5eb0f64ccc014754a23f25446cf1e41b983715c44292dd0ff3fc8a4b6",
+    "otaHeaderString": "OM15082-WIN-JN5180--ENCRYPTED000"
   }
 ]
\ No newline at end of file

[Koenkk]

Thanks!

[mrmaximas]

@Koenkk i have 4 lumi.sensor_smoke.acn03, 3 with build 17, 1 with build 19 but no update available. i always use latest dev.

something went wrong?

{"id":113,"type":"EndDevice","ieeeAddr":"0x54ef4410005066bb","nwkAddr":8022,"manufId":4447,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_smoke.acn03","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[0,1280,3,1],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"modelId":"lumi.sensor_smoke.acn03","appVersion":17,"swBuildId":"2019\u0000www.","dateCode":"20220617","serialNumber":"A00222SSW1BPA01865","manufacturerName":"LUMI","powerSource":3,"zclVersion":3,"stackVersion":2,"hwVersion":1}},"manuSpecificLumi":{"attributes":{"247":{"type":"Buffer","data":[1,33,227,11,3,40,25,4,33,168,67,5,33,26,0,6,36,1,0,0,0,0,8,33,17,1,10,33,39,2,12,32,1,102,32,3,103,32,1,104,33,168,0,160,33,0,0,161,32,0,162,32,0,163,32,0,164,32,0,165,32,1]},"294":0,"295":0,"314":0,"315":0,"316":0,"317":0,"331":1}},"ssIasZone":{"attributes":{"iasCieAddr":"0x00124b002a1aa3c4","zoneState":1}},"genPowerCfg":{"attributes":{"batteryVoltage":31}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":17,"stackVersion":2,"hwVersion":1,"dateCode":"20220617","swBuildId":"2019\u0000www.","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":332242049},"lastSeen":1760995952934,"checkinInterval":3600}

[Koenkk]

@mrmaximas could you provide the debug log when checking for an update for these devices?

See this on how to enable debug logging.

[mrmaximas]

@nickgoh Hello,
Did you rename the original file received from the Aqara hub?

[Koenkk]

The latest OTA in this repo is 17 so it's correct that no update is offered.

[2025-10-21 21:27:41.490] debug: 	zhc:ota: [0x54ef4410007a5329 | lumi.sensor_smoke.acn03] Checking latest image availability, current: {"fieldControl":0,"manufacturerCode":4447,"imageType":9728,"fileVersion":17}

To retrieve the 19 version see: https://www.zigbee2mqtt.io/advanced/more/tuya_xiaomi_ota_url.html

[mrmaximas]

@Koenkk Isn't the recently added image v21 for lumi.sensor_smoke.acn03? I have the same model with versions 17 and 19. Aqara does not offer version 19 or higher via hub for me.

[Koenkk]

@mrmaximas you are right, the OTA ended-up twice in the index, it's fixed now.

[mrmaximas]

@Koenkk 🙏🏻

[mrmaximas]

@Koenkk nevertheless, I was able to run the update only by creating a local OTA index.
It seems to me that there are still two entries in the current index, but refer to different versions, 17 and 21.

[
    {
    "fileName": "lumi.sensor_smoke.acn03.ota",
    "fileVersion": 21,
    "fileSize": 226126,
    "url": "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/images/Lumi/lumi.sensor_smoke.acn03.ota",
    "imageType": 9728,
    "manufacturerCode": 4447,
    "sha512": "f18deefc12bf8acd3994f7dffe38cb0e3b0e04547980fe1d02206070ec277704006adde5eb0f64ccc014754a23f25446cf1e41b983715c44292dd0ff3fc8a4b6",
    "otaHeaderString": "OM15082-WIN-JN5180--ENCRYPTED000",
    "modelId": "lumi.sensor_smoke.acn03"
  }
]

[Koenkk]

Whoops, fixed now.

[mrmaximas]

@Koenkk now looks good!

[msnjdev]

@Koenkk
The version v21 actually breaks my Aqara smoke detector... When going off, it only buzzers one time and then it is muted.

This isn't a Zigbee issue, as I tried it also without a Zigbee connection at it automatically mutes itself still.

@mrmaximas Did you ever tested your devices after the update? Does it also only buzzers one time and then it mutes itself?

[nickgoh]

@Koenkk The version v21 actually breaks my Aqara smoke detector... When going off, it only buzzers one time and then it is muted.

This isn't a Zigbee issue, as I tried it also without a Zigbee connection at it automatically mutes itself still.

@mrmaximas Did you ever tested your devices after the update? Does it also only buzzers one time and then it mutes itself?

@msnjdev, may I know how you triggered the alarm? Was it with smoke? I’d like to test the same method on my unit to check whether the issue can be replicated.

[mrmaximas]

@Koenkk The version v21 actually breaks my Aqara smoke detector... When going off, it only buzzers one time and then it is muted.

This isn't a Zigbee issue, as I tried it also without a Zigbee connection at it automatically mutes itself still.

@mrmaximas Did you ever tested your devices after the update? Does it also only buzzers one time and then it mutes itself?

@msnjdev Unfortunately, you are right. The sensor's behavior has changed, and this is a HUGE PROBLEM. After coming into contact with smoke, it sounds once and then goes silent with a flashing red light.
I tried to forcefully flash the old firmware, but unfortunately the sensor does not accept it. A temporary solution would be to automate the alarm, but the point of these sensors is their autonomy.

[mrmaximas]

@Koenkk please revert OTA for lumi.sensor_smoke.acn03 a.s.a.p.

[mrmaximas]

@Koenkk I attempted to roll back the firmware to the previous version. I created local index smoke.json:

[
    {
    "fileName": "20220718113235_OTA_lumi.sensor_smoke.acn03_0.0.0_0017_20220617_CB9276.ota",
    "fileVersion": 17,
    "fileSize": 222094,
    "url": "images/20220718113235_OTA_lumi.sensor_smoke.acn03_0.0.0_0017_20220617_CB9276.ota",
    "imageType": 9728,
    "manufacturerCode": 4447,
    "sha512": "d5a8e5c323acd99ceaf02ab061e7145dbcf2da028c9d73a6042d02536f0b8aaefbc798b9b47e8fb03345721c0231374c8654e3979e73b10ba51997ad9d41cf0a",
    "otaHeaderString": "OM15082-WIN-JN5180--ENCRYPTED000",
    "modelId": "lumi.sensor_smoke.acn03",
    "force": true
  },
]

I put the 20220718113235_OTA_lumi.sensor_smoke.acn03_0.0.0_0017_20220617_CB9276.ota in the zigbee2mqtt/data/images/ folder, restart z2m and then press update. z2m shows that there is firmware, but nothing happens. I sniffed the update attempt. Please check what went wrong. Z2M reports to sensor Ota No Image Available

OTA.pcapng.zip

[msnjdev]

@Koenkk The version v21 actually breaks my Aqara smoke detector... When going off, it only buzzers one time and then it is muted.
This isn't a Zigbee issue, as I tried it also without a Zigbee connection at it automatically mutes itself still.
@mrmaximas Did you ever tested your devices after the update? Does it also only buzzers one time and then it mutes itself?

@msnjdev, may I know how you triggered the alarm? Was it with smoke? I’d like to test the same method on my unit to check whether the issue can be replicated.

Yeah, I tripped the alarm with real smoke.

[msnjdev]

@Koenkk The version v21 actually breaks my Aqara smoke detector... When going off, it only buzzers one time and then it is muted.
This isn't a Zigbee issue, as I tried it also without a Zigbee connection at it automatically mutes itself still.
@mrmaximas Did you ever tested your devices after the update? Does it also only buzzers one time and then it mutes itself?

@msnjdev Unfortunately, you are right. The sensor's behavior has changed, and this is a HUGE PROBLEM. After coming into contact with smoke, it sounds once and then goes silent with a flashing red light. I tried to forcefully flash the old firmware, but unfortunately the sensor does not accept it. A temporary solution would be to automate the alarm, but the point of these sensors is their autonomy.

yeah, it is sadly not possible to downgrade the fw. I also tried to reflash the same fw, without any luck.

[mrmaximas]

@nickgoh It seems that this update has slightly broken our sensors. Are you experiencing the same behavior as us?

[nickgoh]

@mrmaximas I can confirm that I’m experiencing the same behaviour. My sensor was updated through the Aqara gateway. My test was done using vaping device smoke, so I cannot confirm whether heavier smoke would trigger differently. The Aqara gateway also shows that it's already on the latest firmware.

[mrmaximas]

@nickgoh thanks. I think you should write to Aqara support and request a corrected firmware update.
In which region is your Aqara account located where they push this version?
My test Aqara hub is in the China region, they did not push me this fw.

[msnjdev]

@mrmaximas I can confirm that I’m experiencing the same behaviour. My sensor was updated through the Aqara gateway. My test was done using vaping device smoke, so I cannot confirm whether heavier smoke would trigger differently. The Aqara gateway also shows that it's already on the latest firmware.

I was doing both. I tested it with vape smoke and normal smoke (by burning some 3Dprinter filament I've at home). For me, it mutes in both cases after one beep.

But am I understanding it correctly: You updated your sensor to version 21 over the official Aqara gateway and you have the same problem?
At least the version here on this repo isn't a wrong one and we can hope to get an update which fixes that issue (I was scared, when I found out, that we can't downgrad our sensors anymore. So I tought that the sensor will also reject a new version. But at least Aqara has made the update, so they also can fix it).

[mrmaximas]

@msnjdev I updated the fw from z2m repo.
The topic starter @nickgoh uploaded this fw to the z2m repo; he got it from the official Aqara channel.
Yesterday, I even took apart the sensor and found that it wouldn't be difficult to re-flash it, but the OTA file is encrypted and signed, so we have about zero chance to fix it with wires without the original .bin file.

[msnjdev]

@msnjdev I updated the fw from z2m repo. The topic starter @nickgoh uploaded this fw to the z2m repo; he got it from the official Aqara channel. ...

Alr, atleast that. I guess we need to ask the Aqara Support, if this is an issue OR if we are just stupid to create real smoke. I heard also that sometimes smoke detectors mutes themself, when there isn't enough smoke.

[mrmaximas]

@msnjdev I updated the fw from z2m repo. The topic starter @nickgoh uploaded this fw to the z2m repo; he got it from the official Aqara channel. ...

Alr, atleast that. I guess we need to ask the Aqara Support, if this is an issue OR if we are just stupid to create real smoke. I heard also that sometimes smoke detectors mutes themself, when there isn't enough smoke.

However, previously the sensor buzz continuously until the alarm/smoke was cleared.
Moreover, after a single alarm sound, if smoke hitting the sensor again it does not cause sensor activate; I can see this in zigbee traffic.

smoke.alarm.pcapng.zip

[msnjdev]

@msnjdev I updated the fw from z2m repo. The topic starter @nickgoh uploaded this fw to the z2m repo; he got it from the official Aqara channel. ...

Alr, atleast that. I guess we need to ask the Aqara Support, if this is an issue OR if we are just stupid to create real smoke. I heard also that sometimes smoke detectors mutes themself, when there isn't enough smoke.

However, previously the sensor buzz continuously until the alarm/smoke was cleared. Moreover, after a single alarm sound, if smoke hitting the sensor again it does not cause sensor activate; I can see this in zigbee traffic.

Fair enough, it should go off again when the smoke hits again.

[Koenkk]

Removed the OTA for now

[mrmaximas]

@nickgoh Have you tried contacting Aqara and reporting the issue? Also I asked which region your Aqara account is in, what was the full download URL that you grabbed, but you didn't answer. Thanks!

[nickgoh]

@nickgoh Have you tried contacting Aqara and reporting the issue? Also I asked which region your Aqara account is in, what was the full download URL that you grabbed, but you didn't answer. Thanks!

@mrmaximas I’m currently using the China region in the Aqara app, and the OTA file I extracted came directly from the Aqara gateway’s internal upgrade folder.(via telnet to Aqara Hub M2)

I’ve already contacted Aqara Support regarding this and am now waiting for their response.

[mrmaximas]

@nickgoh thanks for the answer. I also use the China region, but I haven't received that version. My Aqara hub is G2H.
Did they respond to you in any way? They replied a couple of hours ago to the email I sent over the weekend. I advise you to record a video and send it to Aqara Support. At least that's what they asked me to do. I recorded it and sent the link. The more reports about a problem, the more likely it is to be solved.

[mrmaximas]

@nickgoh Just in case, keep this sensor connected to the Aqara hub if they want to check it.

[nickgoh]

@mrmaximas Yes, they replied, but it was only a basic first-level support response. They did confirm that 0.0.0_0021 is the latest firmware. I’ve replied to them again, and hopefully the case will be escalated to their higher-level technical team.

[mrmaximas]

@mrmaximas Yes, they replied, but it was only a basic first-level support response. They did confirm that 0.0.0_0021 is the latest firmware. I’ve replied to them again, and hopefully the case will be escalated to their higher-level technical team.

I was a little luckier, they requested the video right away 😎
Aqara is very conservative; they strongly dislike their devices being used in third-party systems and may simply refuse to provide support. The unfortunate aspect is that it was difficult to identify the issue after the firmware update. It did not occur to me to test the sensor with smoke after the update. @msnjdev Did your sensor activate due to smoke for natural reasons, or did you decide to test it after update?

[msnjdev]

@mrmaximas Yes, they replied, but it was only a basic first-level support response. They did confirm that 0.0.0_0021 is the latest firmware. I’ve replied to them again, and hopefully the case will be escalated to their higher-level technical team.

I was a little luckier, they requested the video right away 😎 Aqara is very conservative; they strongly dislike their devices being used in third-party systems and may simply refuse to provide support. The unfortunate aspect is that it was difficult to identify the issue after the firmware update. It did not occur to me to test the sensor with smoke after the update. @msnjdev Did your sensor activate due to smoke for natural reasons, or did you decide to test it after update?

@mrmaximas I tested mine with vaping smoke and 3D Filament burning. I tested it before and after the update. Before, it worked with multiple beeps. After, sadly not anymore. I just bought them last week, so I never had any real situation, because I didn't fixed them yet on my wall.

[mrmaximas]

@msnjdev If you hadn't make the test after this update, no one might have discovered the hidden problem until a real fire broke out...

[msnjdev]

As this is an pull request, I created an issue ticket in this repo, so we can continue the conversation there. #938