Repository navigation
Replies: 4 comments 5 replies
|
Thx for collecting and providing Infos. We had already a quick look at the espressif zigbee stuff. To early to say anything more. It is on our list to check ;-) |
|
I do have an Espressif C6/H2 board to allow some testing. However I'm hesitant to invest time in Zigbee support, considering there is already plenty of options with ZNP/EZSP. I have the feeling that with C6/H2, we should now target Thread support |
|
IMHO, while Matter over Thread might be the future it will take many years to catch up with where Zigbee devices are today, both feature-wise and market adoption. There are already thousands of inexpensive Zigbee devices on the market today, and also note that the Matter device type is still limited and does not allow custom manufacturer clusters and attributes, so it will take years for the new Matter standard to be extended and mature in a way to compete with the flexibility of the existing Zigbee specifications. |
|
Tasmota supports zigbee, and will do in future. The two Tasmota supported zigbee chip familys are widley available and have good support. Tasmotas goal is not to support every chip especially when it brings no new features. There is a higher chance that the new feature Thread will be added, than adding support for another zigbee chip. |
Yeah I totally understand that, however it is the only Zigbee radio that is built-into ESP32 chips, and I guess that can be called a feature.
Indeed, and that is also very understandable. Especially with the fact that if using OpenThread then it is the same CLI/API on all hardware. |
I believe that that is only partially true. Yes sadly Espressif has chosen to make their initial implementation not so open-source friendly, however on the positive note it has potential because Espressif at least chose to go with the ZBOSS Zigbee stack which I understand is very open-source upstream, and since the same the ZBOSS Zigbee stack has also been adopted other by several others, including Nordic Semiconductor and Telink. Tip is to check out the "nRF52840 Dongle" (nRF52840 SoC based USB dongle for developers and tinkerers) made by Nordic Semiconductor. So an option could be to develop using Nordic Semi's nRF5 series hardware (nRF52840 SoC based development boards) and documentation instead, then port that, as I understand that Nordic Semiconductor has both great developer documentation as well as inexpensive hardware designed for developers that are readily available. https://www.nordicsemi.com/Products/Development-hardware/nrf52840-dongle https://www.nordicsemi.com/Products/nRF52840 https://www.nordicsemi.com/Products/Development-hardware/nrf52840-dk https://docs.nordicsemi.com/category/zigbee https://www.nordicsemi.com/Products/Development-software/nrf5-sdk-for-thread-and-zigbee https://infocenter.nordicsemi.com/index.jsp PS: There are also a few ESP32-C3 boards out there that feature Telink TLSR8258 multi-protocol wireless SoC with ZBOSS Zigbee Stack, (like example the LilyGO T-Zigbee board), however, I believe that Telink do not provide as good documentation as Nordic Semiconductor. There are also radio modules with Telink TLSR8258 available from Ebyte (E180-Z5812SP) |
Probably this is a problem, like it is currently when using BLE and WiFi together. It is not working perfect since the HF hardware sharing is problematic. So for a good solution it is better to have a dedicated zigbee chip, just doing the zigbee job. Time will show if well working solutions with the C6 are possible where wifi and zigbee is handled from the C6. Thread has the same problem, so it might be necessary to use the C6 additionally to an existing ESP. About existing hardware boards, just soldering chips on a PCB makes no working solution. |
Why should the Open Source community support such a unfriendly decision? Honestly I don't care which way the choose, when the have the chance to provide the source code. |
|
Texas Instruments and Silicon Labs are also proprietary Zigbee stacks/solutions that are mostly closed source, they all more or less provide CLIs and APIs interfaces so that third parties can utilise them. ZBOSS is the one that is the most open and the only one that is hardware-independent. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
@s-hadinger Do you have any plans on looking into native ZBOSS Zigbee stack support for Zigbee2Tasmota on ESP32-C6 built-in radio?
Not sure if any use to help achieve native ZBOSS Zigbee support in Tasmota, but FYI, as an alternative to the upstream ESP-IDF Zigbee library, it looks like @P-R-O-C-H-Y is planning on porting the ESP-IDF Zigbee library and ZBOSS libraries to be available as Arduino library/libraries for ESP32. Check it out here:
espressif/arduino-esp32#8807
espressif/esp32-arduino-lib-builder#142
espressif/arduino-esp32#8844
espressif/esp32-arduino-lib-builder#146
Would it be possible to make Zigbee2Tasmota (Z2T) compatible with a serial interface for Espressif's "esp-zboss-lib" (ESP ZBOSS 3.0 Libraries) or other ZBOSS Zigbee library to allow using Zigbee2Tasmota (Z2T) as a gateway with no other hardware and/or serial-server on ESP32-C6 for Serial-over-IP pass-through proxy (similar to ser2net) to enable TCP streaming of the serial communication bridge to allow it to be used as a network-attached remote Zigbee Coordinator so that the Home Assistant's ZHA integration can connect to it via a socket (socat) using the experimental zigpy-zboss?
An open question asked to Espressif that might be a showstopper for Zigbee2Tasmota (Z2T) compatible is if Espressif's current ZBOSS Zigbee libraries for ESP32-C6 currently only support RCP (Radio Co-Processor) mode and not Zigbee NCP (Network Co-Processor) host? Otherwise you would have to also implement RCP (Radio Co-Processor) mode support, however, that might not be impossible if supported upstream, or?
espressif/esp-zboss-lib#4
espressif/esp-zigbee-sdk#124
For reference, Tasmota's Zigbee2Tasmota (Z2T) already supports Texas Instruments ZNP and Silicon Labs EZSP Zigbee stacks/interfaces with respective Zigbee Coordinator adapter running Zigbee firmware in NCP (Network Co-Processor) mode:
https://tasmota.github.io/docs/Zigbee/
Espressif of ESP32 fame joined ZOI (ZBOSS Open Initiative) more than a year ago and has released ESP ZBOSS 3.0 binary libraries for ESP-IDF supporting the Zboss Zigbee 3.0 stack for ESP32-C6 and ESP32-H2 SoCs which both features embedded 802.15.4 radio for Zigbee (and Thread) support, (with the major difference being that the ESP32-H2 hardware does not have WiFi and only one core core)
https://github.com/espressif/esp-zigbee-sdk
https://github.com/espressif/esp-zboss-lib
https://components.espressif.com/components/espressif/esp-zboss-lib
FYI, Espressif has also released a couple of development kits based on ESP32-H2 as reference hardware for such and similar solutions:
https://www.cnx-software.com/2023/06/20/espressif-esp-thread-border-router-board-combines-esp32-h2-esp32-c3-wireless-chips/
That is a new ESP32-H2 + ESP32-C3 combo development board kit marketed as ESP Thread Boarder Router / Zigbee Gateway with an optional Ethernet daughter-board/sub-board sold separately (which would normally be recommended as streaming serial communication over WiFi does not work well), although that Ethernet daughter-board/sub-board is based on WIZnet W5500 which uses a non-standard SPI interface instead of RMII so might not yet be supported in Tasmota)(?).
https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_br
https://openthread.io/guides/border-router/espressif-esp32
An earlier two-board ESP Thread Border Router / Zigbee Gateway solution that combined separate ESP32-C6 and ESP32-H2 boards was previously available as an example project for reference to achieve the same result:
With either of those hardware combinations it should be possible to make a network-attached "Zigbee Coordinator" adapter products based on Tasmota (or ESPHome ) similar to TubesZB Zigbee Gateways with ESP32-C6 or ESP32-H2 that simply tunnel/passthrough the serial connection to the serial interface for Espressif's "esp-zboss-lib" (ESP ZBOSS 3.0 Libraries) from Home Assistant's ZHA integration.
ESP ZBOSS 3.0 Libraries
This repository contains binary libraries supporting the Zboss Zigbee 3.0 stack for ESP32 series chips.
Packages from this repository are uploaded to Espressif’s component service. You can add them to your project via idf.py add-dependency
More information about idf-component-manager can be found in Espressif API guide or PyPi registry.
There now looks to be some Zigbee examples in Espressif’s IoT Development Framework (ESP-IDF):
Those examples include; Zigbee coordinator ("light coordinator"), "Zigbee RCP (radio co-processor"), and "Zigbee gateway":
"light_coordinator is a light coordinator example demonstrating Zigbee Coordinator role. It provides a formation of the Zigbee network. It runs on an 802.15.4 SoC like ESP32-H2. For more details to see the example readme file."
https://github.com/espressif/esp-idf/tree/master/examples/zigbee/esp_zigbee_gateway
https://github.com/espressif/esp-idf/tree/master/examples/zigbee/esp_zigbee_rcp
Wondering if "RPC" works similarly to Silicon Labs RPC which works like a dumb radio requiring external ESP ZBOSS 3.0 libraries?
"This test code shows how to configure Zigbee rcp (radio co-processor) device. Rcp doesn't function alone, it needs to work together with Zigbee gateway (see esp_zigbee_gateway example)"
"After rcp starts up, it will send its own MAC ieee address and Zigbee stack version number to the Zigbee gateway and start working together with Zigbee gateway via UART communication"
ESP32-H2 was apparently early on even certified as a “Zigbee Compliant Platform” by the CSA:
https://www.espressif.com/en/news/ESP32-H2_Thread_and_Zigbee_certified
https://www.espressif.com/sites/default/files/ESP32-H2%20Zigbee%20Compliant%20Platform%20Certification.pdf
Type of Device: Zigbee Compliant Platform
Zigbee PRO Feature Set (2017)
Manufacturer: Espressif Systems (Shanghai) Co., Ltd.
Model Identification: ESP32-H2
Firmware Version: V1.0
Hardware Version: V1.0
Certification Date: October 20, 2021
Certification ID Number: ZIG21030ZCP27315-24
External links, documentation, and other development references
All reactions