You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FYI, ESPHome very close now to getting initial native Zigbee component to allow building DIY Zigbee end-devices with both ESP32 and nrf52 microcontroller
#29916
FYI, just a heads-up to Zigbee2MQTT developers (and ZHA/zigpy developers) as 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:
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.
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:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
FYI, just a heads-up to Zigbee2MQTT developers (and ZHA/zigpy developers) as 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:
and
Plus the matching initial documentation pull requests here for ESPHome docs:
and
The
zigbeecomponent 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:
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:
and
Beta Was this translation helpful? Give feedback.
All reactions