UPDATE: ESPHome firmware now has a native Zigbee component with initial support for building Zigbee end-devices with ESP32 or nrf52 microcontrollers

[Hedda]

FYI, heads-up to ZHA/zigpy (and Zigbee2MQTT) developers as Zigbee gateway compatibility testing/verification and code reviews is wanted for this initial native unified Zigbee end-device building support in the ESPHome microcontroller firmware framework which now looks to be very close to merger into into mainline ESPHome, (and since this is initially only the bare-minimum Zigbee in ESPHome I assume they are also willing to take in feedback and discuss future standardization via Discord too).

In summery; tomaszduda23 and luar123 (who both been working on Zigbee support for ESPHome separately for a couple of years) are now more or less fully aligned and have agreed on how the initial Zigbee config with platform/component abstraction should be handled/formatted at a high-level for ESPHome config to be platform-independent, and as such they both each submitted matching pull requests for initial bare-minimum Zigbee support on nRF52 and ESP32 microcontrollers with IEEE 802.15.4-based radios as ESPHome platforms respectively. You can check those out those PRs, see:

• [nrf52,zigbee] add support for binary_input esphome/esphome#11535

or

• [nrf52, zigbee] Add sensor esphome/esphome#12187

and

• [zigbee][core] Add support for Zigbee binary sensors on ESP32 H2 and C6  esphome/esphome#11553

Plus the matching initial documentation pull requests here for ESPHome docs:

• Zigbee esphome/esphome.io#5526

and

• Add support for Zigbee binary sensors on ESP32 H2 and C6 esphome/esphome.io#5582

The zigbee component allows exposing supported ESPHome components over a Zigbee network to Home Assistant via Zigbee2MQTT or ZHA. Due to the limitations of the Zigbee protocol, only basic properties are exposed. Additional properties must be configured manually in Home Assistant.

Example entry for config.yaml in ESPHome:

# Example config.yaml
esphome:
  name: zigbee_test

esp32:
  board: esp32-h2-devkitm-1
  framework:
    type: esp-idf

zigbee:

binary_sensor:
  - platform: gpio
    pin:
      number: 9
    name: but1
    report: force
  - platform: gpio
    pin:
      number: 8
    id: but2
    on_click:
      min_length: 5s
      max_length: 20s
      then:
        - zigbee.factory_reset

PS: Both tomaszduda23 and luar123 also still have their previous work and pulls requests open that offer much more extensive and comprehensive Zigbee device types (which also have much more information and better overview of the project scopes), but I guess that if the two pull requests linked above are accepted and merged into ESPHome mainline then each of their comprehensive work (linked below) will be partially rewritten to align with the new agreed upon standard and formatting. See these for more background information:

• [nrf52, zigbee] zigbee binary_sensor, switch, time, sensor and number esphome/esphome#7340

and

• https://github.com/luar123/zigbee_esphome

[Hedda]

Update: pull requests that added initial Zigbee end device support for the nRF52 platform has now been merged into ESPHome:

• [nrf52,zigbee] add support for binary_input esphome/esphome#11535
  • [nrf52, zigbee] Add sensor esphome/esphome#12187
  • [nrf52,zigbee] add support for binary_input esphome/esphome#11535
  • [nrf52, zigbee] OnlyWith support list of components esphome/esphome#11533

That means that the next upcoming ESPHome release (scheduled for release as ESPHome 2026.1.0 in a couple of weeks from now) will have have initial Zigbee end device support for the nRF52 platform.

• https://next.esphome.io/components/zigbee/

Note that the matching pull request that will add initial Zigbee end device support for the ESP32 platform has not yet merged into ESPHome:

• [zigbee][core] Add support for Zigbee binary sensors on ESP32 H2 and C6  esphome/esphome#11553

Again, also be ware that both tomaszduda23 and luar123 also still have their previous work and pulls requests open that offer much more extensive and comprehensive Zigbee device types (which also have much more information and better overview of the project scopes), but I guess that if the two pull requests linked above are accepted and merged into ESPHome mainline then each of their comprehensive work (linked below) will be partially rewritten to align with the new agreed upon standard and formatting. See these for more background information:

• [nrf52, zigbee] zigbee binary_sensor, switch, time, sensor and number esphome/esphome#7340

and

• https://github.com/luar123/zigbee_esphome

[Hedda]

FYI; ESPHome 2026.1.0 has now been released with a Zigbee End Device component based on nRF SDK supporting nRF52 platform:

• https://esphome.io/components/zigbee/

"The zigbee component allows exposing supported ESPHome components over a Zigbee network to Home Assistant via Zigbee2MQTT or ZHA. Due to the limitations of the Zigbee protocol, only basic properties are exposed. Additional properties must be configured manually in Home Assistant. Each ESPHome entity consumes one Zigbee endpoint. Because of a limitation in Zigbee2MQTT, at least two endpoints are required. The maximum number of supported endpoints is eight."

So far in ESPHome 2026.1 just adds initial support but it already features supports for sensor, binary sensor, and switch functions:

• https://esphome.io/changelog/2026.1.0/

Quote below from the release notes:

Zigbee Support for nRF52

ESPHome now supports Zigbee on nRF52 platforms, bringing a new connectivity option alongside WiFi, Bluetooth, and Thread:

