How about adding a web-link in ZHA’s UI in order to make it a little more streamlined and easier for each end-user to submit a “device support request” if want zha-quirk to expose additional attributes as entities for Zigbee devices if not yet fully supported/exposed in ZHA’s user interface (frontend)?
Use-case and back-story; for new or unsupported Zigbee devices that do not yet expose all expected device feature/function attributes as entities in the UI of the ZHA integration (native Zigbee gateway component built-into Home Assistant) end-users should first search and submit device support requests under issues in the “ZHA Device Handlers” repository on GitHub if they wish to request that community developers begin to help look into what is needed to create or modify “zha-quirks” to add code to allow custom support for some Zigbee device’s additional or non-standard feature/function attributes.
Do you think that the submission of device signature + diagnostic information could be scripted or in a other way made simpler so it is easier to submit a new (non-duplicate) “device support request” to the zha-device-handlers GitHub repo?
As it stands today I believe that many ZHA end-users find this process to hard as it is as therefore simply refrain from even submitting a new “device support request” to GitHub if their device does not already expose feature/function attribute as an entity, and many ZHA users instead only make a post to the Zigbee section of Home Assistant’s community forum, and there they might just get a reply saying that the user should try migrating to Zigbee2MQTT (Z2M) instead as it has larger community and is as such often quicker to get support for new and unsupported Zigbee devices.
I believe a first-step to make this become a non-problem could be to make it easier to somehow make it easier for ZHA end-user who report or complains in theses forums to search and submit new device support requests on GitHub for tracking and dicussions there, including subission of the required require the device signature + diagnostic information.
PS: It is also relatively complicated for end-suers to test custom zha-quirks, see this guide for reference: