ZHA: Missing args textbox to issue zigbee commands

[seblu]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

The Issue Zigbee Command UI in Manage Clusters is missing an Args textbox. As a consequence, all Zigbee commands requiring arguments are failing with an error message.

Describe the behavior you expected

An Args textbox like the box Manufacturer Code Override to specifies clusters commands args.

Here is a screenshot of the interface in Devtools->Service for the underlying ZHA service.

Steps to reproduce the issue

1.Go the device page of a ZHA device 2.Click on Manage Clusters 3.Choose a clusters with commands with args (e.g OnOff) 4. Under Clusters Commands choose a command with args. (e.g: on_with_timed_off) 5. Press Issue Zigbee Command ...

What version of Home Assistant Core has the issue?

core-2021.11.4

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 94.0.1 / Chromium 96.0

Which operating system are you using to run this browser?

Arch Linux

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[seblu]

Issue is still present in 2022.2.9.

[Hedda]

Tip; temporary workaround until these get added nativly to ZHA's UI could be to experiment with automations using the "framework for generic exposure of device configuration attributes" by @dumpfheimer as well as "ZHA Toolkit". See -> https://github.com/zigpy/zigpy/discussions/934 and/or https://github.com/mdeweerd/zha-toolkit + https://community.home-assistant.io/t/zha-toolkit-toolkit-providing-low-and-high-level-zigbee-commands-through-zha-zigpy/373346 but that is probably more work than extending zha component cover support.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[cremor]

This issue is still relevant for version 2022.6.6

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[cremor]

This issue is still relevant for version 2022.9.4

[steffen890]

Same here