Giter Club home page Giter Club logo

zigbee's Introduction

Zigbee Device Compatiblity Repository

Contributing

Add your device with a simple Google form.

If you've spotted an error or have additional information for a device click on EDIT ON GITHUB box to add. If it's your first time refer to "Editing Articles" for a tutorial.

Open in Gitpod

zigbee's People

Contributors

accelle17 avatar babaisyou avatar bfayers avatar blakadder avatar brazen00 avatar cornim avatar cyrilpawelko avatar deennoo avatar djbenson avatar gamester17 avatar igorsantos07 avatar kenguest avatar larronni avatar letszb avatar lmgusx avatar louis22 avatar lukashass avatar majorsl avatar mattwestb avatar otnow avatar pipiche38 avatar rowcz avatar s-hadinger avatar sfromis avatar stegooding88 avatar sylvainper avatar trockenasche avatar waazdakka avatar woody14619 avatar wrt54g avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

zigbee's Issues

IKEA E1812 shortcut

This is only trigger, no brighteness control possible.
Zigbee recognise LQ and batterry % only. No action for this entity

Philips Hue 1600lm bulb incorrect model

I have a Hue white ambiance 1600lm bulb. It looks to be the same device as LTA011 on the website. I have mine setup in zha, and it appears as LTA012 in the dashboard. Is this possibly a new model revision?

[REQUEST] MCU chip manufacturer column for Zigbee coordinators

Please consider adding a column for MCU chip manufacturer to the Zigbee coordinators section:

https://zigbee.blakadder.com/coordinators.html

Suggest adding additional columns to database of Zigbee coordinators to make comparing easier.

This is as many different manufacturers use the same or similar Zigbee MCU radio chips or modules in their products and while some use the same Zigbee MCU radio chips they might run different Zigbee stacks and firmware.

For example, some Telegesis ETRX357 product series are based on the same type of ETRX35x chip family as Elelabs Zigbee products and Nortek HUSBZB-1 but use different Zigbee stack/firmware. And some MCU chips, like

  • MCU radio chip/module manufacturer (ex. Silicon Labs, Texas Instruments, Digi International, dresden elektronik, ZiGate, and Nordic Semiconductor)
  • MCU radio chip/module model (ETRX357, CC2530, CC2531, CC2538, CC2652R, CC2652P, CC1352P)
  • Zigbee Version (ZHA 1.2, Zigbee PRO, or Zigbee 3.0 are the three most common versions)
  • Zigbee Stack / Firmware, including version as for example both Silicon Labs and Texas Instruments have separate Zigbee stack versions for ZHA 1.2, Zigbee PRO, or Zigbee 3.0. As Silicon Labs has "EmberZNet PRO" (for Zigbee PRO) and "EmberZNet 3.0" (for Zigbee 3.0) , and Texas Instruments as Z-Stack 1.2 (for ZHA 1.2) and Z-Stack 3.0 (for Zigbee 3.0).

See requests/suggestions:

#26
#27
#28
#29

compatible with ?

I would like to share a comment has regards to this wonderful/awesome open source Zigbee database.

On the market today we have different application layers

  • Applications like Home Assistant, Domoticz, Jeedom ....
  • plugins like (ZHA) zigpy, z2m for domoticz, deconz for domoticz, Zigate for Domoticz ....
  • quirks for ZHA
  • middleware (for mqtt) z2m, deconz
  • coordinators .......

In the current database there is potential issues that a device is tag as supported on deConz, but do not work on ZHA because there is a missing Quirks , and vice-versa it can tag as supported on ZHA (because it works with a specific Controller but not an other one)

probably soon, a plugin willbe available on Domoticz based on zigpy layer ( what is used also by ZHA), and where devices could be supported by this new plugin, while it is not supported on ZHA. I'm thinking for instance for legacy Schneider Wisers for which there is no quirks for ZHA , but will work on this up-coming plugin

So I'm wondering if it shouldn't be better to have 2 levels of compatibility

Level 1: is the application/box ( ZHA, Domoticz-Z2M, Domoticz-Zigate ....)
Level 2: is the controller

Broken Z2M link for devices with slash `/` in model name

See the SOHAN Electric RDCBC/Z page for example.

The model name (RDCBC/Z) contains a slash (/), but the Z2M website uses underscore (_) for the sake of not breaking the URL.

This causes the Z2M link to be broken on the Blakadder website:

To fix this, I think this website should substitute slashes for underscores on the fly when generating the Z2M URLs.

Pairing info

Tried to add pairing info to X711A, but couldnt find how to do it like its done with QBKG03LM.

But the pairing info is : When off, hold the button down until its led starts blinking.

Mark "Nexentro Blinds Actuator Mini" as compatible with ZHA and deCONZ

The device "Nexentro Blinds Actuator Mini" can be marked as compatible with ZHA and deCONZ.
Device page: https://zigbee.blakadder.com/Insta_57008000.html

ZHA works out of the box - the device follows all Zigbee specification standards.
I'm using the device myself with ZHA.
But note: Tilt does not work with ZHA yet! This has nothing to do with the device, ZHA simply doesn't support tilt for any cover device yet. There are workaround available, e.g. using the zha.issue_zigbee_cluster_command service to directly send the go_to_tilt_percentage command.

deCONZ should also work out of the box for cover position. To get tilt working you seem to need this custom DDF: https://forum.phoscon.de/t/insta-nexentro-blinds-actuator-mini/687/4
I'm not using deCONZ myself but found that information while researching the device.

[REQUEST] Ability to sort by ZGP (Zigbee Green Power) support as a catagory?

Not that many ZGP (Zigbee Green Power) devices available so far but it would be nice to be able to sort and find a list easily.

https://zigbeealliance.org/solution/green-power/

Maybe "Green Power" could be its own "Devices by Type" category if devices could belong to more than one categories?

Right now it is not possible to search for "green" to try to find greenpower devices:

https://zigbee.blakadder.com/search.html

ZGP (Zigbee Green Power), a.k.a. "Zigbee GreenPower" (sometimes also referred to as a Green Power Device or GPD), is a subset feature of Zigbee that allows for extreme low-power and energy-harvesting technology to be used directly with the Zigbee stack. Using Zigbee Green Power, certain home automation wireless devices (end devices) may be powered by either energy harvesting solutions or sensors that can operate for up to a decade on a single battery coin-cell battery. Energy harvesting technology enables the maintenance-free battery-less devices (end devices) such as switches and remotes operating in a Zigbee network.

Certified ZGP products:

https://zigbeealliance.org/zigbee_products/?product_type=certified_product&se=green+power

Specific examples of ZGP devices:

PS: Some more devices are mentioned in zigpy/zigpy#341

Mains powered devices not working as repeaters

Would it be possible to add information about zigbee repeaters to the database? The website says that most mains powered devices will act as repeaters for other zigbee devices, but this is not always the case. For example, sengled outlets and bulbs do not function as repeaters (at least the ones I have). I spent weeks diagnosing zigbee issues before I figured this fact out.

Maybe just a note on devices that don’t follow the rule?

Sonoff Zigbee bridge is not pairing correctly with Sonoff switch

I'm unable to pair Sonoff wireless Zigbee switch to Sonoff Zigbee bridge, I'm not sure if it's a compatibility issue or I'm doing something wrong:

When pairing the switch

ZbPermitJoin 1

I get the correct console response:

tele/tasmota_DC0B35/3330/SENSOR = {"ZbReceived":{"0x3330":{"Device":"0x3330","Manufacturer":"eWeLink","ModelId":"WB01","Endpoint":1,"LinkQuality":150}}}

Binding

ZbBind {"Device":"0x3330","ToDevice":"0x0000","Endpoint":1,"ToEndpoint":1,"Cluster":6}

Result:

tele/tasmota_DC0B35/RESULT = {"ZbBind":{"Device":"0x3330","Status":0,"StatusMessage":"SUCCESS"}}

But when toggling the switch, it's always OFF (power=0), I get the same response on every toggle.

ZIG: {"ZbZCLReceived":{"groupid":0,"clusterid":6,"srcaddr":"0x3330","srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"LinkQuality":124,"securityuse":0,"seqnumber":19,"fc":"0x18","manuf":"0x0000","transact":19,"cmdid":"0x01","payload":"0000001000"}}
ZIG: ZbZCLRawReceived: {"0x3330":{"0006/0000":0}}
RSL: tele/tasmota_DC0B35/3330/SENSOR = {"ZbReceived":{"0x3330":{"Device":"0x3330","Power":0,"Endpoint":1,"LinkQuality":124}}}

[REQUEST] MCU chip/module model column for Zigbee coordinators

Please consider adding a column for MCU chip/module model to the Zigbee coordinators section:

https://zigbee.blakadder.com/coordinators.html

Suggest adding additional columns to the database of Zigbee coordinators to make comparing easier.

This is as many different manufacturers use the same or similar Zigbee MCU radio chips or modules in their products and while some use the same Zigbee MCU radio chips they might run different Zigbee stacks and firmware.

For example, some Telegesis ETRX357 product series are based on the same type of ETRX35x chip family as Elelabs Zigbee products and Nortek HUSBZB-1 but use different Zigbee stack/firmware. And some MCU chips, like

  • MCU radio chip/module manufacturer (ex. Silicon Labs, Texas Instruments, Digi International, dresden elektronik, ZiGate, and Nordic Semiconductor)
  • MCU radio chip/module model (ETRX357, CC2530, CC2531, CC2538, CC2652R, CC2652P, CC1352P)
  • Zigbee Version (ZHA 1.2, Zigbee PRO, or Zigbee 3.0 are the three most common versions)
  • Zigbee Stack / Firmware, including version as for example both Silicon Labs and Texas Instruments have separate Zigbee stack versions for ZHA 1.2, Zigbee PRO, or Zigbee 3.0. As Silicon Labs has "EmberZNet PRO" (for Zigbee PRO) and "EmberZNet 3.0" (for Zigbee 3.0) , and Texas Instruments as Z-Stack 1.2 (for ZHA 1.2) and Z-Stack 3.0 (for Zigbee 3.0).

See requests/suggestions:

#26
#27
#28
#29

[REQUEST] Zigbee Stack / Firmware column for Zigbee coordinators

Please consider adding a column for Zigbee Stack / Firmware to the Zigbee coordinators section:

https://zigbee.blakadder.com/coordinators.html

Suggest adding additional columns to the database of Zigbee coordinators to make comparing easier.

This is as many different manufacturers use the same or similar Zigbee MCU radio chips or modules in their products and while some use the same Zigbee MCU radio chips they might run different Zigbee stacks and firmware.

For example, some Telegesis ETRX357 product series are based on the same type of ETRX35x chip family as Elelabs Zigbee products and Nortek HUSBZB-1 but use different Zigbee stack/firmware. And some MCU chips, like

  • MCU radio chip/module manufacturer (ex. Silicon Labs, Texas Instruments, Digi International, dresden elektronik, ZiGate, and Nordic Semiconductor)
  • MCU radio chip/module model (ETRX357, CC2530, CC2531, CC2538, CC2652R, CC2652P, CC1352P)
  • Zigbee Version (ZHA 1.2, Zigbee PRO, or Zigbee 3.0 are the three most common versions)
  • Zigbee Stack / Firmware, including version as for example both Silicon Labs and Texas Instruments have separate Zigbee stack versions for ZHA 1.2, Zigbee PRO, or Zigbee 3.0. As Silicon Labs has "EmberZNet PRO" (for Zigbee PRO) and "EmberZNet 3.0" (for Zigbee 3.0) , and Texas Instruments as Z-Stack 1.2 (for ZHA 1.2) and Z-Stack 3.0 (for Zigbee 3.0).

See requests/suggestions:

#26
#27
#28
#29

tuya general device support in ZHA

ZHA have added general support (only model name and no model info) for flowing device:
Scene switch / remotes TS0041, TS0042, TS0043, TS0044
Dimmer switch / remotes TS004F
Cover controller TS130F.

Then the switches / remotes is coming in many different shape is it possible making one "general tuya TS0014" device (one for every type with one symbolic tuya picture) with explaining that all devices with this model is supported in ZHA and normally dont need one new quirk for working (some devices can having extra functions like back light that need being added but it possible doing with one device quirks) ?

I have seeing one general "tuya switch" but i cant finding it in the repro for the moment so i think its deleted or changed.

Thanks in advance !!

Mattias W

easy way to marke all TI CCxxxx coordinator compatible Z4D

hello,

is there an easy way to mark all TI Texas Instrument CCxxxx coordinator ZigbeeforDomoticz compatible ?

By using the library zigpy-znp , all the following are compatible

CC2652P/CC2652R/CC2652RB USB stick and dev board hardware
CC1352P/CC1352R USB stick and dev board hardware
CC2531 USB stick hardware (
CC2530 + CC2591/CC2592 USB stick hardware 

If it is not possible, I'll browse the database and makes PR, but before I wanted to check with you

Multiple Versions of Lidl Livarno Light Bar

Hi,

I've recently bought a Livarno Light Bar from the Lidl Online Shop, which seems to be a different version than this supported model.

Unfortunately I'm having the same issue with ZHA and Home Assistant as described in this thread:
#dresden-elektronik/deconz-rest-plugin#5900

Here is the Zigbee signature of my device, which you might want to add as not fully compatible to the database.

{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x010d", "in_clusters": [ "0x0000", "0x0003", "0x0004", "0x0005", "0x0006", "0x0008", "0x0300", "0x1000", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] }, "242": { "profile_id": 41440, "device_type": "0x0061", "in_clusters": [], "out_clusters": [ "0x0021" ] } }, "manufacturer": "_TZ3210_iystcadi", "model": "TS0505B", "class": "zigpy.device.Device" }

Thanks!

Taking in consideration Plugin and Box

I like much your Database and how easy it is to add product compatibility.

I wonder if it would not make sense to add the notion of Box ( Jeedom, Domoticz, HA ...) and the compatibility as well.

For instance, in the case of Zigate, the product can be compatible with Zigate, but still you have to perform some work on the plugin side to get fully working.

Single Phase 65A DIN Rail Energy Meter Model DDS238-2 manufactured by Hiking

Not working. Joins without entity.

Signature:
{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0051", "in_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "_TZE200_ewxhg6o9", "model": "TS0601", "class": "zigpy.device.Device" }

New brand/devices submitted but not avaiable

I have almost 3 weeks ago submitted several devices from CASA.IA

Here is the shop

ALL of the Zigbee devices have been certified on ZiGate with Domoticz plugin.

Unfortunately it seems that the new submission (as it was referring to a new brand are not yet processed ).

Is there any think I miss in the process ?

API to query over internet

I'm interested to retrieve the list of devices supported by a dedicated Gateway . Is there a JS API to do so ?

I might also be interested to query if a particular device is supported by a dedicated Gateway. Is such API exists ?

Thanks in advance

Request: Add nymea as gateway software

nymea (https://nymea.io/users) is a FOSS smart home/IoT platform with good ZigBee support. Would be nice to see it on the list of gateways.
Currently supported ZigBee adapters:

  • All phoscon models (ConBee I & II, RaspBee I & II)
  • NXP JN5168 & JN5169 (Which seem not to be included in the database yet)
  • All serial port based TI z-Stack models (CC253x - zStack 1.3 & CC2652[P|R|RB] - zStack 3x0). Specifically tested with ebyte 2530, Sonoff Zigbee 3.0 USB and the slae.sh dongle (https://slae.sh/projects/cc2652/) which is currently missing too.
    I'd submit the missing adapters once nymea can be selected in the google form.

As supported devices, it's well tested with all Hue,Tradfri,Develco models, supports most Lumi/aqara/xiami models and many more, but also implements generic device support as a catch-all to support ZigBee spec compliant devices, so anything that follows the standard Cluster Library should work. I could go through the code and submit all explicitly supported devices as well as listing all known-to-work devices reported by the nymea community.

[REQUEST] Zigbee Version column for Zigbee coordinators

Please consider adding a column for Zigbee Version to the Zigbee coordinators section:

https://zigbee.blakadder.com/coordinators.html

Suggest adding additional columns to the database of Zigbee coordinators to make comparing easier.

This is as many different manufacturers use the same or similar Zigbee MCU radio chips or modules in their products and while some use the same Zigbee MCU radio chips they might run different Zigbee stacks and firmware.

For example, some Telegesis ETRX357 product series are based on the same type of ETRX35x chip family as Elelabs Zigbee products and Nortek HUSBZB-1 but use different Zigbee stack/firmware. And some MCU chips, like

  • MCU radio chip/module manufacturer (ex. Silicon Labs, Texas Instruments, Digi International, dresden elektronik, ZiGate, and Nordic Semiconductor)
  • MCU radio chip/module model (ETRX357, CC2530, CC2531, CC2538, CC2652R, CC2652P, CC1352P)
  • Zigbee Version (ZHA 1.2, Zigbee PRO, or Zigbee 3.0 are the three most common versions)
  • Zigbee Stack / Firmware, including version as for example both Silicon Labs and Texas Instruments have separate Zigbee stack versions for ZHA 1.2, Zigbee PRO, or Zigbee 3.0. As Silicon Labs has "EmberZNet PRO" (for Zigbee PRO) and "EmberZNet 3.0" (for Zigbee 3.0) , and Texas Instruments as Z-Stack 1.2 (for ZHA 1.2) and Z-Stack 3.0 (for Zigbee 3.0).

See requests/suggestions:

#26
#27
#28
#29

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.