Suggest rename “Quirk” under Device info in the ZHA integration UI to “Zigbee Device Handler”

[Hedda]

Please consider renaming "Quirk" to instead be called "Zigbee Device Handler" (or "Device Handler") in UI/GUI of the ZHA integration.

This is a late frontend feature request for the month of 'What the Heck' (WTH) that also fits under request for localization improvements.

Not even sure if "quirks" is the correct terminology(?) but I feel that from the end-users perspective it should be called "Zigbee Device Handlers" or just "Device Handlers"in the UI (as in a handler for that Zigbee devices) is better end-user terminology and might be a little more self-explanatory for ZHA users than having it be named only "quirks" in the UI.

The library in the zigpy project that serve those to the ZHA integration is even called "ZHA Device Handlers":

• https://github.com/zigpy/zha-device-handlers/

Other alternative terminology terms that could probably be equally valid to use would be "Device Converter" or "Device Translator" as a quirk's function is to convert or translate firmware quirks into standard Zigbee specs.

https://github.com/zigpy/zha-device-handlers/blob/dev/README.md#what-the-heck-is-a-quirk

Anyway, I believe that any of the terms "Device Handler", "Device Converter", or "Device Translator" should also be much better sentenced for localization if easier to translate than "quirk" as a word on its own? And again, it is also consistant with the library name.

Though using if "ZHA Device Handler", "ZHA Device Converter", or "ZHA Device Translator" was used in the UI/GUI then that could maybe lead to that term being used by more ZHA users for increased community knowledge even if makes for a longer string(?).

Regardless I feel that simply using the word "quirk" alone without any related context in the same sentence is both nondescriptive (as well as not being industry standard terminology) so calling it that in the UI/GUI is really not helping the end-user in any way.

Quirks as terminology for the internal function of the zigpy library and zha integration code can (and will) of course still continue to be used terminology internally in core and for the development of quirks for ZHA.

References:

• https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

• https://github.com/zigpy/zha-device-handlers/

• https://github.com/zigpy/zha-device-handlers/blob/dev/README.md#what-the-heck-is-a-quirk

FYI, "device handler" and "custom device handler" terminology is also used by Samsung SmartThings (classic) app and dev interface:

• https://github.com/codersaur/SmartThings
  • https://www.google.com/search?q=smartthings+device+handlers
  • https://www.google.com/search?q=smartthings+device+handler
• https://www.google.com/search?q=Zigbee+Device+Handlers

PS: Zigbee2MQTT (and zigbee-herdsman) on the other hand instead use "Converter" as terminology for "Zigbee-Herdsman Converters":

• https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html