If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:ZigBee
| BoxMatrix >> Lexicon >> Smarthome-Terms >> ZigBee | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Software | Research |
Protocol
| Protocol: | ZigBee | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Short for: | Zig-zag dance of a honey Bee | ||||||
| Location: | Lexicon >> Smarthome-Terms | ||||||
| Weblinks: | Wikipedia.int - Wikipedia.de - IEEE-802.15.4 (nonpub) | ||||||
| Description: | Low-bitrate low-power Smarthome standard | ||||||
Goto: FRITZ!OS - Models - Compatibility - Hardware - Firmware - Commands - SMW-Browser
Details
ZigBee is a LR-WPAN based low-bitrate low-power Smarthome communication standard.
The Connectivity Standards Alliance, formerly called ZigBee Alliance, already covers more than 400 Companies
and thousands of products, some of which are:
- Amazon Echo
- Belkin WeMo
- Bosch Smart Home,
- Devolo HomeControl
- Homee
- Ikea Trådfli
- Lidl Smarthome
- Magenta SmartHome (Telekom)
- Google Nest
- Osram Lightify
- Philips Hue (Signify)
- Samsung SmartThings
ZigBee has a hierarchy of 3 device types:
- ZigBee Coordinator (ZC)
- ZigBee Routers (ZR)
- ZigBee End Devices (ZED)
There can only be one Coordinator. It is the master of forming the network topology and chooses the RF channel to use.
Routers communicate with each others and with the Coordinator. End Devices only communicate with their respective
parent Router and not to each others.
FRITZ!OS
Models
So far these models (will or do) have ZigBee support:
| S € |
Model Languages, Brandings |
Internet [Annex] |
LAN Ports |
WLAN 802.11 |
PSTN Lines |
Phones | SoC Clock |
RAM | Flash | USB Host |
Image |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
FRITZ!Box 5690 Pro de, en, es, fr, it, nl, pl 1und1, avm, avme |
AON GPON SVect B, J USB-LTE WLAN |
Gbit: 4 2.5G: 1 ZigBee |
11,530 Mb +5,760 Mb +1,200 Mb 2.4GHz 5GHz 6GHz Wi-Fi 7 |
- | Analog: 1 DECT: 6 |
Alder 2200 MHz RTL96 300 MHz |
2,048 MB | 4,096 MB | Ports: 1 USB: 3.1 |
|
 
|
FRITZ!Box 6670 Cable de avm |
DOCSIS31 32x8+2x2 USB-LTE |
Gbit: 4 2.5G: 1 ZigBee |
2,880 Mb +720 Mb 2.4GHz 5GHz Wi-Fi 7 |
- | Analog: 1 DECT: 6 |
Puma7 2000 MHz |
1,024 MB | 2 MB 4,096 MB |
Ports: 1 USB: 2.0 |
|
 
