-
-
Notifications
You must be signed in to change notification settings - Fork 93
ZigBee Devices
I joined my RaspBee to the ZigBee network created by my Hue bridge. This page provides an overview of the ZigBee Devices connected to my Hue bridge, as reported by deCONZ.
Maybe try an make the RaspBee join network by Osram Lightify or innr gateway .
Here's the configuration for a Hue Extended Color Light:
| Endpoint | Profile | Cluster | Name |
|---|---|---|---|
| 02 | ZLL | Extended Color Light | |
| 0000 | Basic | ||
| 0003 | Identify | ||
| 0004 | Groups | ||
| 0005 | Scenes | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0300 | Color Control | ||
| 1000 | ZLL Commissioning | ||
| 0019 | OTAU | ||
| F2 | ZGP | 0061 unknown | |
| 0021 | ZigBee Green Power Sink | ||
| 0021 | ZigBee Green Power Proxy |
A Hue Color Light and a Hue Color Temperature Lights have the same configuration. So does a Hue Dimmable Light, except that it misses the Color Control cluster.
No clue what the 0021 cluster is. There is a matching client service in the Hue bridge. It's reserved in the ZCL under the General functional domain.
A1E0 is the ZigBee Green Power (ZGP) profile.
Here's the configuration for a second-generation Hue bridge:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| F2 | ZGP | 0061 unknown | |
| 0021 | ZigBee Green Power Proxy | ||
| 40 | ZLL | Control Bridge | |
| 1000 | ZLL Commissioning | ||
| 0019 | OTAU | ||
| 1000 | ZLL Commissioning | ||
| 0004 | Groups | ||
| 0005 | Scenes | ||
| 0000 | Basic | ||
| 0300 | Color Control | ||
| 0008 | Level Control | ||
| 0006 | On/Off | ||
| 41 | ZHA | Combined Interface | |
| 000F | Binary Input (Basic) | ||
| 0406 | Occupancy Sensing | ||
| 0402 | Temperature Measurement | ||
| 0405 | Humidify Measurement | ||
| FC00 | Device Setup (manufacturer specific) | ||
| 0400 | Illuminance Measurement |
I suspect the Binary Input (Basic) is used for buttonevent for the Hue dimmer switch. Apparently they planned for a ZigBee version of the CLIPHumidity sensor? Then why no ZigBee version of the CLIPContact sensor? No clue about the FC00 cluster, but the Hue dimmer switch has a corresponding server. Could it be for the lights commissioned by the dimmer switch?
Here's the configuration for a Hue motion sensor:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| 02 | ZHA | Occupancy Sensor | |
| 0000 | Basic | ||
| 0001 | Power Configuration | ||
| 0003 | Identify | ||
| 0406 | Occupancy Sensing | ||
| 0400 | Illuminance Measurement | ||
| 0402 | Temperature Measurement | ||
| 0019 | OTAU | ||
| 01 | ZLL | On/Off Sensor | |
| 0000 | Basic | ||
| 0000 | Basic | ||
| 0003 | Identify | ||
| 0004 | Groups | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0300 | Color Control | ||
| 0005 | Scenes |
So the motion sensor talks ZHA?! The 01 endpoint seems to suggest it could work without a Hue bridge?!
Here's the configuration for a Hue dimmer switch:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| 01 | ZLL | Non-Color-Scene Controller | |
| 0000 | Basic | ||
| 0000 | Basic | ||
| 0003 | Identify | ||
| 0004 | Groups | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0005 | Scenes | ||
| 02 | ZHA | 000C | |
| 0000 | Basic | ||
| 0001 | Power Configuration | ||
| 0003 | Identify | ||
| 000F | Binary Input (Basic) | ||
| FC00 | Device Setup (manufacturer specific) | ||
| 0019 | OTAU |
The Scenes cluster is missing from one of the dimmers, which reports as Non-Color Controler. Read error or different firmware?
I suspect the Binary Input (Basic) is used for buttonevent. No clue about the FC00 cluster, but the Hue bridge has a corresponding client.
Here's the configuration for an Osram E14 bulb:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| 03 | ZLL | Color Temperature Light | |
| 1000 | ZLL Commissioning | ||
| 0000 | Basic | ||
| 0003 | Identify | ||
| 0004 | Groups | ||
| 0005 | Scenes | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0300 | Color Control | ||
| FC0F | ? Device Setup (power-on defaults) | ||
| 0019 | OTAU |
Except for the FC0F cluster, it looks pretty straightforward. Maybe Orsam uses this to set the power-on default?
Here's the configuration for an Osram plug:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| 03 | ZLL | On/Off Plug-In Unit | |
| 1000 | ZLL Commissioning | ||
| 0000 | Basic | ||
| 0003 | Identify | ||
| 0004 | Groups | ||
| 0005 | Scenes | ||
| 0006 | On/Off | ||
| 0B04 | Electrical Measurement | ||
| 0019 | OTAU |
Looks pretty straightforward.
Here's the configuration for an innr RB 162 dimmable light:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| 01 | ZLL | Dimmable Light | |
| 0000 | Basic | ||
| 0004 | Groups | ||
| 0003 | Identify | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0005 | Scenes | ||
| 02 | ZLL | 1000 unknown | |
| 1000 | ZLL Commissioning |
Indeed, no over-the-air update for the firmware as innr support had indicated. ZLL Commissioning is in a separate endpoint, but otherwise no surprises.
Here's the configuration for an innr PL 110 or UC 110:
| EP | Profile | Cluster | Name |
|---|---|---|---|
| 01 | ZLL | Dimmable Light | |
| 0000 | Basic | ||
| 0004 | Groups | ||
| 0003 | Identify | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0005 | Scenes | ||
| FFFF | ? | ||
| 0019 | OTAU | ||
| 0000 | Basic | ||
| 0004 | Groups | ||
| 0003 | Identify | ||
| 0006 | On/Off | ||
| 0008 | Level Control | ||
| 0005 | Scenes | ||
| 0019 | OTAU |
Huh, over-the-air update for the firmware? Furthermore, the box seems to be configurable as a ZigBee control device as well. Maybe innr uses the same board for their gateway?
Home | FAQ | Getting Started | Reference