Replies: 2 comments
|
FYI, Zigbee2MQTT's webpages for their supported devices has something somewhat similar that lists what endpoints each device exposes. Ex: |
0 replies
|
@mkerstner a related idea could be to look into adopting the standard XML format used by CSA's ZAP (ZCL Advanced Platform) for this: The website could then parse Zigbee and Matter specification XML files to generate intermediate representations to render on the web. This is the official Zigbee and Matter specifications XMLs from Connectivity Standards Alliance, and a few other projects use it similarly. See ex: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Pretense: Zigbee devices organize their features using the Zigbee Cluster Library (ZCL). Clusters are functional building blocks, attributes store the device state data inside servers, and commands are instructions sent between clients and servers to read, write, or alter that data.
Would it be useful to have full lists of Zigbee device's commands, clusters, and attributes capability datasets for each and every Zigbee device in the OHF Device Database?
For example, hsolgaard have collected n openly reusable dataset called zigbee-capabilities (released under CC0) that records the clusters, commands and attributes actually reported by particular Zigbee device models and firmware versions.
https://hsolgaard.github.io/zigbee-capabilities/
ZHA currently has a device testing database with very similar content and nearly 1,000 device diagnostics files but it has no ZDO capabilities:
https://github.com/zigpy/zha/tree/dev/tests/data/devices
For reference, seen those as talked about under zigpy discussions here:
All reactions