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

Legrand 067775/741811 update invalid image failure #328

Closed
yashijoe opened this issue Jun 19, 2023 · 144 comments
Closed

Legrand 067775/741811 update invalid image failure #328

yashijoe opened this issue Jun 19, 2023 · 144 comments

Comments

@yashijoe
Copy link

What happened?

Interface tells me there is an update
I try to upgrade and get the message “invalid image”

What did you expect to happen?

Upgrade successfully

How to reproduce it (minimal and precise)

Press upgrade firmware
Get the message:
“ Error 2023-05-17 09:18:40Update of 'refrigerator_plug' failed (Update failed with reason: 'invalid image')”

Zigbee2MQTT version

1.30.4-1

Adapter firmware version

004a

Adapter

Legrand 067775/741811

I’ve also tried with dev version and updated index.json. Same result

thank you

@SilentT-FR
Copy link
Contributor

SilentT-FR commented Jun 19, 2023

Original post : Koenkk/zigbee2mqtt#17709

Same problem for me

The Firmware files was downloaded from Legrand Website
https://static.developer.legrand.com/files/2023/05/1021-0011-004e4203-NLP.zip

I have open a post on the forum of legrand
https://developer.legrand.com/forums/topic/connected-outlet-nlp-78-firmware/

i Cant sniffing my zigbee traffic to capture the OTA

i have tested to capture from ethernet network but contrary from this howto : https://github.com/zigbeefordomoticz/wiki/blob/master/en-eng/Corner_Retreiving-Legrand-Firmware.md from @pipiche38

i dont see same url
3 0.072753 192.168.1.88 51.145.143.28 HTTP 248 GET /firmware/0/xxxx/17/74/xxxxx/tiaLUbj6BjvLZXCRfIPne-l11eJ7vPp0GozOAxfY4NQ HTTP/1.1 Host: fw.netatmo.net:80\r\n

@SilentT-FR
Copy link
Contributor

@benjR You have Capture the 78 OTA Files and it was the same issue with your file, you have an idea about my capture ? i have this Gateway

@essegi65 just for follow the issue and an user with same issue with bticino product

@rossowl just for follow the issue, you have 46 outlet no news with the new file from legrand, you have better experiance ?

@vezyr same issue follow the issue

@novisys same issue follow the issue

@sekot same issue i thinks follow the issue

@essegi65 same issue follow the issue

@benjR
Copy link
Contributor

benjR commented Jun 19, 2023

I used another gateway, but here is my theory :

I think the firmware files are fine (I used the same method for the other Legrand device I pushed and managed to update through z2m locally) but there is an issue on how the files are matched to the devices, seems like it's trying to apply to a wide scope of devices instead of just the single corresponding device.

When I added the fw file I sniffed I used the node tool provided to do so, and instead of adding some new lines it replaced another fw for another device in the json file.

So I'm thinking both issue could be the same : the detection of the device is not working well on Legrand files or products (same info? same ids?) therefore when trying to update it is probably using the wrong file on the wrong device.

@SilentT-FR
Copy link
Contributor

ok i have a beginning of response about legrand

https://developer.legrand.com/forums/topic/nlc-firmware-version/#post-9734

they are aware about the difference between the version number which is written in the file and those which are provided by the zigbee stack

@SilentT-FR
Copy link
Contributor

SilentT-FR commented Jun 19, 2023

I used another gateway, but here is my theory :

I think the firmware files are fine (I used the same method for the other Legrand device I pushed and managed to update through z2m locally) but there is an issue on how the files are matched to the devices, seems like it's trying to apply to a wide scope of devices instead of just the single corresponding device.

When I added the fw file I sniffed I used the node tool provided to do so, and instead of adding some new lines it replaced another fw for another device in the json file.

yes because the precedent firmware is the NLP v74, you have replaced that by the v78

3b61e15#diff-7aebb122a6ea8a2749d60cb05b7e103c9eae6e2e85e48d2d6cd9e20b63013975L1539-L1541

and i you can see the firmware file from legrand i use also the node script

and it replace your

c0234dd#diff-7aebb122a6ea8a2749d60cb05b7e103c9eae6e2e85e48d2d6cd9e20b63013975R1539-R1541

