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)
• 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

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	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	Alder 2200 MHz RTL96 300 MHz		4,096 MB	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!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!Smart Gateway	LAN WLAN	Gbit: 1 ZigBee	600 Mb 2.4GHz	-	-	Maple 1000 MHz	256 MB	128 MB	-

For the 5690's and 6670 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-lrwpan_usb.rules (formerly 95-aflrwpan_usb.rules) to set up 2 tty devices:

• Product id 7101 creates the ttyACM0 device and the ttyLRWPAN_NCP symlink - NCP is the Network Co-Processor.
• Product id 7102 creates the ttyACM1 device and the ttyLRWPAN_PTEST symlink - PTEST is factory side production test

The interface runs the zncp-1.0.2.bin firmware, which is part of FRITZ!OS.
The second device is only created if production test firmware is loaded which only happens during production.

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, zncp-1.0.2.bin
• Firmware: zncp-1.1.1.bin, zncp-1.2.0.bin, zncp-1.2.1.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
• 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-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.

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 

SMW-Browser

Property:ZigBee

Information is currently being retrieved from the backend.