...
...
...
...
...
...
Table of Contents | ||
---|---|---|
|
...
...
...
...
...
...
...
FAQ
What are the key features being added in zigbee 3.0?
- Unified all Application Profiles into one standard
- Improved security
When can device vendors start certifying zigbee 3.0 products?
The certification process opened on May 15, 2016. However, most silicon vendors are still finalizing their support of the Green Power features, so very few devices have been certified to date.
When will MMB release RapidConnect firmware that will be compliant with zigbee 3.0?
MMB's first public release of zigbee 3.0 compliant RapidConnect firmware will likely be in June, 2017. If you are interested in testing an alpha or beta release, please contact your Account Manager for more information.
What are Devices and Clusters available for certification today?
As of March 20, 2017, the following devices can be certified:
- On/Off Switch
- On/Off Light Switch
- Level Control Switch
- Dimmable Plug-in Unit
- On/Off Output
- Color Temperature Light
- Extended Color Light
- Level Control Output
- Scene Selector
- Shade Controller
- Configuration Tool
- Window Covering Device
- Window Covering Controller
- Remote Control
- Combined Interface
- Temperature Sensor
- Range Extender
- Color Controller
- Color Scene Controller
- Mains Power Outlet
- On/Off Light
- Non-Color Controller
- Non-Color Scene Controller
- Dimmable Light
- Color Dimmable Light
- On/Off Light Switch
- Dimmer Switch
- Color Dimmer Switch
- Light Sensor
- Occupancy Sensor
- Control Bridge
- On/Off Sensor
- Green Power Proxy Basic
- Green Power Combo Basic
- Green Power Device
What will happen to the existing application profiles like Home Automation and zigbee Light Link?
...
What will happen to zigbee Smart Energy?
This is still being discussed by the members of the zigbee alliance. At present, there are no firm plans to merge the zigbee Smart Energy Application Profile into zigbee 3.0.
How will zigbee GreenPower work with zigbee 3.0?
All ZigBee 3.0 routers must be able to act as a proxy for Green Power (the zigbee networking and application-level specification for energy-harvesting end devices).
Will zigbee 3.0 devices be backward compatible with older devices?
...
How can device vendors test their device for zigbee 3.0 compliance?
The zigbee alliance will be providing a ZigBee 3.0 Test Tool and a Green Power Test Harness. Each company will receive a complimentary license for the zigbee 3.0 Test Tool. Additional licenses are 1000 USD per year. Green Power Test Harness licenses are 1000 USD per year.
zigbee 3.0 Test Tool (ZTT) licenses can be purchased from https://www.regonline.com/ZigBee3testtool
Will Unsecured Rejoin (TC Rejoin) still be allowed in zigbee 3.0?
No. In zigbee PRO stack r21 and zigbee 3.0, TC Rejoin (or Unsecured Rejoin) using the default or well-known link key will no longer be allowed. It will only be allowed for devices that have completed successful link key exchange, where they receive unique link keys.
See zigbee PRO Stack r21 specification (05-3474-21), Table 4.33 Trust Center Policy Values, attribute allowRejoins.
What might block you from certifying a zigbee 3.0 product right now?
While zigbee 3.0 is gathering momentum, only a couple of vendors have certified their product so far.
There are a few factors right now that may limit or block product certification:
- Not every device type is available for certification yet.
- Not every cluster is available for certification yet.
- The Green Power test harness is not yet available for vendors to test their implementation before submitting their product to an authorized test house.
- The zigbee 3.0 Test Tool is still working out bugs and issues.
If you are planning a new zigbee product, please check with us on whether your product would be gated by any of these factors, and what we can do to accelerate your path to certification.
What is the upgrade path from legacy HA devices to zigbee 3.0 for MMB customers?
...
Style |
---|
{style}
.wiki-content h1 {
font-family: 'Helvetica Neue', sans-serif; font-size: 30px; font-weight: bold; color: #20b6e1; letter-spacing: 1px; line-height: 1; text-align: left;
#border-bottom: 1px solid #98bddd !important;
}
.wiki-content h2 {
font-family: 'Helvetica Neue', sans-serif; font-size: 20px; font-weight: normal; color: #00517f; letter-spacing: 1px; line-height: 1; text-align: left;
}
.wiki-content h3 {
font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: bold; color: #00517f; letter-spacing: 1px; line-height: 1; text-align: left;
}
.wiki-content h4 {
font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; font-style:italic; color:#00517f; letter-spacing: 1px; line-height: 1; text-align: left;
}
#title-text{
font-family: 'Helvetica Neue', sans-serif; font-size: 40px; font-weight: 500; letter-spacing: 1px; line-height: 1; text-align: left;
}
.panel, #content .panel {
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
}
.panel .panelHeader {
text-align: left;
color: #FFFFFF;
line-height: 1em;
padding: 10px 10px 5px;
margin-bottom: 0;
background-color: #00517f;
-moz-border-radius-topleft: 5px;
-moz-border-radius-topright: 5px;
-webkit-border-top-right-radius: 5px;
-webkit-border-top-left-radius: 5px;
border-top-right-radius: 5px;
border-top-left-radius: 5px;
color:#FFFFFF
}
{style} |