Improve APIs to make adding new devices simpler so that the ZHA community can support new devices more quickly

[mkerstner]

This epic tracks the delivery of the following roadmap opportunity:

• Further shape Zigbee support by implementing missing features in ZHA while retaining choice #93

Description

Needs to be backwards compatible with existing (custom) quirks.
Critical to get right to solve the issues both ZHA and Z2M suffer from.

Deliverables/features

• wip

Completion criteria

No response

Additional context

No response

[Hedda]

For reference, the first steps towards achieving this was merged into zigpy/zha libraries that will make it in Home Assistant 2026.7 release, see:

• Bump ZHA to 2.0.0 home-assistant/core#174586

  • Move the quirks API out of zigpy zigpy/zha-device-handlers#5113
  • Migrate quirks out of zigpy and provide direct entity access zigpy/zha#762
  • Move quirks API out of zigpy zigpy/zigpy#1846

  "Our quirks API is now fully revamped: complex ZHA entities can now be created entirely within with quirks, allowing for faster community support of new devices and new complex devices."

Also see related draft PR what will add quirks v2 builder cluster binding + reporting without entity:

• Add quirks v2 builder cluster binding + reporting without entity zigpy/zha-device-handlers#5128

Note that niether ZHA integration documentation or repository description and readme files has been updated yet to reflect that change, see:

• Updated ZHA device handlers and quirks details home-assistant/home-assistant.io#46445

and

• Update zha-device-handlers repo description + all readme files to match migrations in 2.0.0 releases? zigpy/zha-device-handlers#5129

PS: IMHO it would btw also be good to make a new Home Assistant developers blog-post to high-light these major changes to ZHA! 😀