From Wikipedia, the free encyclopedia
  (Redirected from Talk:ZigBee)
Jump to: navigation, search
WikiProject Telecommunications (Rated Start-class, Mid-importance)
WikiProject icon This article is within the scope of WikiProject Telecommunications, a collaborative effort to improve the coverage of Telecommunications on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.

Zigbee Bit Rates[edit]

The statement "Data transmission rates vary from 20 to 900 kilobits/second." is either incorrect or confusing. The actual data rate is 250kbps. Is the 900kbps intended to mean the data rate between devices or the bit rate on the air? — Preceding unsigned comment added by Jcwren (talkcontribs) 18:37, 24 January 2012 (UTC)

Jcwren (talk) 18:37, 24 January 2012 (UTC)

ZigBee's security flaw while key exchange[edit]

This is the paper the german article references:

When a devices is paired with the network, the secret network key is transmitted unsecurely. The problem is, as statet correctly, that the network key in transfered encrypted with a standard key. Therefore any eavedropper can decrypt it. By jamming the network an attacker can "encourage" the owner of the ZigBee network to rejoin the jammed device with the network and then sniff the key. Without the owner unwillingly helping the attacker this flaw is hard to exploit. — Preceding unsigned comment added by (talk) 21:26, 12 January 2017 (UTC)

Zigbee Bandwidth[edit]

I found contrary claims of the channel bandwidth Zigbee devices use. While it is true that the channels are separated by 5 MHz, it is nowhere mentioned in standards that the bandwidth is 5 MHz. I see some research papers claiming that the bandwidth is 2 MHz. E.g. this: Mutual interference analysis of IEEE 802.15.4 and IEEE 802.11b, CMOS RFIC Architecture from Cadence and Agilent webpage Anyone has a clear idea?

Allrite82 (talk) 23:02, 13 December 2007 (UTC)

Why the name?[edit]

Can anybody explain the origin of the name 'ZigBee' ? I think this may add context to the introduction of the article.