|
FRITZ!Box 7690 de, en, es, fr, it, nl, pl 1und1, avm, avme |
SVect USB-LTE WLAN |
Gbit: 2 2.5G: 2 ZigBee |
5,760 Mb +1,440 Mb 2.4GHz 5GHz Wi-Fi 7 |
- | Analog: 2 DECT: 6 |
Miami 1100 MHz |
1,024 MB | 4,096 MB | Ports: 1 USB: 2.0 |
|
|
|
FRITZ!Smart Gateway de, en, es, fr, it, nl, pl avm, avme |
LAN WLAN |
Gbit: 1 ZigBee Matter |
600 Mb 2.4GHz |
- | - | Maple 1000 MHz |
256 MB | 128 MB | - | 
|
The list of Connectivity Standards Alliance Certified AVM Products shows all 4 models are ZigBee 3.0 certified.
For the ZigBee capable models 5690pro, 6670 and 7690 AVM states that they are prepared for the Matter standard later,
Since fw 7.63 (2024-10-09) the FRITZ!Smart Gateway supports Matter, latest 7.90 labor for the 5690pro (2024-10-17) does not!
Compatibility
Here 2 useful links to find compatible ZigBee devices:
- AVM: Zigbee-Kompatibilitätsliste (german} - devices officially tested by AVM
- IPPF: AVM-Gateway-kompatible Zigbee-Geräte (german} - community testing devices not listed by AVM
Hardware
ZigBee support by AVM uses the NRF52 RF chip by Nordic, which AVM calls the Network Co-Processor (NCP).
It uses serial port emulation over an internal USB-Host port and identifies itself with vendor id 057c which is AVM.
It is detected by udevd which triggers 95-lrwpan_usb.rules (formerly 95-aflrwpan_usb.rules) to set up 2 tty devices:
- Product id
7101creates the ttyACM0 device and the ttyLRWPAN_NCP symlink - NCP is the Network Co-Processor. - Product id
7102creates the ttyACM1 device and the ttyLRWPAN_PTEST symlink - PTEST is factory side production test
The second device is only created if production test firmware is loaded which only happens during production.
The NCP does not require special Kernel-Modules, just cdc-acm.ko for the tty emulation and usbcore.ko.
It runs the following Firmware which is part of FRITZ!OS:
Firmware
The NRF52 RF chip runs one of the folloẃing firmware files, the version used differs between models:
This is a subset of the Binary-Files section, filtered for '*ZigBee*' or '*NRF52*' or '*ZNCP*' binaries or descriptions.
Daily updated index of all binaries found scanning Firmware-Probes . Last update: 2024-11-14 05:50 GMT.
The label (static) in the Binary column shows there are other objects in this wiki using this name.
The Mod column shows the amount of models using the respective file. Click the column header to sort by this number.
You can hover or click a possible Link in the Type column to see the target of that link.
| Binary | Mod | Firmware | Description | Path | Size/Bytes | Type | Origin |
|---|---|---|---|---|---|---|---|
| zncp-0.2.0.bin | ZigBee Network Co-Processor firmware. | AVM | |||||
| zncp-1.0.0.bin | ZigBee Network Co-Processor firmware. | AVM | |||||
| zncp-1.0.1.bin | 1 | 7.52 | ZigBee Network Co-Processor firmware. | /lib/firmware/lrwpan/hw265_2 | 379k | Blob | AVM |
| zncp-1.0.2.bin | 3 | 7.51 - 7.58 | ZigBee Network Co-Processor firmware. | /lib/firmware/lrwpan/hw265_2 | 367k - 379k | Blob | AVM |
| zncp-1.1.1.bin | 2 | 7.58 - 7.61 | ZigBee Network Co-Processor firmware. | /lib/firmware/lrwpan/hw265_2, /lib/firmware/lrwpan/hw284_1 | 360k | Blob | AVM |
| zncp-1.2.0.bin | ZigBee Network Co-Processor firmware. | AVM | |||||
| zncp-1.2.1.bin | 3 | 7.61 - 7.90 | ZigBee Network Co-Processor firmware. | /lib/firmware/lrwpan/hw279_1, /lib/firmware/lrwpan/hw284_1, /lib/firmware/lrwpan/hw285_1 | 343k - 363k | Blob | AVM |
| zncp-1.3.2.bin | 3 | 7.61 - 7.90 | ZigBee Network Co-Processor firmware. | /lib/firmware/lrwpan/hw265_2, /lib/firmware/lrwpan/hw284_1, /lib/firmware/lrwpan/hw285_1 | 323k - 362k | Blob | AVM |
| 8 files | |||||||
Commands
ZigBee is handled by the alw_zb_gw_app daemon, which is started by the alw_zb_gw_app.service.
It handles the ttyLRWPAN_NCP device and serves the alw_gw_uds.sock socket to all client executables.
One client is the commandline interface alw_zb_gw_cli, which is used by supportdata.aha.
A second client is the ctlmgr plugin library liblrwpan.so, whch maintains the lrwpan ui-module.
Configuration is stored in TFFS in lrwpan.cfg, which is maintained by the ZigBee daemon.
A third client is the aha plugin library libahamodaflrwpan.so, which is the bridge to AHA automation.
The fourth client is the psupportd daemon, which is used for production test and RF calibration.
ZigBee stack:
- Lexicon: ZigBee, LR-WPAN
- Components: NRF52
- Firmware: zncp-0.2.0.bin, zncp-1.0.0.bin, zncp-1.0.1.bin, zncp-1.0.2.bin
- Firmware: zncp-1.1.1.bin, zncp-1.2.0.bin, zncp-1.2.1.bin, zncp-1.3.2.bin
- Devices: ttyACM0, ttyACM1, ttyLRWPAN_NCP, ttyLRWPAN_PTEST
- Sockets: alw_gw_uds.sock
- Sinks: aflrwpan_gw_app
- Commands: alw_zb_gw_app, alw_zb_gw_cli, alw_flash_util, alw_zb_gw_stop
- Commands: supportdata.aha, zb_pcap_dump, uart_flash_tool
- Libraries: liblrwpan.so, libahamodaflrwpan.so, libalwptest.so
- Libraries: libalwncpdfu.so, libalwswdutil.so, libalwncpmgmt.so, libalwudsmsg.so
- Libraries: libcodsu.so, libudev.so, libusb.so, libgpiod.so
- Config: lrwpan.cfg, 95-lrwpan_usb.rules, 95-aflrwpan_usb.rules, alw_zb_gw_app.service
- UI-Modules: lrwpan
- Logs: alw_runtime.log, alw_zb_coordinator.log, alw_gw_crashlog.json
- Temp: supportdata.lrwpan
- Procfs: lrwpan
ttyLRWPAN_PTEST is handled by libalwptest.so for alw_flash_util, which also flashes the firmware zncp-1.0.2.bin
using the alw_swd_flash_nrf52_bin function of libalwswdutil.so.
