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.

Sign up for GitHub

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

Jump to bottom

Aqara curtain driver e1 OTA fails #15745

Closed
mjvanderveen opened this issue Dec 24, 2022 · 84 comments · Fixed by Koenkk/zigbee-herdsman-converters#6983
Closed

Aqara curtain driver e1 OTA fails #15745

mjvanderveen opened this issue Dec 24, 2022 · 84 comments · Fixed by Koenkk/zigbee-herdsman-converters#6983
Labels
problem Something isn't working

Comments

@mjvanderveen
Copy link

What happened?

ZNCLBL01LM aqare curtain driver e1 OTA update announced in both zigbee2mqtt as well as home assistant updates. But the update is unable to complete.

What did you expect to happen?

OTA to complete

How to reproduce it (minimal and precise)

Current version 0.0.0_0027

Go to zigbee2mqtt ota and press update firmware for the aqara curtain driver e1 track version.

Zigbee2MQTT version

1.28.4-1

Adapter firmware version

0100

Adapter

Sonoff_Zigbee_3.0_USB_Dongle_Plus

Debug log

info 2022-12-24 21:36:14: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Updating 'Curtain parents right' to latest firmware","meta":{"device":"Curtain parents right","status":"update_in_progress"},"type":"ota_update"}'

debug 2022-12-24 21:36:16: Received Zigbee message from 'Curtain parents right', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":27,"imageType":4105,"manufacturerCode":4447}' from endpoint 1 with groupID 0
debug 2022-12-24 21:36:16: Got OTA request '{"fieldControl":0,"manufacturerCode":4447,"imageType":4105,"fileVersion":27}'
debug 2022-12-24 21:36:16: ZigbeeOTA: downloaded main index
debug 2022-12-24 21:36:16: getNewImage for '0x54ef441000558255', meta {"fileVersion":6168,"fileSize":288213,"url":"https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20220506181329_lumi.curtain.agl001_Multi_JN5189_FMSH_0.0.0_2424_20220422_1aa302.ota","sha512":"0d1bae25759420898d381b98e97858d2e47f48cd3495abd8754661d0e1957eb5b570a2ae7435acc435d5a18665409e07148abae6f1f4a190c9af786d94ec725d"}
debug 2022-12-24 21:36:16: ZigbeeOTA: downloading firmware image from https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20220506181329_lumi.curtain.agl001_Multi_JN5189_FMSH_0.0.0_2424_20220422_1aa302.ota
debug 2022-12-24 21:36:17: OTA update checksum validation succeeded for '0x54ef441000558255'
debug 2022-12-24 21:36:17: getNewImage for '0x54ef441000558255', image header {"otaUpgradeFileIdentifier":{"type":"Buffer","data":[30,241,238,11]},"otaHeaderVersion":256,"otaHeaderLength":56,"otaHeaderFieldControl":0,"manufacturerCode":4447,"imageType":4105,"fileVersion":6168,"zigbeeStackVersion":2,"otaHeaderString":"CURTAIN-OCC-JN5189---ENCRYPTED00","totalImageSize":288213}
debug 2022-12-24 21:36:17: Got new image for '0x54ef441000558255'
debug 2022-12-24 21:36:17: Starting upgrade

error 2022-12-24 21:38:47: Update of 'Curtain parents right' failed (Timeout: device did not request any image blocks)
debug 2022-12-24 21:38:47: Error: Timeout: device did not request any image blocks
at /app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:360:28
at runNextTicks (node:internal/process/task_queues:61:5)
at listOnTimeout (node:internal/timers:528:9)
at processTimers (node:internal/timers:502:7)
@mjvanderveen mjvanderveen added the problem Something isn't working label Dec 24, 2022
@tjxism
Copy link

tjxism commented Jan 7, 2023

I am also experiencing this issue. Same issue for QBKG31LM. Update reported and can be started, however it will show failed to update in the end.

@lundyfpv
Copy link

Seeing the same on my end, but I'm using the TubeZB coordinator if that matters somehow.

@Uschinator
Copy link

Same. Using a Conbee 2
Aqara curtain driver E1 (ZNCLBL01LM)
Firmware: 0.0.0_0024

The Update starts and after it goes to 100% it shows the same Firmware again and if i check i can update the Firmware again. On home Assistant it shows the Version as 6168

"update": {
"installed_version": 24,
"latest_version": 6168,
"state": "available"
},
"update_available": true,

@VeeTeeDev
Copy link

Same problem :-)...

I have 3 and the sonoff stick model E.

Screenshot 2023-01-27 at 21 13 47

One of them shows a progress bar... but when it's finished, nothing changes. The other 2 don't do anything...

@pushnoi
Copy link

pushnoi commented Jan 28, 2023 •
edited
Loading

Yes, same problem over here. The version 6168 does not make any sense. Latest one available is supposed to be Version: 0.0.0_2424: https://www.aqara.com/en/version/curtain-driver-e1-track-version

@LayerCakeMakes
Copy link

Same issue here, I'm stuck on 0.0.0_0024.

@NfkPollo
Copy link

NfkPollo commented Feb 1, 2023

I have same issue
image

@nathan-curtis
Copy link

Bump - same issue and it doesn't look like an owner has been assigned yet?

@GewoonRoy GewoonRoy mentioned this issue Feb 9, 2023
Closed
@klevin92
Copy link

same issue

@mrmartin95
Copy link

Same issue

@ChLah
Copy link

ChLah commented Mar 2, 2023

Same issue here.

@WorlockM
Copy link

WorlockM commented Mar 6, 2023

Same issue using Zigbee2MQTT and Conbee 2 stick.

@pushnoi
Copy link

pushnoi commented Mar 26, 2023

Who do i have to buy a beer to get this to be picked up?

@ChLah
Copy link

ChLah commented Mar 30, 2023

I'd join you spending a beer

Who do i have to buy a beer to get this to be picked up?

@github-actions
Copy link
Contributor

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 Apr 30, 2023
@pushnoi
Copy link

pushnoi commented Apr 30, 2023

Bump, still same issue.

@Sacr87
Copy link

Sacr87 commented Apr 30, 2023

Same issue.

@LayerCakeMakes
Copy link

Yes, very much should not be automatically closed, this is still a problem.

@github-actions github-actions bot removed the stale Stale issues label May 1, 2023
@cranxi
Copy link

cranxi commented May 5, 2023

Same issue.

@AppleFlapp
Copy link

looks like the same issue here.

@Hotelk52339
Copy link

Same issue

Is someone going to fix it ?

@gr1spy
Copy link

gr1spy commented May 24, 2023

Same issue :(

@Joakim-T
Copy link

Same issue on both of mine

Both devices report firmware upgrades are available..

"update": {
    "installed_version": 27,
    "latest_version": 6168,
    "state": "available"
},

When i try to update it fails after a while with..

Update of 'Curtain Bedroom' failed (Timeout: device did not request any image blocks)

@Dimmers81
Copy link

Same for me

@rcursaru
Copy link

It also happens while using a Home Assistant SkyConnect dongle.
image
I am also willing to contribute to the (case of good) beer fund :)

@pesbob
Copy link

pesbob commented Jul 11, 2023

Same issue. But the Aqara curtain driver e1, works fine. So no need for an update.

@luchtgitaar
Copy link

The problem is Z2M 'thinks' an update is available. But there is no update available (at least on the Xiaomi end).

@segdy
Copy link

segdy commented Nov 17, 2023

Very much struggling with this as well.
Where is the source for OTA availability? Where did z2m know there’s an update available?

@nathan-curtis
Copy link

In your screenshot it looked that the update started but does not finish, could you provide me the herdsman debug log when trying to update this device?

As soon as I can I'm just now recovering from the addon move weirdness of NR16 this week it may be a few days. But someone just above me nailed it. The problem is we're being offered something not there or invalid.

The spinning was just a side effect. Now that you fixed that one we still keep getting offered this invalid Ota.

@Koenkk
Copy link
Owner

Koenkk commented Nov 18, 2023

Can someone provide the debug log when trying to update this device? The OTA is pulled from https://github.com/koenkk/zigbee-ota

@nathan-curtis
Copy link

Sorry got caught up in the changes to addons this week had to repair my install. Will be at least Mon before I can.

@highincolorado
Copy link

highincolorado commented Nov 18, 2023 via email

@highincolorado
Copy link

highincolorado commented Nov 18, 2023 via email

@Koenkk
Copy link
Owner

Koenkk commented Nov 19, 2023

@Otnow you added the fw for this device (lumi.curtain.agl001) in Koenkk/zigbee-OTA#147, it seems to not be working, should we remove this or is there an other OTA available for this device?

@VeeTeeDev
Copy link

All,

Too bad I didn't read all of this first. I was very annoyed with the update messages in Zigbee2mqtt...
I tried adding the rods to my Aqara app through my G2H camera's. I wasn't able to do that because of 'wrong' region errors. My G2H are Chinese. So I decided to go and buy the AQARA Hub M2 (yesterday). I connected the rods and tried to update them.
result when I go to the firmare in the aqara app:
0.0.0_2424 (no updates available "Your firmware is up do date") (1 of 3)
0.0.0_2727 (no updates available "Your firmware is up do date") (2 of 3)

So of the 3 I have, 2 are on 0.0.0_2727 and 1 on 0.0.0_2424, but for both there is no update available....

Weird!

@Otnow
Copy link

