"Zzh!" (short for "Zig-a-zig-ah!") open-source hardware licensed Zigbee USB-stick based on TI CC2652R

Hedda · June 29, 2020, 8:20am

FYI; ZHA uses the “ZHA Device Handlers” library by default for ZHA exception and deviation handling:

So what you might need to do to get devices with problems working is create a new custom device handler, also known as a “quirk”, or update the existing quirks, or submit an new issue on that GitHub repository with more detailed information and logs if you need help with the creation or updating ZHA custom device handlers:

github.com

zigpy/zha-device-handlers/blob/cb820ebbcf0d5f044bde8997aed09091486dbce8/CONTRIBUTING.md

# Initial Contribution Guidelines - WIP

- All code is formatted with black. The check format script that runs in CI will ensure that code meets this requirement and that it is correctly formatted with black. Instructions for installing black in many editors can be found here: <https://github.com/psf/black#editor-integration>

- Capture the SimpleDescriptor log entries for each endpoint on the device. These can be found in the HA logs after joining a device and they look like this: `<SimpleDescriptor endpoint=1 profile=260 device_type=1026 device_version=0 input_clusters=[0, 1, 3, 32, 1026, 1280, 2821] output_clusters=[25]>`. This information can also be obtained from the zigbee.db if you want to take the time to query the tables and reconstitute the log entry. I find it easier to just remove and rejoin the device. ZHA entity ids are stable for the most part so it _shouldn't_ disrupt anything you have configured. These need to match what the device reports EXACTLY or zigpy will not match them when a device joins and the handler will not be used for the device.

- Create a device class extending CustomDevice or a derivitave of it

- All custom cluster definitions must extend CustomCluster

- Use an existing handler as a guide. signature and replacement dicts are required. Include the SimpleDescriptor entry for each endpoint in the signature dict above the definition of the endpoint in this format:

  ```yaml
  #  <SimpleDescriptor endpoint=1 profile=260 device_type=1026
  #  device_version=0
  #  input_clusters=[0, 1, 3, 32, 1026, 1280, 2821]
  #  output_clusters=[25]>
  ```

- Use constants for all attribute values referencing the appropriate labels from Zigpy / HA as necessary

This file has been truncated. show original

Once a new quirk is added or updates there are instructions in their readme file now on how to test new releases of zha-device-handlers that are not yet available in Home Assistant so you do not have to wait for a new release of Home Assistant as well:

github.com

zigpy/zha-device-handlers/blob/dev/README.md

# ZHA Device Handlers For Home Assistant

![CI](https://github.com/zigpy/zha-device-handlers/workflows/CI/badge.svg?branch=dev)
[![Coverage Status](https://codecov.io/gh/zigpy/zha-device-handlers/branch/dev/graph/badge.svg)](https://app.codecov.io/gh/zigpy/zha-device-handlers/tree/dev)

ZHA Device Handlers are custom quirks implementations for [Zigpy](https://github.com/zigpy/zigpy), the library that provides the [Zigbee](http://www.zigbee.org) support for the [ZHA](https://www.home-assistant.io/components/zha/) component in [Home Assistant](https://www.home-assistant.io).

ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices. Zigbee devices that deviate from or do not fully conform to the standard specifications set by the Zigbee Alliance may require the development of custom ZHA Device Handlers (ZHA custom quirks handler implementation) to for all their functions to work properly with the ZHA component in Home Assistant.

Custom quirks implementations for zigpy implemented as ZHA Device Handlers are a similar concept to that of [Hub-connected Device Handlers for the SmartThings Classics platform](https://stdavedemo.readthedocs.io/en/latest/device-type-developers-guide/) as well that of [Zigbee-Herdsman Converters (formerly Zigbee-Shepherd Converters) as used by Zigbee2mqtt](https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html), meaning they are virtual representation of a physical device that expose additional functionality that is not provided out-of-the-box by the existing integration between these platforms. See [Device Specifics](#Device-Specifics) for details.

# How to contribute

## Primer

ZHA device handlers and its provided Quirks allow Zigpy, ZHA and Home Assistant to work with non-standard Zigbee devices. If you are reading this you may have a device that isn't working as expected. This can be the case for a number of reasons but in this guide we will cover the cases where functionality is provided by a device in a non specification compliant manner by the device manufacturer.

## What are these specifications

Reference official Zigbee specification documentation from Connectivity Standards Alliance (a.k.a. "CSA-IOT", formerly "Zigbee Alliance"):

This file has been truncated. show original

slaesh · July 30, 2020, 7:13am

Here is another alternative using the powerful CC2652R

wpy0228 · August 2, 2020, 5:12pm

What is the difference with the zzh? They seem to be using different firmware. Have tested with ZHA?

nickrout · August 2, 2020, 8:45pm

What do you mean?

slaesh · August 3, 2020, 8:21am

It’s the “same” firmware. Just compiled for another Chip. If you “just” want to use the stick as an zigbee-coordinator there is no difference at all…

otherwise, if you want to develop something with it (sensor or any other zigbee device):

onboard chip-antenna possible
other USB-chip, better/wider driver support
onchip timer and external rtc-crystal possible
possibility to break-out the CC2652R part, to build a standalone (maybe battery powered) device
automatic bootloader mode for easy flashing
reset-button on board
…

Gamester17 · August 3, 2020, 8:42am

What do you mean? Different to what? ZHA support multiple adapter models from different manufacturers. Different manufacturers use different firmware, and some adapter models when it is the same manufacturer use newer firmware when it has a newer chip. All adapters/chips listed on the ZHA integration component page work with ZHA in Home Assistant.

wpy0228 · August 3, 2020, 4:27pm

Oh Ok. Sorry for the confusion. I thought it was different when I saw it in the Z2M page. But all clear now!!!

Hedda · August 10, 2020, 7:39am

I have now submitted a pull request to clarify that all TI CC1352x and CC2652x are supported by ZHA

The PR only updates ZHA documenation withoyut any code changes. CC1352P, CC1352R, CC2652P, CC2652R, CC2652RB use the same TI Zigbee coordinator firmware/API version and are all already supported by the current branch with existing ZHA and zigpy/zigpy-cc libraries. No code changes needed.

talondnb · August 18, 2020, 11:05am

Hi @slaesh, I’ve placed an order on the 9/8/20 but have not yet had any updates on the status. I’ve also sent a message to you via Tindie a few days ago. Please respond, cheers.

Gamester17 · August 18, 2020, 12:20pm

FYI, a few days ago I noticed he had posted on Tindie that he he had to go away on an unplanned trip:

"DELAY On an unplanned emergency business trip! May take up to a week… Production is still running! All delayed orders will get some goodies! For new Orders use this code: 4163C0A1"

talondnb · August 18, 2020, 12:36pm

Thanks, yes i saw that message too. It has been over a week but will have to wait a little longer I guess.

slaesh · August 25, 2020, 6:47am

hey there! didn’t saw this community post here anyhow

currently, I am a step in front of the wave now… just some days more and all incoming orders will be processed directly again, as it should be!

sorry for the inconvenience!
love to see your projects running as soon as possible

Cinamon · August 25, 2020, 4:49pm

I have just received a new zzh stick because the old batch was not good. Perfect service from Omer.
But i have still not the range what i expected from this stick. My conbee2 stick has a much better range then this one. Also without routers.

Tinkerer · August 25, 2020, 5:13pm

I found that the new stick didn’t really change the signal strength (it was about 160 with the sensor about 2 meters from the stick, it’s about 170 now). However, when I move it to the other side of the house I’ve got a LinkQuality of about 60 to 70 - about 10 to 12 meters away, through 4 plasterboard walls.

dan123 · September 7, 2020, 3:10pm

Hi @slaesh, Do you have any update on the orders? I placed my order on the 5th Aug, I am still waiting patiently. Thanks for any update.

Tinkerer · September 8, 2020, 6:30am

I got an email yesterday about this:

The backlog has been made up. And all open orders are going out this week!

Gamester17 · September 14, 2020, 7:13am

@slaesh See that you are “out of stock” now. How long is the wait time until you get in new stock?

lawsuitup · September 15, 2020, 10:35pm

Ok I’m having a hard time flashing the ZZH. Can anyone help? I think I am following the directions to a t.

nickrout · September 15, 2020, 10:38pm

Nobody can help unless you say exactly what you have done and what result you achieved, including relevant logs if available.

lawsuitup · September 16, 2020, 1:00am

Ok, so once I get to the cc2538-bsl.py -p COM6 -evw CC26X2R1_20200805.hex

my command prompt window shows:

C:\Users\mfidl\Desktop\cc2538-bsl-master>
[main 2020-09-16T00:57:24.599Z] update#setState idle
(node:1436) Electron: Loading non-context-aware native module in renderer: '\\?\C:\Users\mfidl\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\vscode-sqlite3\build\Release\sqlite.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:1436) Electron: Loading non-context-aware native module in renderer: '\\?\C:\Users\mfidl\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\spdlog\build\Release\spdlog.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:3780) Electron: Loading non-context-aware native module in renderer: '\\?\C:\Users\mfidl\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\spdlog\build\Release\spdlog.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:3780) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[main 2020-09-16T00:57:54.604Z] update#setState checking for updates
[main 2020-09-16T00:57:55.065Z] update#setState idle

EDIT: I should also note that a VSCode window opens cc2538-bsl.py