the script detect same version same size but not the same checksum... enough to pull your hair out

So I'm thinking both issue could be the same : the detection of the device is not working well on Legrand files or products (same info? same ids?) therefore when trying to update it is probably using the wrong file on the wrong device.

here is your PR
3b61e15

you have writen : Legrand-412171-78.fw

NLP Firmware is for this devices : https://static.developer.legrand.com/files/2023/02/Connected-outlet.xlsx

Cloud legrand firmware say NLPO but i thinks its use the same firmware

legrand NLP

@SilentT-FR
Copy link
Contributor

@benjR Comparing your file and the legrand firmware website

Only 2 lines is not equal the first and the last

buts its not exploitable file in notepad++ i dont know software can read this

@SilentT-FR
Copy link
Contributor

Normaly new info next week
https://developer.legrand.com/forums/topic/nlc-firmware-version/

@yashijoe
Copy link
Author

yashijoe commented Jul 1, 2023

🤞🏻

@trollix
Copy link

trollix commented Jul 3, 2023

Same bug for me:
OTA doesn't work.

screenshot_1310 screenshot_1311

@SilentT-FR
Copy link
Contributor

Hi all Legrand respond :
https://developer.legrand.com/forums/topic/nlc-firmware-version/

If anyone of subscribed user with same problem can capture the traffic and identify the version from you start upgrade

For me from v74 ( "installed_version": 4867071, ) and v62 ("installed_version": 4080131) not work
003e > v62
004a > v74
(hex to dec)

@SilentT-FR
Copy link
Contributor

SilentT-FR commented Jul 25, 2023

Ehhhh

i have testing to simply reboot the socket by using my circuit breaker and i have clic update just after apear online
and is go and running to the end

i make more socket tommorow,,, you know the WAF...

If you can test other...

Cordially

@SilentT-FR
Copy link
Contributor

Not work for other socket...

@SilentT-FR
Copy link
Contributor

Its because it was in older version

@tkintscher
Copy link

Hmm, interesting. I have two wall switches here (067771) and am trying to upgrade them.

Both have "installed_version": 4604927 and "latest_version": 4669955.

The first one was not power cycled. This shows the "invalid image" error (see before_reboot.txt).

The second one I rebooted with the circuit breaker (for ~15 sec), then clicked update as soon as the switch appeared again. Here I see several commandQueryNextImageRequest messages. Then nothing for a few minutes. Finally I get Error: Timeout: device did not request any image blocks.

I attach the two logs from z2m, but probably it's the same that you folks see...
after_reboot.txt
before_reboot.txt

@tkintscher
Copy link

I also do not understand in the case of NLF:

It says on developer.legrand.com that the version is 72.
The filename is 1021-000e-00474203-NLF.zigbee and
0x47 (hex) = 71 (dec)

Now, 474203 is the actual version in the file header, but maybe there was a mistake when uploading?

@essegi65
Copy link

essegi65 commented Aug 2, 2023

I updated to version 1.32.2 but I still have problems updating the "bticino" K4531C devices (zigbee associates them as LEGRAND 067775/741811) currente firmware version 004A.
Makes "invalid image" error

@SilentT-FR
Copy link
Contributor

No news from legrand forum
i have upload a sniffing capture i thinks its analyse it

@titou4307
Copy link

Same problem for me : impossible to update Legrand 412170

Firmware passed of 0025 to 004e on 1/3 Legrand 412170
Firmware not pass of 0025 to 004e on 2/3 Legrand 412170

Does it possible to force the falsh with the firmware file under Z2M

@benjR
Copy link
Contributor

benjR commented Aug 15, 2023

Didn't have the time to look more at it recently, but now the OTA check fails on all my Legrand devices with this message, never had it before on any device, tried with my Legrand 067776 and 412171 devices.

image

EDIT: had to re-pair all devices to manage to get rid of it

@Koenkk
Copy link
Owner

Koenkk commented Aug 25, 2023

@SilentT-FR I think we should disable OTA for now, agree? (which devices are affected?)

@titou4307
Copy link

I don't know what to do...
Many sujects opened

@rossowl
Copy link

rossowl commented Aug 25, 2023

@titou4307 zigbee2mqtt settings OTA Disable automatic update check
Then stop zigbee2mqtt, open state.json, find your device and remove lines:
"update": {
"state": "available",
"installed_version": 4867071,
"latest_version": 5128707
}
Then start zigbee2mqtt and done.

@lamerjack
Copy link

Same issue with a Bticino F20T60A that is a Legrand 412015 say invalid image.
If i check ota on a updated unit say that the firmware in the unit is more recent.
I tested also with SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P latest firmware. and with a different brand dongle.

@Koenkk
Copy link
Owner

Koenkk commented Aug 27, 2023

@titou4307 does it work for anyone? If not, we should disable it.

@pierrepinon
Copy link

@Koenkk it's impossible to upgrade legrand devices to latest firmware. So I think you can disable it !

@r0m1CH
Copy link

r0m1CH commented Mar 11, 2024

i don't know how to check if I'm up to date or not. I mean Z2M see update but cannot do anything. But is it real?
image

Based on my findings, I should be under latest version of theses firmwares:
412170 => NLPT
412171 => NLPO
064882 => NLC

But I dont know how to double check/ validate this.

@wladkolc
Copy link

Hello, same issue here when using with skyconnect dongle.

I have installed zigbee2mqtt on my macbook, connected older sonoff zigbee 3.0 stick and made upgrade. After upgrade i have powered off circuit breaker with all lights for 2 minutes. Then my device was updated properly.

@ddrag001
Copy link

ddrag001 commented Mar 11, 2024

Hello, same issue here when using with skyconnect dongle.

I have installed zigbee2mqtt on my macbook, connected older sonoff zigbee 3.0 stick and made upgrade. After upgrade i have powered off circuit breaker with all lights for 2 minutes. Then my device was updated properly.

This didn't work for me. It takes about 20 min for the update download then I powered off the breaker for 2 min, but it still giving me this:
legrand error

@r0m1CH
Copy link

r0m1CH commented Mar 11, 2024

Same issue. This is so annoying. Cannot do anything :s

@ddrag001
Copy link

I wonder if the Legrand gateway would make the update process easier... I have one coming next week.

@Loic691
Copy link
Contributor

Loic691 commented Mar 12, 2024 via email

@r0m1CH
Copy link

r0m1CH commented Mar 12, 2024

But you need to remove pairing from z2m to the legrand gateway ?
I had one and never find a way to handle this smoothly.
Yesterday (i dont why), i was able to update on of my 064882 device to the latest version I guess. However the firmware date is older...
image

@ddrag001
Copy link

That's weird. Originally, my power sockets 067775/741811 came with firmware version 54529536 and the power consumption was not working, so I forced the update using the NLP-74, and now it says fw version 4867071, 20180307 004a and everything works, but that is actually downgrade lol what a mess .
Does that mean that the device should only use this firmware because the newer one would not work properly? Like I mentioned, the device came with firmware version 54529536, which is newer, and the power consumption wasn't working.
So, now I am not sure if its a good idea to upgrade again, at least I am hoping the power consumption work under the latest fw.

@ddrag001
Copy link

Quick update: I was able to upgrade by turning off the circuit breaker for 2min. then as soon as I turn it back on, within less than a minute, I initiated the update and after about 20 min it was successfully updated from 004a (4867071) to 0053 (5456895) and everything works.

@marcbernis
Copy link

marcbernis commented Mar 12, 2024 via email

@ddrag001
Copy link

@marcbernis I am glad you got it updated. My socket also shows fw 0053 but with a build date 20180307. That is weird. I have two more of these.I am fighting with the second one. Now after the NLP-74 fw forced update procedure, the power consumption was not working (worked on the 1st socket), but I suspected the entries in the reporting were just not added which I did and then it worked. What I also noticed is that for two identical devices Legrand (067775/741811) its giving me a different upgrade path
1st one: 004a (4867071) -> 0053 (5456895)
2nd one: 004a (4867071) -> 4866563

@Xavinooo
Copy link

For legrand devices, the firmware build date is actually the device manufacturing date. It won't change via firmware update.

@FabianMangold
Copy link
Contributor

FabianMangold commented Mar 12, 2024

Hi there,

The last couple of firmwares have been quite a struggle indeed.
What you can do, is try the following:

  • Update issue: Update does not start:
    Try to powercycle the device, switching it OFF a couple of minutes prior powering it back on.
  • Update fails to complete (device did not request any image blocks)
    You may want to patch the updateToLatest method of the OTA common lib as follows:
            // increase the timeout for Legrand devices, so that they will re-initiate and update themselves
            if ( request.payload.manufacturerCode == 4129 ) {
                imageBlockOrPageRequestTimeoutMs = 900000;
            }

or use the attached file locally.
Since this has some drawbacks, we will most probably not patch this into the DEV branch straightaway.
Let me know how that out for you. Using this, all my Legrand devices were able to update to the latest firmware releases.

common.ts.txt
CC: @Koenkk

Also, generally speaking, please open a new ticket referencing this one, instead of writing into a closed thread, since this makes tracking way more complicated.

Cheers,

@r0m1CH
Copy link

r0m1CH commented Mar 12, 2024

THanks @FabianMangold for the feedback. I will try.

Can I abuse you? I'm not sure where to place common.ts under my Z2M docker container ?
Cannot find the file where updateToLatest function is defined.
Can you be more specific ?

Cheers,

@r0m1CH
Copy link

r0m1CH commented Mar 12, 2024

Oh maybe I speak too quickly.
Are you refering to /app/node_modules/zigbee-herdsman-converters/src/lib/ota/common.ts ?

@FabianMangold
Copy link
Contributor

FabianMangold commented Mar 12, 2024

Hi @r0m1CH ,
That seems the location indeed !
To be honnest, i don't use Docker really, I run the builds out of my IDE, so I am afraid my guidance is somewhat limited here, sorry for that.

I've commited the fix to my fork over here if that helps.

@r0m1CH
Copy link

r0m1CH commented Mar 12, 2024

Thanks again. This is the right files. I made the change I'm gonna try this and keep you posted !

@r0m1CH
Copy link

r0m1CH commented Mar 13, 2024

Feedback: This is working super well. @FabianMangold
I updated my 8 legrand devices that was waiting updates for MONTHS... Nothing worked.

So what is working well (some device ask two updates):

  1. Amend the OTA common lib as explained above.
  2. powercycle the device off for few minutes
  3. start the OTA

This time it should complete.

Thanks a lot !

@ddrag001
Copy link

ddrag001 commented Mar 13, 2024

I have been able to update my 3 sockets using the method I posted above, however it's a little tricky, but it gets the job done eventually.
@r0m1CH I wanted to try Fabians method, but I could not find common.ts on my system, nor I could find the path above. Do you have any hints? I am running HA & Z2M together on a bare metal.

@r0m1CH
Copy link

r0m1CH commented Mar 13, 2024

@ddrag001 the ts file is not compiled yet.

I had to edit this exact file:
/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js

I don't know where it can be located on your bare metal system.

I have to edit this file again every time I recreate the docker container.
It could be great if these lines could be definitively written in the project for the next release.

@FabianMangold I had to put 1800000 ms instead your 900000ms.
My normal update time is around 20 minutes when it starts.

@FabianMangold
Copy link
Contributor

Hi @r0m1CH ,

Thanks for the feedback. You are right, my value was based on a somewhat faster update (i had decreased the delay between packets for troubleshooting purposes) and of course of a less congested network.

I've created PR #7212 so that the fix makes into the DEV branch.
@ddrag001: Please use the next DEV releases in order to test the fix. You will find guidance on how to switch Z2M to DEV here.

@HermesHonshappo
Copy link

Hello. Just FYI, I switched the Z2M add-on in HA to the edge branch, which includes this PR
After a power cycle, I was able to update a Legrand 412171 which had been pestering me for the past 2 months about an update available, but was never able to update.
Thanks a lot, and I confirm it helps for other Legrand devices, not only the ones in the issue title

@cocapic
Copy link

cocapic commented Apr 9, 2024

Hi, did i miss something to do ?

im in 1.36.1 OOTB who normaly fix this issue, but still have same behavior fo 412170, 412171

ty

@marcbernis
Copy link

