Nordic Semi nRF52840 chips with ZBOSS Zigbee stack now usable as Zigbee Coordinator for the ZHA integration via new radio library for zigpy

Hedda · May 10, 2023, 9:10pm

You can now use a Nordic Semiconductor nRF52840 dongle as Zigbee Coordinator radio adaper for the ZHA integration via zigpy-zboss:

https://github.com/kardia-as/zigpy-zboss

Still unofficial and bleeding-edge experimental so need to manually add radio library to ZHA in HA. See:

github.com/zigpy/zigpy

[SUGGESTION] Use Nordic nRF52840 chip ...

opened 05:49PM - 24 Apr 20 UTC

captcha1

The Nordic nRF52840 chip is inexpensive and has Zigbee ZBOSS support. The [pc…a10059](https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52840-Dongle) is only $10. Nordic has an SDK with different [Zigbee architectures (entire stack or just MAC layer)](https://infocenter.nordicsemi.com/topic/sdk_tz_v4.0.0/zigbee_architectures.html) ... and [example code](https://infocenter.nordicsemi.com/topic/sdk_tz_v4.0.0/zigbee_cli_wrapper.html) ... and [precompiled examples](https://infocenter.nordicsemi.com/topic/sdk_tz_v4.0.0/thread_zigbee__intro.html#thread_zigbee_precompiled_examples) [MakerDairy sells similiar USB dongles in a nice case](https://store.makerdiary.com/collections/frontpage)

Should make usable to use either nRF52840 USB dongle or nRF52840 dev kits with correct firmware.

nRF52840 Dongle only costs around $10 USD today:

nRF52840 DK (Development Kit for developers) cost about $60 USD today:

Anyway, ZBOSS Zigbee stack support has the potential to be a big deal since its firmware is open-source and hardware independent:

https://dsr-zoi.com

https://dsr-iot.com

PS: Perhaps more interesting is that if and when this zigpy-zboss library gets developed further then you could be able to use ESP32-C6 / ESP32-H2 SoCs with ESPHome as Zigbee adapter for ZHA:

github.com/esphome/feature-requests

Zigbee/Thread support on the new upcoming ESP32-H2 variant?

opened 05:50PM - 03 Sep 21 UTC

levihb

enhancement

**Describe the problem you have/What new integration you would like** A new variant of the ESP32 [was announced last month](https://www.espressif.com/en/news/ESP32_H2), the ESP32-H2. It supports 802.15.4 and therefore Zigbee and Thread, as well as BLE, and now runs on a RISC-V architecture which should be a lot more efficient. It also still supports WiFi. This looks super interesting because it will finally give home users a way to easily build Zigbee/Thread versions instead of WiFi ones. I think ESPHome supporting this would be a brilliant step forward. **Please describe your use case for this integration and alternatives you've tried:** There are no alternatives to ESPHome for Zigbee as far as I know? Or really any simple development environments for home users. **Additional context** Of course the H2 isn't out yet. But I think it'd be good to get a discussion on this going before it is released. Zigbee is definitely a lot more friendly to larger home installations in many ways. Support for battery operated end Zigbee devices would also be a huge leap forward. And I would think that should be possible on the new H2.

github.com/zigpy/zigpy

[REQUEST] esp-zigbee radio library for zigpy to use with esp-zboss (DSR ZBOSS Zigbee stack) on Esspresif ESP32-C6 and ESP32-H2 SOCs?

opened 11:10AM - 30 Sep 22 UTC

Hedda

Open discussion about possibility of an esp-zigbee radio library for zigpy to us…e esp-zboss via serial interface, what do you think? For zigpy projects to use ESP32-C6/ESP32-H2 based ESP32 radio module or ESP32 DevKit development board as a Zigbee radio. Espressif joined ZBOSS Open Initiative (ZOI) + released ESP32 SoCs with 802.15.4 radios via a variant of DSR ZBOSS Zigbee stack. https://dsr-zoi.com https://www.prweb.com/releases/espressif_joins_zboss_open_initiative_zoi_a_community_for_royalty_free_zigbee_pro_stack_software/prweb18263163.htm https://dsr-zboss.com/#!/updates/zboss-open-initiative-in-2021 **Update!** A newer "**ESP32-C6**" SoC, module and development board have now also been launched with **WiFi 6**, BLE 5.0, and 802.15.4, including Zigbee and OpenThread, all on the same chip. (compared to"**ESP32-H2**" SoC which do not support WiFi). (Note that this request is somewhat similar to other requests posted about zigpy radio library for [Nordic Semiconductor nRF5 which has also joined ZBOSS Open Initiative](https://blog.nordicsemi.com/getconnected/why-has-nordic-semiconductor-joined-the-zboss-open-initiative) and will in the future also have the ability to run a variant of DSR ZBOSS Zigbee stack, though expect that both Espressif and Nordic Semiconductor will respectively wrap that in their own custom Serial/CLI interfaces -> https://github.com/zigpy/zigpy/issues/394 ). https://www.espressif.com.cn/en/news/ESP32-C6_Available https://espressif-docs.readthedocs-hosted.com/projects/espressif-esp-dev-kits/en/latest/esp32c6/esp32-c6-devkitc-1/index.html **Background:** Just over a year ago Espressif announced a "**ESP32-H2**" SOC variant which has an 802.15.4 + Bluetooth radio (instead of a Wi-Fi radio) and now it looks like Espressif has now made its Zigbee software for it public, (based on DSR ZBOSS stack as part of "ZBOSS Open Initiative", a.k.a. ZOI), though it seems like Espressif themselves are currently focusing on providing an all-in-one embedded Zigbee gateway and Zigbee/Thread to Matter bridge implementation (as a “One-Stop Matter Solution” with two-SoC based gateway/bridge implementation consisting of an ESP32-H2 SoC for Zigbee/Thread using in combination with an ESP32-S3 SoC for Wi-Fi/Ethernet bridging). However what is needed for a matching zigpy radio library is for Espressif to also provide a serial interface like UART or SPI that other native projects can use to directly communicate with the Zigbee stack / Zigbee Coordinator radio, as then those applications which depends on [zigpy](https://github.com/zigpy/zigpy) could make use of use a ESP32-H2 SoC as a Zigbee Coordinator radio natively, including applications such as [Home Assistant's ZHA integration](https://www.home-assistant.io/integrations/zha), the [Zigbee Plugin for Domoticz](https://www.domoticz.com/wiki/ZigbeeForDomoticz), and the [Zigbee Plugin for Jeedom](https://doc.jeedom.com/en_US/plugins/automation%20protocol/zigbee/) that are all using [zigpy libraries](https://github.com/zigpy/) as dependencies, (and the same serial interface could also be used in similar Zigbee frameworks such as [zsmartsystems.zigbee](https://github.com/zsmartsystems/com.zsmartsystems.zigbee) and [zigbee-herdsman](https://github.com/Koenkk/zigbee-herdsman) used as dependecies in other popular home automation applications such as [OpenHAB](https://www.openhab.org/addons/bindings/zigbee/), [IoBroker](https://github.com/ioBroker/ioBroker.zigbee) and [Zigbee2MQTT)](https://www.zigbee2mqtt.io/). ESP32-H2 SoC (and ESP32-H2 DevKitC Board) + ZBOSS Open Initiative (ZOI) + Zigbee certification announcements: https://www.espressif.com/en/news/ESP32_H2 https://www.espressif.com/en/news/ESP32-H2_Thread_and_Zigbee_certified https://en.dsr-corporation.com/news/espressif-joins-zoi esp-zigbee: https://github.com/espressif/esp-zigbee-sdk https://github.com/espressif/esp-zigbee-sdk/tree/main/components/esp-zigbee-lib https://github.com/espressif/esp-zboss-lib/ https://components.espressif.com/components/espressif/esp-zboss-lib https://github.com/espressif/esp-idf/tree/master/examples/zigbee https://github.com/espressif/esp-idf/tree/master/examples/zigbee/esp_zigbee_rcp https://github.com/espressif/esp-idf/tree/master/examples/zigbee/esp_zigbee_gateway esp-protocols including esp modem (for AT commands, etc.), esp websocket client, mDNS (Zeroconf and DNS-SD), Asio, and more: https://espressif.github.io/esp-protocols/ https://github.com/espressif/esp-protocols https://github.com/espressif/esp-protocols/tree/master/components/esp_modem https://github.com/espressif/esp-protocols/tree/master/components/esp_websocket_client https://github.com/espressif/esp-protocols/tree/master/components/mdns https://github.com/espressif/esp-protocols/tree/master/components/asio Other indirectly related tools: https://github.com/espressif/esptool https://github.com/espressif/openocd-esp32 https://github.com/espressif/esp-usb-bridge esp-thread: https://openthread.io/guides/border-router/espressif-esp32 https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_rcp https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_cli https://github.com/espressif/esp-thread-lib https://github.com/espressif/esp-thread-br https://openthread.io/vendors/espressif esp-matter (Matter / Project CHIP): https://medium.com/the-esp-journal/matter-bridge-for-non-matter-devices-d3b7f003a004 **https://blog.espressif.com/matter-thread-border-router-in-matter-240838dc4779** https://docs.espressif.com/projects/esp-matter/en/main/esp32/index.html https://docs.espressif.com/projects/esp-matter/en/main/esp32/ https://github.com/espressif/esp-matter/tree/main/examples/zigbee_bridge https://github.com/project-chip/connectedhomeip/tree/master/examples/lighting-app/esp32 https://www.espressif.com/en/news/ESP_Matter_Solution https://www.espressif.com/en/solutions/device-connectivity/esp-matter-solution https://github.com/espressif/esp-matter "**_We offer both Matter-Zigbee and Matter-BLE Mesh bridge solutions with full functional software SDK support. A Matter-Zigbee Bridge uses two SoCs (Wi-Fi + 802.15.4), they are connected via a serial interface like UART or SPI, while a Matter-BLE Mesh Bridge can be done on single SoC with both Wi-Fi and BLE interfaces._**" ![image](https://user-images.githubusercontent.com/6320001/193288233-f01d99aa-031d-4e12-902c-5bfa36dfaf7d.png) ![image](https://user-images.githubusercontent.com/6320001/193288824-3d642559-6b1a-4888-8164-b4a3a2230a69.png) PS: I think esp-zigbee support is of interest for ESP32-based Zigbee remote adapter bridges, like ex. Tube's and ZigStar Gateways: https://github.com/tube0013/tube_gateways https://github.com/mercenaruss/zigstar_gateways https://github.com/codm/cc2652p2-tcp-zigbee https://github.com/cyijun/OpenZ3Gateway

Hedda · July 21, 2023, 1:37pm

FYI, @DamKast committed fixes to GitHub - kardia-as/zigpy-zboss and released zigpy-zboss v1.0.2

https://github.com/kardia-as/zigpy-zboss/releases

https://pypi.org/project/zigpy-zboss/

Note that this is still experimental and not yet included in the zha component in Home Assistant core, so if you want to test using an Nordic Semi nRF52840 dongle as a Zigbee Coordinator then you need manually patch directly in the Home Assistant core, modify the source by patching the ZHA component (”zha” under components) inside it to include zigpy-zboss as well as add ”zboss” to the ZHA manifest (manifest.json) as a new radio type, in the same way that the zha component there already includes for example zigpy-znp and ”znp” radio type in ZHA manifest → https://github.com/home-assistant/core/tree/dev/homeassistant/components/zha → https://github.com/home-assistant/core/blob/530556015f98097664d02372701efb15442c6949/homeassistant/components/zha/manifest.json

Alternatively, I believe you can copy the ZHA component and use that as a custom component itself to override the built-in core integration or maybe perhaps even rename it? → Creating your first integration | Home Assistant Developer Docs (a tip, if you try to do that, is to know that the manifest.json file has support for a version key which you could set to a higher version than one that comes with the core and thus it will not overwrite it on updates.

Hedda · August 15, 2023, 10:46am

FYI, in related news; noticed grobasoz added some Zigbee CLI/RCP firmware images for ESP32-C6:

zigbee-firmware/ESP32-C6 at master · grobasoz/zigbee-firmware · GitHub
- zigbee-firmware/ESP32-C6/ZigbeeCLI at master · grobasoz/zigbee-firmware · GitHub
- zigbee-firmware/ESP32-C6/Zigbee_RCP at master · grobasoz/zigbee-firmware · GitHub

ESP ZBOSS 3.0 Libraries (esp-zboss-lib from Espressif) is also based on DSR’s ZBOSS Zigbee stack so if Espressif’s ZBOSS 3.0 Libraries CLI is compatible with the standard ZBOSS CLI then in theory you should be able to make a DIY network-attached remote Zigbee Coordinator adapter setup (i9n a setup similar to Espressif’s new ESP32-H2 + ESP32-C3 combo development board kit) where you have for example ESP32-S3 with ESPHome or Tasmota running serial proxy server and the and it connected to a the ESP32-C6 running only Zigbee CLI firmware so that it just acts as a Zigbee radio adapter when connected via serial using CLI interface.

I have not tested this and again I have no idea if Espressif’s ZBOSS 3.0 Libraries CLI is compatible with the standard ZBOSS CLI So no idea how or if these firmware images from grobasoz would work or not (but grobasoz is at least well known in Home Assisistant’s ZHA community for providing good unofficial Zigbee NCP firmware images for a wide range of Silicon Labs based Zigbee Coordinator adapters).

PS: Espressif also has an earlier two-board ESP Thread Border Router / Zigbee Gateway solution that combined separate ESP32-S3 and ESP32-H2 boards as an example project for reference to achieve a somewhat similar result:

francisp · August 15, 2023, 12:26pm

Is there ready to flash firmware available ?

I had to download several gigabytes of software, and google a few hours (because the Nordic Semiconductor documentation is lacking on a few points) just to produce a less then 300k hex file to flash to my nRF52840 to act as a OTBR. But working with HA !

Hedda · August 15, 2023, 12:59pm

The answer is yes if you are asking about Zigbee NCP (Zigbee Coordinator) firmware for nRF52840.

Link to compiled “nrf-zboss-ncp” hex firmware for nRF52840 USB dongle is in zigpy-zboss readme:

https://github.com/kardia-as/zigpy-zboss/blob/main/README.md#firmware

https://github.com/kardia-as/nrf-zboss-ncp

Alternatively, you can get the very latest unmodified version from the ZBOSS NCP Host example zip:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/zigbee/tools.html#ug-zigbee-tools-ncp-host

https://developer.nordicsemi.com/Zigbee/ncp_sdk_for_host/

You can flash nRF52840 USB dongle using programmer application from the nRF Desktop application

https://www.nordicsemi.com/Products/Development-tools/nrf-connect-for-desktop

francisp · August 15, 2023, 1:01pm

Great. I have a second one coming, I’ll try it out.

Hedda · August 15, 2023, 1:17pm

Nice, be sure to post any issues to the https://github.com/kardia-as/zigpy-zboss repository on GitHub

stolevegen · November 25, 2023, 8:37am

Has anyone got this working with ZHA or Z2M?
I have flashed a NRF5284 Dongle with the firmware, and ported usb through VM.

I copied the ZHA folder from Github
Added the folder as /homeassistant/custom_components/zha2

Under manifest.json

  "domain": "zha2",

.........

  "version": "9.2.3",

.........

  "usb": [
    {
        "vid": "2fe3",
        "pid": "0100",
        "description": "ZEPHYR Zigbee NCP",
        "known_devices": "NRF5284 Dongle Coordinator"
    },
................

  "loggers": [
    "zigpy-zboss"

..................

  "requirements": [
    "zigpy-zboss==1.1.2"

Under radio_manager.py

AUTOPROBE_RADIOS = (
    RadioType.zigpy-zboss,
    RadioType.zboss
)

Under const.py

import zigpy_zboss.zigbee.application

.............

class RadioType(enum.Enum):
    """Possible options for radio type."""
    )
    zboss = ("zigpy-zboss = Zigpy-zboss Zigbee radios",
        zigpy_zboss.zigbee.application.ControllerApplication,
        )

When configuring ZHA the dongle is available in Serial Device Path as :
/dev/ttyACM1 - Zigbee NCP, s/n: B0xxxxxxxxxxx4E - ZEPHYR

However, no matter which zigbee radio type I choose it never connects successfully. The Zigpy Zboss RadioType I tried to create is not available as a choice.

Hedda · November 26, 2023, 11:59am

Note that this have nothing to do with Zigbee2MQTT (also know as Z2M). This zigpy radio library can only be used with the ZHA integration → https://www.home-assistant.io/integrations/zha/

Since it is still experimental and unofficial so not include by default you should post any quations or requests as new issues to the zigpy-zboss repository on GitHub → Issues · kardia-as/zigpy-zboss · GitHub

stolevegen · November 26, 2023, 9:58pm

I started from scratch, and now it works.

Flashed the NRF52840 dongle with the following firmware https://github.com/kardia-as/nrf-zboss-ncp/blob/38c2e6ffed83ce079212fbaa417daded706faf78/nRF52840_dongle/v2.2.0_ncp_zboss_max_mem.hex

Copied Home Assistants /components/zha to my custom components folder /custom_compontents/zha

Then added a random version key to /custom_compontents/zha/manifest.json

"domain": "zha",
"version": "2023.1.1",

further down in the same manifest.json file, under "requirements": [ , you find a list of packages:
add "zigpy-zboss==1.1.2" to that list.

  "requirements": [
    "zigpy-zboss==1.1.2",
    "bellows==0.36.8",

Then open the file /config/custom_components/zha/core/const.py
Add import zigpy_zboss.zigbee.application

import zigpy_znp.zigbee.application
import zigpy_zboss.zigbee.application

Further down in the same file you will find class RadioType(enum.Enum):
Add boss to it

class RadioType(enum.Enum):
    """Possible options for radio type."""

    ezsp = (
        "EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis",
        bellows.zigbee.application.ControllerApplication,
    )
    boss = ("zigpy-zboss = Zigbee radio",
        zigpy_zboss.zigbee.application.ControllerApplication,
    )

Finally, restart HA.

When you go to “Settings” - “Devices & services” - “Add integration” and search for “Zigbee Home Automation” there should be a package next to it to indicate that it’s a custom integration

Using these steps the NRF52840 Dongle now works as an coordinator with ZHA.

Hedda · November 27, 2023, 10:54am

@stolevegen maybe you care to write step-by-step instructions into ”testing_guide.md” file and submit to the repo for others to follow and update → GitHub - kardia-as/zigpy-zboss

I believe it was mentioned that you if you do nlt also rename your custom copy of the addon in the manifest then you also need to add a distant future date as the version as otherwise it will be overwritten by the official zha integration updates? At least I think someone posted that here → Issues · kardia-as/zigpy-zboss · GitHub

That should be ”zboss” instead of ”boss”

Hedda · November 29, 2023, 7:26pm

Would also be great if you or someone else could test and confirm radio migration + backup and restore functionality for zboss radio under zha → ZBOSS Zigbee network backup and network restore + radio migration via zigpy radio API? · Issue #11 · kardia-as/zigpy-zboss · GitHub

That is, test migrating back and forth between diffuradio dongles → https://www.home-assistant.io/integrations/zha/#migrating-to-a-new-zigbee-coordinator-adapter-inside-zha

codyc1515 · January 31, 2024, 12:21am

I wasn’t able to get this to work. What did you put for port speed and flow control?

I’m getting the following error, regardless:

Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:421
First occurred: 13:16:35 (7 occurrences)
Last logged: 13:19:38

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 233, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 149, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 177, in post
    return await super().post(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
    result = await method(view, request, data, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 320, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 416, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/zha/config_flow.py", line 316, in async_step_verify_radio
    return await self.async_step_choose_formation_strategy()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/zha/config_flow.py", line 332, in async_step_choose_formation_strategy
    await self._radio_mgr.async_load_network_settings()
  File "/config/custom_components/zha/radio_manager.py", line 249, in async_load_network_settings
    async with self.connect_zigpy_app() as app:
  File "/usr/local/lib/python3.11/contextlib.py", line 204, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/zha/radio_manager.py", line 181, in connect_zigpy_app
    app = await self.radio_type.controller.new(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 242, in new
    app = cls(config)
          ^^^^^^^^^^^
TypeError: Can't instantiate abstract class ControllerApplication with abstract method permit_with_link_key

Hedda · January 31, 2024, 5:30pm

By default the UART baudrate should be set to 115200 if using firmware from GitHub - kardia-as/nrf-zboss-ncp

Suggest you post a new issue to → GitHub - kardia-as/zigpy-zboss

codyc1515 · February 5, 2024, 12:25am

Have done so now. Still not working on latest HA beta.

Hedda · April 15, 2024, 7:21am

Developers wanting to assist with this radio library project can help write and submit unit tests for it:

Write unit tests · Issue #7 · kardia-as/zigpy-zboss · GitHub

For reference please see tests directory for bellows, zigpy-znp, and zigpy-deconz radio libraries: