[ZHA] OTA Cluster Command Fails in UI

[HarvsG]

The problem

I am trying to use the ZHA to initiate an OTA update for a new Ikea shortcut button - this is required to unlock some new functionality (double-click function).

I used to do it via the UI in previous versions (I can't exactly remember which core version last worked) but now I get an error.

What version of Home Assistant Core has the issue?

2022.7.5

What was the last working version of Home Assistant Core?

2022.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/#ota-firmware-updates

Diagnostics information

zha-80b76ad65b871268802c6554cb65dc16-IKEA of Sweden TRADFRI SHORTCUT Button-14d1468631804939410d45f64d7b18d5.json.txt

Example YAML snippet

Using the Developer tools command seems to not fail but I can't see that the OTA actually starts. Although is I remove the args: I get the same error.

service: zha.issue_zigbee_cluster_command
data:
  ieee: "94:de:b8:ff:fe:0e:07:c6"
  endpoint_id: 1
  cluster_id: 25
  cluster_type: out
  command: 0
  command_type: client
  args:
    - 0
    - 100

Anything in the logs that might be useful for us?

➜  ~ tail -f config/home-assistant.log | egrep zigpy
  File "/usr/local/lib/python3.10/site-packages/zigpy/zcl/__init__.py", line 310, in reply
  File "/usr/local/lib/python3.10/site-packages/zigpy/types/struct.py", line 209, in serialize
  File "/usr/local/lib/python3.10/site-packages/zigpy/types/struct.py", line 177, in assigned_fields

### Additional information

_No response_

[probot-home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[puddly]

Pressing the button in the UI only worked in the past because of lenient parsing by devices, it's not standards-compliant. At the moment the service call is the only way to send the correct command to the device.

[HarvsG]

Related: #71234