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 september. 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 | 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 - 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)
- 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
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 |
SFP 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 |
- | Ports: 1 USB: 3.1 |
![]() | ||
![]() |
FRITZ!Box 5690 XGS |
SFP USB-LTE WLAN |
Gbit: 4 10G: 1 ZigBee |
5,760 Mb +1,200 Mb 2.4GHz 5GHz Wi-Fi 7 |
- | Analog: 1 DECT: 6 |
- | Ports: 1 USB: 3.1 |
![]() | ||
![]() |
FRITZ!Smart Gateway de, en, es, fr, it, nl, pl avm, avme |
LAN WLAN |
Gbit: 1 ZigBee |
600 Mb 2.4GHz |
- | - | Maple 1000 MHz |
256 MB | 128 MB | - | ![]() |
For the 5590's AVM states that they are prepared for the Matter standard later,
So far only a FRITZ!Smart Gateway firmware was found, which is the base of all research here.
Interface
The ZigBee interface uses an internal USB-Host port and identifies itself with vendor id 057c
which is AVM.
It is detected by udevd which triggers 95-aflrwpan_usb.rules to set up 2 tty devices:
- Product id
7101
creates the ttyLRWPAN_NCP device - NCP is the Network Co-Processor. - Product id
7102
creates the ttyLRWPAN_PTEST device - PTEST is factory side production test
The interface runs the zncp-1.0.1.bin firmware, which seems to be an update, one of possibly more images.
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
- Firmware: zncp-0.2.0.bin, zncp-1.0.0.bin, zncp-1.0.1.bin
- Devices: 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
- Commands: supportdata.aha
- Libraries: liblrwpan.so, libahamodaflrwpan.so, libalwptest.so
- Libraries: libalwncpdfu.so, libalwswdutil.so, libalwudsmsg.so
- Libraries: libcodsu.so, libudev.so, libusb.so, libgpiod.so
- Config: lrwpan.cfg, 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.1.bin
using the alw_swd_flash_nrf52_bin
function of libalwswdutil.so.
Supportdata
supportdata.aha is prepared for ZigBee debugging - fw 7.29:
if [ ! -z ${CONFIG_ZIGBEE} ] && [ ${CONFIG_ZIGBEE} == "y" ] then LRWPAN_SUPPORT_DATA_FILE=/var/tmp/supportdata.lrwpan alw_zb_gw_cli --supportdata ${LRWPAN_SUPPORT_DATA_FILE} cat ${LRWPAN_SUPPORT_DATA_FILE} rm ${LRWPAN_SUPPORT_DATA_FILE} echo "lrwpan.cfg" cat /var/flash/lrwpan.cfg fi
alw_zb_gw_cli obviously is a commandline interface to an external ZigBee gateway.
LED-Events
The LED drivers libhui.so and hui.ko already know ZigBee related LED events - fw 7.29:
zigbee zigbee_aktiv zigbee_inaktiv zigbee_error lrwpan_pairing lrwpan_pairing_start lrwpan_pairing_error lrwpan_pairing_timeout lrwpan_pairing_success lrwpan_pairing_done
aha
In libahatools.so there's a KPI event prepared for ZigBee - fw 7.39:
KPI_INFORMATION_TYPE_ZIGBEE_EVENT
In libaha.so ZigBee is also named - fw 7.39:
Zigbee IsZigBee