marcbernis commented Jun 3, 2024

Hello I cannot update Legrand 412171 even using Z2M dev branch.

Many thanks for support!
Best regards
Marc

I'm using Z2M Edge (1.37.1-dev commit: 9f5b5d1 over HA.
I made a power cycle (even unpair / pair) the device & power cycle before and or after.

Zigbee2MQTT version 1.37.1-dev commit: 9f5b5d1
Coordinator type zStack3x0
Coordinator revision 20221226

Initial version of 41271:
Build date: 20220706
Firmware version: 0025
Installed Version: 24417312441731

Target version of 41271:
Build date: 20221130
Firmware version: 0053
Version: 5456895

The update upload work to the end but it finished saying it updated to same version (see logs below):

I'm using Z2M Edge (1.37.1-dev commit: 9f5b5d1 over HA.
The update upload work to the end but it finished saying it updated to same version (see logs below):
Info 2024-05-30 14:45:36MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand/action', payload 'off'
Info 2024-05-30 14:45:45Checking if update available for 'Chauffe Eau Legrand'
Info 2024-05-30 14:45:46Update available for 'Chauffe Eau Legrand'

====================================================================================================================================================================
Info 2024-05-30 14:45:46MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":112,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":2441731,"latest_version":5456895,"state":"available"},"update_available":null,"voltage":null}'

=> From verion 2441731 SW Build 0025 to 5456895 SW Buils 0053
...

Info 2024-05-30 14:47:33Update of 'Chauffe Eau Legrand' at 7.89%, ≈ 20 minutes remaining
...
Info 2024-05-30 15:04:14Update of 'Chauffe Eau Legrand' at 94.26%, ≈ 1 minutes remaining
...

Info 2024-05-30 15:06:33Finished update of 'Chauffe Eau Legrand'

=> Update said from 5456895 to 5456895 (looks maybe abnormal)
Info 2024-05-30 15:06:33MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":105,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":5456895,"latest_version":5456895,"state":"idle"},"update_available":null,"voltage":null}'

====================================================================================================================================================================
Info 2024-05-30 15:06:33Device 'Chauffe Eau Legrand' was updated from '{"dateCode":" \u000020220706\u0000\u0000\u0000\u0000\u0000","softwareBuildID":"0025"}' to '{"dateCode":" \u000020220706\u0000\u0000\u0000\u0000\u0000","softwareBuildID":"0025"}'

=> Update said from 0025 to 0025 (initial version 2441731)
Info 2024-05-30 15:06:34MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"from":{"date_code":" \u000020220706\u0000\u0000\u0000\u0000\u0000","software_build_id":"0025"},"id":"Chauffe Eau Legrand","to":{"date_code":" \u000020220706\u0000\u0000\u0000\u0000\u0000","software_build_id":"0025"}},"status":"ok","transaction":"zz8fd-6"}'

Info 2024-05-30 15:06:35MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"action":"off","auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":109,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":5456895,"latest_version":5456895,"state":"idle"},"update_available":null,"voltage":null}'

Info 2024-05-30 15:06:35MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"action":"","auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":109,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":5456895,"latest_version":5456895,"state":"idle"},"update_available":null,"voltage":null}'
Info 2024-05-30 15:06:35MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand/action', payload 'off'

Error 2024-05-30 15:16:35Failed to configure 'Chauffe Eau Legrand', attempt 1 (Error: ZCL command 0x0004740000854ff5/1 haElectricalMeasurement.configReport([{"minimumReportInterval":10,"maximumReportInterval":65000,"reportableChange":5,"attribute":"activePower"},{"minimumReportInterval":10,"maximumReportInterval":65000,"reportableChange":null,"attribute":"rmsCurrent"},{"minimumReportInterval":10,"maximumReportInterval":65000,"reportableChange":null,"attribute":"rmsVoltage"}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNREPORTABLE_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:316:28) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:771:26) at Endpoint.configureReporting (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:557:9) at setupAttributes (/app/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:76:13) at result.configure (/app/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:1488:29) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/index.ts:173:21) at Configure.configure (/app/lib/extension/configure.ts:121:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))
Info 2024-05-30 14:45:36MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand/action', payload 'off'
Info 2024-05-30 14:45:45Checking if update available for 'Chauffe Eau Legrand'
Info 2024-05-30 14:45:46Update available for 'Chauffe Eau Legrand'