Otnow commented Nov 19, 2023

Unfortunately, the device reports an incorrect firmware version (lower than it actually is) and, accordingly, the firmware update occurs with an error, because it tries to update to the same or lower version than the one on the device.

I will try to make a fix in the code for this problem in the near future.

@anthonyjhicks
Copy link

anthonyjhicks commented Nov 28, 2023 •
edited
Loading

Looks like this issue has been identified, thanks Otnow. Just adding to the up votes here that I also have the 27 to 6168 stuck upgrade issue. I disabled the update entities on my Aqara E1's to help my OCD. Looking forward to a fix though ;)

@vsimanin
Copy link

vsimanin commented Jan 15, 2024 •
edited
Loading

Unfortunately, the device reports an incorrect firmware version (lower than it actually is) and, accordingly, the firmware update occurs with an error, because it tries to update to the same or lower version than the one on the device.

I will try to make a fix in the code for this problem in the near future.

@Otnow
Hi! I'm sorry for the trouble. It's been a long time, have you managed to solve the problem? I'm also stuck with this endless update.

@Otnow
Copy link

Otnow commented Jan 15, 2024

@Otnow
Hi! I'm sorry for the trouble. It's been a long time, have you managed to solve the problem? I'm also stuck with this endless update.

Hi. Unfortunately not yet.

@marcgarciamarti
Copy link

marcgarciamarti commented Jan 23, 2024 •
edited
Loading

Affected by this too. Also, these devices are not reliable for me. I wanted to upgrade the firmware in an attempt to fix the unreliability that I'm experiencing. Anybody else experiencing unreliability with device dropping out of the network? I did not link the issue I created just because it may not be related and wanted to avoid adding noise...

@markhaines
Copy link

I’ve got a couple of them in my network and they’ve been good as gold reliability wise. Still haven’t needed to charge them yet either!

@marcgarciamarti
Copy link

@markhaines that is indeed interesting. My experience is, when I pair these devices, they work for a limited time period (a couple of days), then they stop working and any command I send to them, they simply won't react. It's good to know that your experience is positive. Could you share what FW versions are your devices on?

@segdy
Copy link

segdy commented Jan 23, 2024

Also for me well so far from reliably perspective.

Third reality blinds in turn, nothing but troubles

@marcgarciamarti
Copy link

I created issue 20795. If you could take a look at it, I would be very thankful. I really don't want to paste a link to that issue here, as I don't want for Github to link the two issues together, but any insight would be most appreciated

@vsimanin
Copy link

I created issue 20795. If you could take a look at it, I would be very thankful. I really don't want to paste a link to that issue here, as I don't want for Github to link the two issues together, but any insight would be most appreciated

please, these are two different problems, write to the point, otherwise we will not move forward.

@marcgarciamarti marcgarciamarti mentioned this issue Jan 27, 2024
Closed
@Otnow Otnow mentioned this issue Jan 31, 2024
Merged
@Otnow
Copy link

Otnow commented Jan 31, 2024

The PR fixing current problem has been merged.

Note for PR: when pairing, device will immediately display correct firmware version, otherwise you need to wait until device sends next heartbeat message (~ 6-6,5 minutes) or perform its manual reconfiguration and then restart zigbee2mqtt (so that correct version is displayed in web interface).

@vsimanin
Copy link

vsimanin commented Feb 1, 2024 •
edited
Loading

Note for PR:

Very thanks @Otnow !!
Did I understand correctly that there will be no changes until these fixes are included in the new version of z2m?

@Otnow
Copy link

Otnow commented Feb 1, 2024

Very thanks @Otnow !!
Did I understand correctly that there will be no changes until these fixes are included in the new version of z2m?

You are welcome 🙂

Yes, fix is included in today's release 1.35.2.

@vsimanin
Copy link

vsimanin commented Feb 1, 2024

It works! I’ll add a feature: when checking for updates through the z2m interface, an error appears that I have a newer version. Perhaps this is normal, in any case it does not cause problems, everything is fine!
Screenshot_2024-02-01-22-36-20-85_c3a231c25ed346e59462e84656a70e50

@Otnow
Copy link

Otnow commented Feb 1, 2024

I’ll add a feature: when checking for updates through the z2m interface, an error appears that I have a newer version. Perhaps this is normal, in any case it does not cause problems, everything is fine!

Yes, this is normal, sometimes it happens that firmware version on device is higher than available OTA update.

@mjvanderveen
Copy link
Author

Wonderful, will give it a go! Thanks for all the debugging support

@highincolorado
Copy link

Installed and tested, looks good, thanks!

@anthonyjhicks
Copy link

anthonyjhicks commented Feb 2, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
problem Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix display of incorrect firmware version for Aqara ZNCLBL01LM Otnow/zigbee-herdsman-converters