• Binary sensor support - Expose GPIO states via Zigbee (#11535)
• Sensor support - Expose ESPHome sensors via Zigbee’s Analog Input cluster with automatic unit mapping ([#12187]([nrf52, zigbee] Add sensor esphome/esphome#12187))
• Switch support - Control ESPHome switches via Zigbee as binary output (#13083)
  wipe_on_boot: once - Wipe network settings only on first boot, preserving connections after OTA updates
• Framework version support - Configure nRF-SDK version with experimental support for SDK 2.9.2 and 3.2.0 (#12489)

Future of Zigbee End Device support in ESPHome:

Zigbee support in ESPHome is currently available only on nRF52 platforms but there is an open PR to also add ESP32 support as well:

• [zigbee][core] Add support for Zigbee binary sensors on ESP32 H2 and C6  esphome/esphome#11553

Also be ware that both tomaszduda23 and luar123 also still have their previous work and and side-development with pulls requests open as drafts that offer much more extensive and comprehensive Zigbee device types (which also have much more information and better overview of the project scopes), but I guess that if the two pull requests linked above are accepted and merged into ESPHome mainline then each of their comprehensive work (linked below) will be partially rewritten to align with the new agreed upon standard and formatting.

See these for more background information:

• https://github.com/luar123/zigbee_esphome

and

• [nrf52, zigbee] zigbee binary_sensor, switch, time, sensor and number esphome/esphome#7340

[Hedda]

FYI, the initial pull request by luar123 to add support for Zigbee binary sensors on ESP32 H2 and ESP32-C6 has finally been merged to ESPHome mainline so should be included in next month’s ESPHome 2026.5.0 release (to be relesed some time in May of 2026):

• [zigbee][core] Add support for Zigbee binary sensors on ESP32 H2 and C6  esphome/esphome#11553

Should be noted that a recent major change in Espressif’s upstream ESP Zigbee SDK will relativly soon require larger under-the-hood changes in the underlying zigbee_esphome component library that be built to enable this -> https://github.com/luar123/zigbee_esphome

Originally posted by luar123 in esphome/esphome#11553 (comment)

I could bring forward more PRs for additional options, sensor, switch and number components quite fast. However, espressif released a version 2.0 zigbee sdk a few days ago. Currently I am implementing it in my external component to test it (this will probably take a few days). If it works well we should consider to update here, or in a separate PR, before the release because they change the zigbee partition type. Overall, changes are large, they dropped zboss in favor of their own stack and integration with esp-idf seems much better. Functional changes are small, so review effort should be low, but all functions/types/macros change names.

For reference see:

• https://github.com/espressif/esp-zigbee-sdk/blob/main/RELEASE_NOTES.md

  • https://docs.espressif.com/projects/esp-zigbee-sdk/en/latest/esp32/migration-guide/v2.x/overview.html

    • https://docs.espressif.com/projects/esp-zigbee-sdk/en/latest/esp32/migration-guide/index.html

      • ESP Zigbee SDK 2.x Release espressif/esp-zigbee-sdk#803

In summery:

• v1.x is based on ZBOSS

  • LTS (Long-Term Support) version, which is under maintenance (bug fixes only, no new features).
  • It is stable for existing products.

• v2.x is based on Espressif proprietary Zigbee stack

  • A fully self-developed Zigbee stack provides greater flexibility and better capability to meet the evolving requirements of the Zigbee market
  • Full control of the entire stack, enabling better hardware–software adaptation
  • Faster iteration for new features (e.g., Zigbee 4.0, direct) and bug fixes
  • Improved code efficiency and reduced code size

• Espressif employee xieqinan wrote that Espressif will provide an example demonstrating how to perform OTA from v1.x to v2.0 as soon as possible. In the meantime, we can review their migration guide to understand the differences between v1.x and v2.x.

• xieqinan also wrote that Espressif Zigbee 4.0 certification testing for v2.x is being planned and will be completed as soon as possible.

[Hedda]

FYI, ESPHome 2026.5.0 was just released (May 2026) and now also includes Zigbee End Device support for the ESP32 platform in ESPHome:

• https://esphome.io/changelog/2026.5.0/#zigbee-expanded-to-esp32-h2-and-c6

  luar123 brought ESP32-based Zigbee support to ESPHome in #11553, porting the standalone zigbee_esphome external component into core. The implementation runs on the radio-equipped ESP32-C6 and ESP32-H2 variants and publishes ESPHome binary_sensor entities as Zigbee binary_input clusters, recognized automatically by ZHA and zigbee2mqtt. Zigbee router and end devices are supported.

That release also extend and improve its existing Zigbee support on the nrf52 platform as well (including adding Zigbee Router support):

• https://esphome.io/components/zigbee/

Note! luar123 has since then also begun working experimental (Espressif) zigbee-sdk v2.0 implementation in a "v2" branch in his repo:

• https://github.com/luar123/zigbee_esphome/tree/v2

  • Support for esp-zigbee-sdk v2.0 luar123/zigbee_esphome#96

    • What does it mean to this project that Espressif’s ESP Zigbee SDK 2.0 replaces ZBOSS with a new propriatory Zigbee stack? luar123/zigbee_esphome#93

Important!

To improvde this help to collect working cluster definitions in his discussion thread there:

• Collect Zigbee cluster definitions luar123/zigbee_esphome#22

  If something is not working please check the troubleshooting section first. Config validation is not complete. Always consult Zigbee Cluster Library for cluster definitions

[trilu2000]

Has someone a definition for a cover?
As an Actor: Up, Stop, Down, set Position.
As a Sensor: Control Information (moving up, moving down, idle) and current Position

[Hedda]

@trilu2000 recommend that you try asking here instead-> https://github.com/luar123/zigbee_esphome/discussions