====================================================================================================================================================================
Info 2024-05-30 14:45:46MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":112,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":2441731,"latest_version":5456895,"state":"available"},"update_available":null,"voltage":null}'

=> From verion 2441731 SW Build 0025 to 5456895 SW Buils 0053
...

Info 2024-05-30 14:47:33Update of 'Chauffe Eau Legrand' at 7.89%, ≈ 20 minutes remaining
...
Info 2024-05-30 15:04:14Update of 'Chauffe Eau Legrand' at 94.26%, ≈ 1 minutes remaining
...

Info 2024-05-30 15:06:33Finished update of 'Chauffe Eau Legrand'

Info 2024-05-30 15:06:33MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":105,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":5456895,"latest_version":5456895,"state":"idle"},"update_available":null,"voltage":null}'

====================================================================================================================================================================
Info 2024-05-30 15:06:33Device 'Chauffe Eau Legrand' was updated from '{"dateCode":" \u000020220706\u0000\u0000\u0000\u0000\u0000","softwareBuildID":"0025"}' to '{"dateCode":" \u000020220706\u0000\u0000\u0000\u0000\u0000","softwareBuildID":"0025"}'

=> Update said from 0025 to 0025 (initial version 2441731)

Info 2024-05-30 15:06:34MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/update', payload '{"data":{"from":{"date_code":" \u000020220706\u0000\u0000\u0000\u0000\u0000","software_build_id":"0025"},"id":"Chauffe Eau Legrand","to":{"date_code":" \u000020220706\u0000\u0000\u0000\u0000\u0000","software_build_id":"0025"}},"status":"ok","transaction":"zz8fd-6"}'

Info 2024-05-30 15:06:35MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"action":"off","auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":109,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":5456895,"latest_version":5456895,"state":"idle"},"update_available":null,"voltage":null}'

Info 2024-05-30 15:06:35MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand', payload '{"action":"","auto_mode":"off","current":null,"device_mode":"switch","led_if_on":"OFF","led_in_dark":"OFF","linkquality":109,"power":0,"power_on_behavior":"previous","state":"OFF","update":{"installed_version":5456895,"latest_version":5456895,"state":"idle"},"update_available":null,"voltage":null}'
Info 2024-05-30 15:06:35MQTT publish: topic 'zigbee2mqtt/Chauffe Eau Legrand/action', payload 'off'

Error 2024-05-30 15:16:35Failed to configure 'Chauffe Eau Legrand', attempt 1 (Error: ZCL command 0x0004740000854ff5/1 haElectricalMeasurement.configReport([{"minimumReportInterval":10,"maximumReportInterval":65000,"reportableChange":5,"attribute":"activePower"},{"minimumReportInterval":10,"maximumReportInterval":65000,"reportableChange":null,"attribute":"rmsCurrent"},{"minimumReportInterval":10,"maximumReportInterval":65000,"reportableChange":null,"attribute":"rmsVoltage"}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNREPORTABLE_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:316:28) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:771:26) at Endpoint.configureReporting (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:557:9) at setupAttributes (/app/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:76:13) at result.configure (/app/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:1488:29) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/index.ts:173:21) at Configure.configure (/app/lib/extension/configure.ts:121:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))

@marcbernis
Copy link

Hello I still have this update issue with at the end of the update process "from 025 to 025" and no update to latest version while initilal OTA message is "installed_version":2441731,"latest_version":5456895,"".

Any idea on how to fix it?

Thanks
Marc

@FabianMangold
Copy link
Contributor

Hi Marc,

Since this thread is closed, it's probably best to open another one, for better tracking.
It's been quite a whilte since the last update, if none of the above workarounds work, you could try to explicitly downgrade to an older firmware, and attempt to update to the latest.
Also note that certain devices require some intermediate firmwares, thus this approach "may" work for your device.

Can you please give this a try, and if not successful open another issue for further tracking ?
Thanks,
Fabian

@marcbernis
Copy link

marcbernis commented Sep 25, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests