Comments
What’s wrong with the existing standard of Bluetooth?
Bluetooth consumes too much power, costs too much, and only supports short distances. ZigBee (and Z-Wave for that matter) adds very little overhead in terms power consumption and cost, so it can be implemented in small, very low cost devices like remote controls and light switches that don’t have the processing power for Bluetooth. Furthermore, Zigbee is a mesh-networking technology so it can span an entire house.
Note to the article: The RF4CE is *NOT* building their protocol on top of ZigBee. ZigBee builds on top of IEEE 802.15.4, so do Wireless HART and 6loWPAN and the now upcoming protocol from RF4CE.
In other words, please don’t mistake IEEE 802.15.4 for ZigBee. IEEE 802.15.4 covers the PHY and MAC layer, while ZigBee is an extension on top of this forming the network layer and parts of the application layer.
The RF4CE protocol is not ZigBee.
Yes, John is absolutely correct (and then Zigbee developers pile on their own extensions so nothing is interoperable).
Please forgive the faux pas.
good work
Hi Julie, nice post.
You might be interested to know that ZigBee has in fact been incorporated into at least one CE device. AlertMe, a home management platform, is one of the first CE devices to incorporate the ZigBee protocol and is a prime example of how it can be used in the home.
Can put you in touch with the CEO if you’d like to know more about them.
The RF4CE consortium has taken the 802.15.4 PHY/MAC protocol and developed the RF4CE protocol on top of this from scratch. Any previously existing protocol such as Synkro will NOT be RF4CE compliant.



I think they should do away with IR all togeater.