IKEA E2134 OTA failing with error 1 about zigpy HOT 11 OPEN

Yeah, the most notable one I think for stability is that the max data size is actually respected. Before, when the device asked for a 64 byte chunk of the OTA file, it got a 64 byte chunk. We limit it to 40 bytes in the beta.

from zigpy.

Ping @puddly !!!

Have mailing one sniff to you with failing OTA.

from zigpy.

@mese16 Please don't cross-post "same issue" multiple times across repositories. If you aren't adding any new information or new debug logs of the entire update process, your comment isn't really contributing anything.

from zigpy.

Is this with Home Assistant 2024.3.0b0?

from zigpy.

No its on the production system thta was running HA 2024.2.0 and was having that problem and was updating all system to 2023.2.5 and its still there.
Its have one Billy EZSP 6.10.X.

I thinking letting it on the production system until HA 2024.3 is released and see if its doing the same. The problem i cant downgrading it then its updated and very likely locked bootloader like all new devices and i dont like suing one hammer for opening it (have not found and taking it apart without destroying it). If next major is working all is OK. If moving it to one of the RCP its very likely can working and we dont have any live system for looking on the problem.

Do you like have one sniff of it ? I can do it filtering one the mac layer so getting all and not other bad things.
If yes i mailing it to you plus network key in the mail.

from zigpy.

There are OTA improvements (including an increased timeout) in HA Core 2024.3.0 betas.

from zigpy.

Its requesting 63 byte

Frame 3689: 126 bytes on wire (1008 bits), 126 bytes captured (1008 bits) on 
ZigBee Encapsulation Protocol, Channel: 25, Length: 62
IEEE 802.15.4 Data, Dst: 0x073b, Src: 0x0ecd
ZigBee Network Layer Data, Dst: 0x0000, Src: 0x995e
ZigBee Application Support Layer Data, Dst Endpt: 1, Src Endpt: 1
ZigBee Cluster Library Frame
    Frame Control Field: Cluster-specific (0x01)
        .... ..01 = Frame Type: Cluster-specific (0x1)
        .... .0.. = Manufacturer Specific: False
        .... 0... = Direction: Client to Server
        ...0 .... = Disable Default Response: False
    Sequence Number: 89
    Command: Image Block Request (0x03)
    Payload
        Field Control: 0x00
        Manufacturer Code: Ikea of Sweden (0x117c)
        Image Type: Manufacturer Specific (0x1938)
        File Version: 0x01000064
            0000 0001 .... .... .... .... .... .... = Application Release: 1
            .... .... 0000 0000 .... .... .... .... = Application Build: 0
            .... .... .... .... 0000 0000 .... .... = Stack Release: 0
            .... .... .... .... .... .... 0110 0100 = Stack Build: 100
        File Offset: 0
        Max Data Size: 63

And data to and from the device in the Zigbee network layer:
ikeaotaA.txt

EDIT Was wrong frame posted !!!!

from zigpy.

I am having the same issue with HA 2024.3.0.

from zigpy.

With HA 2024.3.0 it have starting updating an looks doing it OK so liks being fixed in the last rework done in the OTA code

from zigpy.

Same issue with HA 2024.3.0.

from zigpy.

Updated to HA 2024.3.0 core (non-beta) and supervisor 2024.02.1 on HAOS. Moved 1 motion sensor within 5" of my coordinator and put batteries back in. Still fails firmware update from 0x01000057 to 0x01000064. I have 10 total Vallhorn sensors all on 57 firmware. Just figured I'd add one more data point. If it helps to send logs, appreciate a little hint on how to do so. I'm a HA newbie and it seems like I can only filter logbook by "firmware" entity and can't seem to figure out where the logging is for the failed firmware update attempts.

from zigpy.