NLC Firmware Version
Hi
Before upgrade a Zigbee NLC, i have fetched this version
cluster ‘genOta’, data ‘{“fieldControl”:0,”fileVersion”:1524227,”imageType”:21,”manufacturerCode”:4129}’ from endpoint 1 with groupID 0
1524227 its 0017 so v23
i use the v31 on your website my system detect this version 2048515
The upgrade was a success
but After my zigbee composent sent me this :
‘commandQueryNextImageRequest’, cluster ‘genOta’, data ‘{“fieldControl”:0,”fileVersion”:2049023,”imageType”:21,”manufacturerCode”:4129}’ from endpoint 1 with groupID 0
this version : 2049023 its not corresponding on detected files you have an idea ?
Hello Clément,
I answer to your 2 topics at once
I asked Netatmo’s developers, here is their answer :
Currently, there is a little difference between the file version readable on the update file and the file version retrieved by the ZigBee stack. We will fix this error is the next files we’ll put online so that the 2 files will match. This being said, this has no impact on firmware and they will correctly work
Have a good day,
Leslie – Community Manager
Ok but for me and other : https://github.com/Koenkk/zigbee-OTA/issues/328
we have all same issue about the NLP v78 Firmware of your website, where we see our NLP Devices respond a error code 0x96: ‘invalid image’. debug 2023-06-12 23:40:57Error: Update failed with reason: ‘invalid image’
however the NLC firmware Works
Hello Clément,
I warned the teams, they planned to try to reproduce it in the next sprint starting next week. I’ll tell you once I know more
Have a good day,
Leslie – Community Manager
Hi again Clément,
I had a feedback from developers regarding NLP-78 : it correctly works on their side
Here is their answer :
Test conditions :
- Gateway Zigbee = ZUTH lab Zigbee 3.0 certification gateway (Silab based)
- NLP fw update from 54 to 78
Proof: Capture Zigbee in attachement.
Network key: 917455d7f02a733528fb7b8da7d613d1
network filter: wpan.dst_pan == 0xaabb
Conclusion:
We correctly see the plug updating at the end of the capture and it launches in v.78 (frame 34532)
They can investigate more but they will need to know the start version you use to test the update and, if possible, a Zigbee capture of your OTA
You can compare with the capture I added in attachement
Have a good day,
Leslie – Community Manager
I update from v74 (“installed_version”: 4867071, )
and v62 (“installed_version”: 4080131)
We use this version for v74
https://github.com/Koenkk/zigbee-OTA/raw/3b61e152fbdfefa00c2df4351a454b5b82734208/images/Legrand/1021-0011-4a4203-NLP-74.zigbee
and this version for v62
https://github.com/Koenkk/zigbee-OTA/raw/0bfe6a7b682fde3559b66c1d600038415868b07b/images/Legrand/1021-0011-3e4203-NLP-62.zigbee
they both dosent work
003e > v62
004a > v74
(hex to dec)
Clément,
Even from v.74 to v.78 no problem on their side
Capture in attachement :
Network key value: bfb49db8ead579a9470461697fe1bda4
Network ID filter: wpan.dst_pan == 0xfabb
It looks like a specific case linked to your gateway. Teams can’t investigate further without a ZigBee capture coming from your gateway
Have a good day,
Leslie – Community Manager
Hello Clément,
The provided ZigBee capture is too short to be correctly analyzed : only 20 seconds and just the first OTA launch. Also, it seems to be taken on Gateway side but far away from the ZigBee device (or with a sniffer not efficient enough ?). We see 0 messages coming from the ZigBee device (wpan.src16 == 0xca08 -> gives zero message) and finally we don’t see any OTA invalid image frame
Teams will need a more complete image if you want them to check what happens
Have a good day,
Leslie – Community Manager
Hi i reupload with sniffer short from the coordinator and the end devices
wpan.addr16 == 0xd3eb
Same key
i dont need a long capture because the time for the update failed its from the beginning
i have repeat 3 times the upgrade for more data
You must be logged in to reply to this topic.