Answer: Bees perform a zick-zack dance to communicate food locations. The multi-hop routing also does a kind of zick-zack to convey information. [German article: "Der Tanz der Bienen beginnt" in ELEKTRONIKPRAXIS NR. 8 – 14. April 2005" by Prof. Dr. Axel Sikora] FabFive Ti (talk) 23:56, 24 November 2008 (UTC)

The answer can be found in the current ZigBee article (with a reference to an outside article that provides more detailed information). It appears that the relationship between the ZigBee name and the bee communication dance is a retroactive justification myth, and that the name was originally selected largely because it wasn't trademarked. --Allan McInnes (talk) 06:58, 25 November 2008 (UTC)
Ah, what a faux pas. Indeed, the name is just waggle dance. Having moved the information to the end, this discussion topic should be removed, though. FabFive Ti (talk) 12:53, 25 November 2008 (UTC)

I have a question. Is it ZigBee or Zigbee? Both are used in this article. (talk) 04:26, 8 December 2009 (UTC)

Answer: It should be ZigBee. I have tidied up the spelling. AutolycusQ (talk) 15:34, 12 March 2013 (UTC)

Clean up[edit]

  • Got rid of the advert warning. It is misleading to put this warning since there are multiple vendor claims.
  • So what is wrong with this page?
    • Too much info: No. Length is reasonable.
    • Some info read too much like an add? yes, especially in the module section.
    • Solution for module:
      • Suppression of all trademarks, marketing names, etc.. since it does not bring any technical information.
      • Suppression of any adjectives such as best,first etc..
      • No comparison (vendor A module is bigger than vendor B module). Note that in this case bigger is not better.
      • Using the same style for every entry.
      • Standardize on: offers, provides etc..
    • Solution for Chip:
      • Not much to modify.
      • Contrary to module, standard practice is to know a chip by its name which is a number.
      • Standardize on: <chip number> offers etc..
    • General:
    • Organise entries in alphabetical order.
    • Max number of lines: 3
      • Why limit the number of lines?
        • To make it readable and allow an increase of entries without taking too much space.
    • Finally, as it stands now , vendor information is reasonable. I do not guarantee the future, but before suppressing it completely, let us give a chance to the herding of cats.

Dilane 02:53, 13 November 2006 (UTC)
-Very Nice job, thanks--MountainLogic 22:59, 17 November 2006 (UTC)

Contrary to the Microchip Blurb[edit]

Microchip currently has no plans to continue support of their existing rudimentary stack which has limited support for other vendor's RF section (Chipcon, in particular). It is misleading, or downright dishonest to include mention of this stack inferring it is viable. It is not certified as interoperable, cannot be certified in its current state, nor does Microchip have any current plans to make it certifiable.—Preceding unsigned comment added by BluesFiddler (talkcontribs) -Source for this claim? This sounds very harsh! --MountainLogic 19:51, 10 November 2006 (UTC)
-Indeed it is harsh, but not nearly as harsh as developing a product only to discover this was all a figment of somebody's imagination! It is simple enough to ask the question of a Microchip FAE before committing to a project. The good news is they now have their own radio (MRF24J40) in sample quantities; allegedly available in production quantities 1Q 2007. Their 3.6 stack has been certified as ZigBee-compliant with this radio. If you are just hacking, none of this matters. If you are in development, make sure you target the MRF24J40 and the 3.6 stack. Once production has been confirmed, most of this comment can be deleted except for the caveat to check your PICDEM-Z kit for the proper radio. --[User:BluesFiddler] 15 December 2006

I have verified that the Microchip radio is now available (at least in limited quantities) and the stack now supports their radio (MRF24J40) and is currently supported by Microchip as evidenced by the fact they are now on revision 3.8 of the stack. This was confirmed by acquiring their current PICDEM-Z package and implementing a simple application beyond their demo application. BluesFiddler 01:07, 23 March 2007 (UTC)

The first commercial ZigBee product[edit]

zPoint Products was informed that the ZigBee USB Dongle (as shown at Light Fair in the ZigBee Alliance booth) was the first commercial product in the world (according to the Zigbee Alliance, who invited zPoint Products to demonstrate a ZigBee wireless lighting control system in their booth). That was a surprise given all the hype about ZigBee to date. However, anything else out there appears to be dev. kits or vapor ware, at least as of Sept. 2006. That was certainly the case in April 2006 when the product was first shown.

This can easily be verified by the Zigbee Alliance. Ask Bob Heile, the Chairman, since he's the one that informed us of the status of our product. Bempey 05:19, 30 September 2006 (UTC)

"Please DO NOT put commercial information"[edit]

Revragnarok recently deleted the entire "Device Vendors" and "Chip/Firmware Vendors" sections with no explanation beyond a comment "Please DO NOT put commercial information (vendor, supplier, etc.) here". I disagree with this. Anybody interested in Zigbee will be interested in an overview of who is implementing it and how the various implementations compare. Of course we should not allow it to turn into a forum for advertisements by every single commercial vendor, but a brief summary of the major contendors is completely warranted, and has numerous precedents in other Wikipedia articles, e.g. Photoshop: Alternatives. Feel free to reword the descriptions to eliminate bias and prune the list, but you cannot just delete entire sections of Wikipedia content because commercial products were mentioned. --Anonymous 02:13, 8 June 2006 (UTC) —Preceding unsigned comment added by (talkcontribs)

No, I didn't. Ausinha did here [1]. I think we can use a few but see Section 1.5. It can use some pruning. -- RevRagnarok Talk Contrib Reverts 10:17, 8 June 2006 (UTC)
A list of resources is usefull because much of the technical documentation and white papers on the topic is going to only be found from the vendors at this point. That said, the vendor list did need some cleaning up (removal of words like "leading," "world's first," etc.). A better break down of the catagories (splitting ICs from stacks, adding a engineering services area, renaming devices to modules and adding consumer devices when they arrive) to reduce the need for verbage and thus the tempation for embelishment. If ZigBee does take off and we see mass adoption much of the page should be split off and become ZigBee Development and this page replaced with much more non-technical user oriented material--MountainLogic 17:17, 20 September 2006 (UTC)
I've changed my mind. The marketing speak on this page is out of control. Time to eliminate commercial links. If reader really need to find links thay can to to the page. --MountainLogic 21:43, 8 November 2006 (UTC)
I think that is a bit harsh... I agree the vendor lists were getting "out-of-hand", but today's edit (removing ALL vendor sections), is reactionary. Just because something is commercial information, doesn't mean it is useless information. I vote we leave the vendor lists in and just keep trimming here and there. Mware 20:56, 30 November 2006 (UTC)
Perhaps it is time to create a ZigBee Market Page??--MountainLogic 01:55, 5 December 2006 (UTC)
The deletion of the vendors of chips and products is totally against the intention of the provision of knowledge to the public.

This is a new technology and there are many engineers and designers who are interested in it beyond a discussion of the theory behind it. Not only has someone deleted all the useful content for anyone interested in experimenting or learning more about the hardware supporting ZigBee, but someone has deleted half of the pages that were linked to by this article! If a company cannot exist in Wikipedia because any reference to a commercial organization is "spam", then I will go ahead and delete all the entries for IBM, Michael Dell and his company, Bill Gates & Microsoft, Apple, Henry Ford & his company, GM, Chrysler, Harley Davidson, Wright Brothers etc. Well, I think that you get my point. The fact that all those companies mentioned have pages, but someone can willy-nilly delete a bunch of the notable companies performing ground-breaking work in the worlds of embedded computers and wireless controls just because the editor (deletor) is:

  • not interested in those topics, or
  • not knowledgable in those fields

is a sign of total hypocrisy, and I believe that they are a dis-credit to the Wikipedia community! Bempey 02:48, 7 December 2006 (UTC)

This Wiki entry *used* to be useful. Now it is quite useless. If you are not going to allow vendor lists (sans the superlatives), you might as well delete my "Contrary to the Microchip Blurb" entry since it now refers to something which no longer exists. If you are going to target amateurs only, that is fine, but I *used* to come here first as my first look at serious subjects. Also, while I am on a rant, mass delete-ers are obligated to delete everything that references that which was deleted.--User:BluesFiddler 15 December 2006

I've restored the list to a new page ZigBee_Products so that it can live or die on its own. If the community annotates the listing it can become more than a bill board into perhaps a history of technology type article if it is done without bias. --MountainLogic 17:32, 20 March 2007 (UTC)

The link to "ZigBee_Products" has either already been deleted by somebody or it was never properly linked. While this might be a reasonable solution for allowing vendor references, I continue to fail to see what harm is done by allowing vendor references within this article. Most people know that you cannot believe everything you read regardless of whether a vendor states it or some anonymous author contributing to these (or any other) pages states it. BluesFiddler 01:07, 23 March 2007 (UTC)

If you check with deleted pages it would seem that User:Irishguy seems to have a problem with that list. —Preceding unsigned comment added by MountainLogic (talkcontribs)

See WP:NOT#DIR. — RevRagnarok Talk Contrib 03:11, 27 March 2007 (UTC)

-- (talk) 15:46, 4 May 2009 (UTC) It is really a pity, that there is no list to ZigBee vendors :-( This is important and useful for everybody looking for more info. I think ZigBee Vendors and ZigBee products should be listed. Googling for ZibBee vendors is much more chatoic than having a few links (might be even a separate, referenced link) in Wikipedia

Comparison of 802.15.4 radio modules[edit]

See Comparison of 802.15.4 radio modules - (talk) 12:41, 10 June 2009 (UTC)


Does anyone know any low cost products (sub $20) that use zigbee?

No commercial products have been released, to my knowledge. Most zigbee products are development boards right now. --Bakkster Man 02:23, 6 March 2006 (UTC)
Products are now available on the market including home automation stuff from [| Control 4]. I am not aware of anythign below $20 yet =\ Kail Ceannai 12:08, 16 January 2007 (UTC)
I was under the impression that the pricing meant for the IC. Kind of like when AMD announces a new processor would be available at $75, that's when you buy them in lots of 1000 and you don't expect your entire end-user PC to then cost $75 - it's only one component. — RevRagnarok Talk Contrib 13:00, 16 January 2007 (UTC)

I have found information confirming the uncited note about 128kB Zigbee devices, such as the Chipcon CC2430-F128 (a $10 chip). What is the most appropriate way to incorporate this information? 21:24, 6 July 2007 (UTC)


Are there any standards for device control that run on top of ZigBee. It's great that ZigBee makes it easier and potentially cheaper to do wireless control of a lamp, but is there any standard way to use ZigBee to tell a lamp to turn on and off?

I haven't really been able to find any such standards, and I'm wondering if I'm missing something.

If ZigBee were higher bandwidth and the devices had more processing power, I'd assume that the home automation related UPnP standards would come into play, but they seem too heavyweight to seriously consider using them over ZigBee.

ZigBee makes use of profiles as far as I can remember, but those as is the ZigBee standard itself is not public. This knowledge itself commes derived from some datasheets and manuals included with a testboard I obtained from Chipcon. I don't believe ZigBee is high bandwith, at least not higher then Bluetooth, also the devices are usually not high processor powered. --Alras 15:33, 8 February 2006 (UTC)
ZigBee devices are supposed to have an application code (can't remember the actual name) which defines a standard. The idea is that Company A can make a ZigBee lamp controller and get application code 1. Company B can then make a ZigBee lamp controller with timer, place it under application code 1, and the devices would work together. Company C then comes along and makes a full suite of wireless home controll products, and all of these applications are made application code 1.
The ideal way this is accomplished is through "binds", where the data on two different devices are linked. Using the lamp example, the on/off data bit of the light switch is bound to the on/off of the lamp. Whenever the switch changes the lamp is automatically informed and changes its status.
ZigBee's goal isn't wireless light switches (thankfully). The ideal application is embedded sensors, especially where low-power is a prime factor of the design, and device networks, where one controller can communicate with many other devices. I'm actually working on a project to integrate zigbee into an embedded sensor network. I'd go into more detail, but the patent work has yet to go through. Let's just say, that it's a small sensor which will collect data in a large area and the many sensors will transmit their data to a reader. Hopefully I'll be able to tell you what it actually is at some point. --Bakkster Man 02:23, 6 March 2006 (UTC)
I believe the ZigBee Alliance (or some member thereof) is intending to create "profiles" to help standardize the control of devices, but I cannot remember off hand where I picked up this rumor. As of yet, I do not know of any standard framework for the application layer that develoeprs might layer upon the ZigBee standard; most researchers are still concerned with the Network, Transport, and Session layers. Kail Ceannai 22:58, 6 December 2006 (UTC)

This may be more appropriate to the introduction section, but one of the reasons our industry is so excited about Zigbee is that it will decrease risk of interference with WLANs in the professional and commercial market. Most of our control equipment operates at 2.4 GHz (802.11g), and moving to a 915MHz platform will allow us to deploy our control equipment much more easily. Sorry if this is self-evident, but I haven't seen any specific mention of it. 13:06, 7 May 2007 (UTC)

Node size[edit]

"node size" indicated in kilobytes. This is confusing. An explanation of what is meant by "size" in this context would be helpful.


Are you guys sure that OpenBee is written in UML? I'm pretty sure the M in UML is modelling. As in it is always pseudocode, never real. -- RevRagnarok 02:10, 19 April 2006 (UTC)

UML is modelling, and then most tools generate code in a standard programming language, although some (experimental ones) can generate machine/object code. They should correctly state that the SW was "designed" in UML, or something more accurate. Bempey 03:24, 7 December 2006 (UTC)

OpenBee is modeling a Zigbee stack in UML from which a tool can generate an implementation. The openbee team is actually using C to test the model on their dev board. —Preceding unsigned comment added by (talkcontribs)


In, the part of the introduction beginning with "CCM*", it's not clear that the article is talking about encryption, or what all the acronyms mean. -- Beland 06:05, 19 July 2006 (UTC)

The way this article is written makes my eyes glaze over. And I've been an electrical engineer for 25+ years. Buzz, buzz buzz ... —QuicksilverT @ 01:53, 20 November 2006 (UTC)
Agreed. It has way too much jargon, and the intro needs to be completely rewritten to simplify and break it down for the person who is not in the know. I mean, talking about protocol and standards is all good and fine, but what the heck is the dang product for? What does it do, in terms the layman can understand? --Lendorien 23:28, 6 April 2007 (UTC)

ZigBee node size is small / ZigBee node size is big[edit]

The most capable ZigBee node type is said to require only about 10% of the software of a typical Bluetooth or Wireless Internet node, while the simplest nodes are about 2%[citation needed]. However, actual code sizes are much higher, closer to 50% of Bluetooth code size[citation needed]. ZigBee chip vendors have announced 128 kilobyte devices[citation needed].

So which is it? If these sentences don't conflict they can at least be cleaned up; it really does read like too many people edited it.

What does the 10% versus 50% mean, to say nothing of the 2%? Does the node need smaller data structures than Bluetooth, which is the only explanation that occurs to me? Howard C. Berkowitz 13:19, 18 July 2007 (UTC)

Harmonization with IETF Work[edit]

Is the Zigbee or IEEE work here completely independent of the IETF ZEROCONF and MANET work? Why? Why not? Howard C. Berkowitz 13:19, 18 July 2007 (UTC)

Detailed not technical[edit]

19-Oct-2007: I have been editing several technical articles (such as "Discrete Fourier transform") to add simplified wording, but this article "ZigBee" is not too technical, just detailed in content. The article doesn't even mention "radio field" (or "digital signal processing"). Actual overly technical articles typically have more than 3 rare terms in a sentence (such as aquifer, aquitard & aquiclude) or contain several mathematical formulas; however, this article doesn't involve any of those technical issues. I have removed tag "{{technical}}" and suggested writing a more detailed analysis as to why the article is troublesome. Please don't tag an article as "technical" just because it contains detailed information. -Wikid77 07:50, 19 October 2007 (UTC)

Added section on controversy[edit]

Added section on controversy. Requesting review since this is a very sensitive issue. The section absolutely must appear neutral to all. User:Kcrao Allrite82 (talk) 23:02, 13 December 2007 (UTC)

AfD result[edit]

The article "Drop-in Networking" has been redirected to this location following an AfD. Editors more conversant in the subject than myself may wish to use content from the history of that article to improve this article if they wish. Orderinchaos 13:21, 15 February 2008 (UTC)

Merge ZDO with ZigBee article?[edit]

This discussion is started with two comments from the ZDO Talk Page.

Seems to me this page (ZDO) is really not necessary, as ZigBee Device Object is a component of the ZigBee standard. At best, this ought to be a reference to ZigBee Specification. Al.banting (talk) 16:29, 13 April 2008 (UTC)

  • I SUPPORT the merge proposal! Rationale: ZDO is definitely a minor subcomponent of ZigBee. Also, this page has little to no content and is not sufficient to warrant an encyclopedia page in Wikipedia. N2e (talk) 03:38, 23 July 2008 (UTC)


What frequency band do ZigBee transmitters and receivers actually use?

Every mention of frequency in the current ZigBee article mentions 3 ISM bands, and the frequency limits of those ISM bands. But I am pretty sure that any one particular Zigbee transmitter is physically capable of using only one ISM band.

Do ZigBee transmitters use an entire ISM band, or a smaller part of a ISM band? Do different Zigbee products use different ISM bands, or different parts of the same ISM band, and so are inherently incapable of communicating with each other?

-- (talk) 13:55, 31 July 2008 (UTC)

It would be really nice to add a blurb on zigbee's spectral mask / emissions mask. —Preceding unsigned comment added by (talk) 15:00, 25 September 2008 (UTC)

This concise reference to the bands and data rates comes from an application note, am I allowed to cite the source or would that be advertising?

'The IEEE 802.15.4 defines three frequency bands of operations: 2.4 GHz, 915 MHz and 868 MHz. Each frequency band offers a fixed number of channels, i.e., the 2.4 GHz frequency band offers 16 channels (channels 11-26), 915 MHz offers 10 channels (channels 1-10) and 868 MHz offers 1 channel (channel 0). The bit rate of the protocol depends on the operational frequency. The 2.4 GHz band provides up to 250 kbps, 915 MHz provides up to 40 kbps and 868 MHz provides a data rate up to 20 kbps. The actual data throughput will be less than the maximum specified bit rate due to the packet overhead and processing delays.'

The frequency band you end up using will be depend on the tranceivers that you buy and that would depend on the target country, i.e. the country into which you intend to sell the finished product. -- (talk) 07:13, 15 April 2009 (UTC) Nolfese.

Please check, but I think the 2.4GHz can be used globally and is one of the advantages of Zigbee, as opposed to regional frequencies, which I guess can also be used: "Global operation in the 2.4GHz frequency band according to IEEE 802.15.4 Frequency agile solution operating over 16 channels in the 2.4GHz frequency" Pav — Preceding unsigned comment added by (talk) 10:04, 18 March 2014 (UTC)

Can 802.15.4 and 802.11 inter-communicate at 2.4GHz?[edit]

Xbee wireless programmable sensor modules for $20+ sound interesting, but for many situations that cost is still too much. Worse, to get started you must purchase at least two modules, the remote and a base unit for your computer. But if 802.15.4 and 802.11 can both use 2.4GHz, than it seems like common existing computer wireless interfaces should be physically capable of communicating with 802.15.4 remotes. Is this possible? Can any 802.11 hardware inter-communicate with any 802.15.4 sensor?

Are there any cheaper programmable wireless sensors than Zigbee/Xbee? - (talk) 12:50, 10 June 2009 (UTC)

Regarding the GPL rant[edit]

Not only is this out-of-place, but by my reading it's also perfectly inaccurate.

The license on the free ZigBee specification says that the specification document can be used for "all non-commercial purposes", including "development of non-commercial software, tools and documentation".

Nowhere does it say that this non-commercial software can't be used by a third-party inside a commercial product. Nowhere does it say that this non-commercial software cannot be open-sourced.

What it says is that if you want to use the specification document to develop a commercial product, you must pay.

This is a pretty straightforward piece of licensing, and the GPL guys have no need to get their knickers in a twist over it. ZigBee are placing no restrictions on you, the developer, but only on your use of the specification document, as is their right.

To summarize:

Any developer can download the free specification and develop open-source products (such as libraries) on a non-commercial basis, and release them under the GPL.

Any developer can download that GPLed code and use it in a commercial setting. But, if this developer also wishes to refer to the specification document, he needs to pay ZigBee their fee.

There is absolutely no inconsistency with the GPL. Yet again Stallman's license causes Fear, Uncertainty and Doubt. —Preceding unsigned comment added by (talk) 17:06, 18 December 2009 (UTC)

Well according to their membership FAQ they seem to think that if you use ZigBee in a commercial product you need to be a member: (talk) 22:55, 31 January 2011 (UTC)
They seem to imply that if you are embedding Zigbee into your product you are a developer, which is reasonable. If you can use it in a commercial product without the need for a developer to look at the specification, than you do not need to subscribe. That's what they say, at least --Pot (talk) 12:20, 1 February 2011 (UTC)
The incompatibility exists. Example: I subscribe to the Zigbee alliance, I download and study the specification, then I implement a Zigbee stack and release it under the GPL. You take it, read the specification and modify it. At this point, if you want to use the modifications for commercial uses, you must subscribe to the Zigbee alliance. Whether you choose to subscribe or not, you are imposed a requirement on redistribution that is additional to the GPL. The GPL has a termination clause by which any additional requirements on distribution nullify the licence. This means that nobody but me has the right to do anything with my GPL implementation, as the GPL terminates itself because of the additional requirement. --Pot (talk) 12:20, 1 February 2011 (UTC)

the GPL rant is clearly written with an agenda in mind that is negative towards ZigBee - it doesn't belong in an encyclopedia, it belongs in a commercial/political forum. Just to illustrate the point: the proposed alternative, 6LowPAN and related stack likely contains IP declarations (see IETF) that can't be brought under the GPL either - e.g. many large contributors only promise not to use their IPR but reserve the right to sell it to a party that made no such obligation. Go figure.

— Preceding unsigned comment added by (talk) 20:59, 17 June 2013 (UTC)

But, if this developer also wishes to refer to the specification document, he needs to pay ZigBee their fee.[edit]

I know this is a dumb question but what exactly does 'refer' mean in this context? —Preceding unsigned comment added by (talk) 02:26, 21 May 2010 (UTC)

Zigbee Pro[edit]

Here are a couple references if anyone is interested in adding Zigbee Pro info to the article. --Kvng (talk) 21:49, 27 July 2010 (UTC)

Merge from IEEE 802.15.4-2006[edit]

We have three ZigBee articles with overlapping content. I suggest they all be merged into this article. --Kvng (talk) 13:07, 4 February 2011 (UTC)

No way. IEEE 802.15.4-2006 can't be merged, because it's another entity. (talk) 12:24, 14 February 2011 (UTC)
yeah, ZigBee rests on top of IEEE 802.15.4, along with some other protocols. OsamaBinLogin (talk) 19:58, 14 December 2013 (UTC)

Redundant info in Radio hardware section?[edit]

The data rate metrics given in paragraph 2 are repeated in Para. 3. The only difference is Para. 3 qualifies these as "raw, over-the-air" and they follow a description of modulation types.

DonL (talk) 19:57, 27 September 2011 (UTC)

Zigbee illustration[edit]

The inclusion of a 1 Euro coin (or any coin) is a very bad choice for a size comparison in any illustration. One helpful contributor has added that the 1 Euro is similar in size to a US quarter (actually 1 mm larger) - a great help to those who do not have a quarter handy (virtually the whole planet outside of America). I do not doubt that the majority of the world's population have neither a Euro not a US quarter handy. I have added to the list of coins but I somehow think the average Iranian or New Zealander will still be unimpressed. Granted: it is possible to go to the coin's article and find its size, but then it would be equally valid to simply state the module's dimensions.

It is much better to include an object that is universally avaialable in every country. A milimetre scale would be the obvious choice - though there is one country where most of the inhabitants still have no idea how big a millimetre is. Another choice might be an AA size battery as these are universally available.

Can someone with access to a Zigbee module replace the illustration with one everyone can scale on sight. I B Wright (talk) 13:22, 30 October 2012 (UTC)

I have replaced the photo of the very old module with something up-to-date. I hope the size reference is more suitable. AutolycusQ (talk) 12:04, 19 March 2013 (UTC)

ZigBee certification[edit]

We have "individual devices must have a battery life of at least two years to pass ZigBee certification". That sounds out of date, can anyone provide a current reference? AutolycusQ (talk) 15:45, 14 March 2013 (UTC)

Delete Purely Commercial Content[edit]

The following link in section "External Links" leads to nothing else but purely commercial content complete with directions to call the "Sales Team of AdaptiveM2M":

Because the above link is to nothing else but commercial material I suggest that it is deleted as soon as possible. If no one objects to this message in the next 7 days I will delete the said link.

Regards — Preceding unsigned comment added by (talk) 11:29, 5 October 2015 (UTC)

External links modified[edit]

Hello fellow Wikipedians,

I have just added archive links to one external link on ZigBee. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

YesY An editor has reviewed this edit and fixed any errors that were found.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

If you are unable to use these tools, you may set |needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.

Cheers. —cyberbot IITalk to my owner:Online 05:03, 17 October 2015 (UTC)

Help Needed[edit]

Hi. I am not the best with editing. I do what I can, but I am much batter at finding grammar problems than I am with fixing them. I have added some inline comments with what needs to be done that I can't. Thanks for making Wikipedia even better than it was yesterday! Hungryce (talk) 01:47, 26 January 2016 (UTC)

Did a few fixed based on your comments. The passages of passive voice were left alone. (See what I did there?) The passive voice is appropriate when the actor is not important. If you ask my what I did this morning, then I'd say "I edited Wikipedia", and not the "This morning the Wikipedia was edited by me". On the other hand when the person doing the action is less important, it is left out by using passive voice. So if you write "ZigBee was conceived in 1998, standardized in 2003, and revised in 2006" we are less interested (at this point) in who did the conceiving, standardizing, and revising. --Cornellier (talk) 01:01, 13 March 2016 (UTC)

WiFi/Zigbee rf interference?[edit]

Article needs a section on rf interference. As currently written, the article behaves as though nothing else uses the 2.4GHz spectrum. In the real world, this is nonsense. WiFi channel contention between neighbouring properties is already a significant issue and householders will want to give a far higher priority to optimising neighbourhood channel allocation than to accommodating an ill-behaved appliance like a smart meter (which is the first place most people will see a Zigbee-enabled device). --John Maynard Friedman (talk) 17:37, 10 March 2016 (UTC)

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 4 external links on ZigBee. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

You may set the |checked=, on this template, to true or failed to let other editors know you reviewed the change. If you find any errors, please use the tools below to fix them or call an editor by setting |needhelp= to your help request.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

If you are unable to use these tools, you may set |needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.

Cheers.—InternetArchiveBot (Report bug) 19:24, 20 July 2016 (UTC)

Removing License section[edit]

I am removing the License section because it contains outdated information. Since August 2014, membership is no longer required for commercial use of the zigbee standards - see this archived version of the membership FAQ. Compare that with this earlier version, which clearly describes a closed standard. — Preceding unsigned comment added by (talk) 10:51, 7 August 2017 (UTC)

The FAQ says you still must be a (paid?) member to use the word "Zigbee" in describing your product. --Wtshymanski (talk) 20:52, 7 August 2017 (UTC)

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on Zigbee. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

You may set the |checked=, on this template, to true or failed to let other editors know you reviewed the change. If you find any errors, please use the tools below to fix them or call an editor by setting |needhelp= to your help request.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

If you are unable to use these tools, you may set |needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.

Cheers.—InternetArchiveBot (Report bug) 04:08, 3 September 2017 (UTC)