zha-device-handlers

ZHA quirks 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.

Not yet testedsource: GitHubPythonApache-2.0commit 8c8e861c9bf8

Python, Apache-2.0 licensed. The project labels itself: hacktoberfest, home assistant and home automation.

zha-device-handlers has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
1,143
forks
1,210
open issues
891
watchers
38
size
5 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

hacktoberfesthome-assistanthome-automation

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/zha-device-handlers.svg)](https://argusic.com/subject/zha-device-handlers)

Questions

Does zha-device-handlers run?
zha-device-handlers has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test zha-device-handlers?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for zha-device-handlers?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion