TubesZB Coordinators and Routers

⚠️ Site Re-Organization in progress ⚠️

Information and documentation on TubeZB coordinators and routers. Pre-assembed hardware devices can be purchased from https://www.tubeszb.com

TubeZB Coordinators work via serial over Ethernet for use with any zigbee controller project that can access and interface with a remote Serial to IP bridge/proxy server device.

This can today be used by home automation applications such as example; Home Assistant (ZHA integration) and Zigbee2MQTT.

Current Products

Find latest Firmware and Source files

CC2652 Products
	tubeszb-cc2652-poe-2022	CC2652P2 Radio Module + Olimex ESP32-PoE Module
	tubeszb-cc2652-eth_usb	CC2652P2 Radio Module + WirelessTag WT32-ETH01 ESP32 Module
pic	tubeszb-router	CC2652P2 Based Zigbee Router

EFR32 Products
	tubeszb-efr32-MGM12P-eth_usb	MGM12P Radio Module + WirelessTag WT32-ETH01 ESP32 Module

Retired Products - Previous hardware versions

Find the latest Firmware and Source files

CC2652 Products
	tubeszb-cc2652-eth	CC2652P2 Radio Module + WirelessTag WT32-ETH01 ESP32 Module
	tubeszb-cc2652-poe	CC2652P2 Radio Module + Olimex ESP32-PoE Module

EFR32 Products
pic	tubeszb-efr32-MGM112-pro1	MGM12P Radio Module + WirelessTag WT32-ETH01 ESP32 Module
	tubeszb-efr32-MGM210_Series_2	MGM210 Radio Module + WirelessTag WT32-ETH01 ESP32 Module

Getting up and Running

ZHA

For EFR32 Gateways see specific insturctions for config file https://github.com/tube0013/tube_gateways/tree/main/tube_zb_gw_efr32

Auto Discovery for EFR32 Gatways is currently broken in HA, Please ignore the discovered device and set up manually

Connect the gateway to a ethernet cable which has access you your local network.
Power on the gateway with a micro usb cable and power supply. The link lights on the ethernet port will start blinking as it tries to negotiate a connection with your home network router.
Determine the device's ip address If your local network supports .local mdns addresses, the devices can be reached that way:

-for CC2652p based microUSB powered coordinators: tube_zb_gw_cc2652p2.local

-for CC2652p based PoE coordinators: tube_zb_gw_cc2652p2_poe.local

-for EFR32 based coordinators: tube_zb_gw_efr32.local

Using a Reserved or static IP Address is strongly advised. Reserve the address in the router or use a static ESPHome build with static ip
Configure your software to access the device.

For HomeAssistant's Built in ZHA implementation:

Add the ZHA Integration via the Add Integrations option:

In the next window use the dropdown to select Manual:

Select the Radio type:

For CC2652p based gateways select ZNP
For EFR32 based gateways select EZSP

For the Specifying the Port Specific Settings: Enter socket://ip_or_localdns_name:6638 and Port Speed of 115200 and Software Flow Control.

CC2652p Based example:

EFR32 Based example:

Zigbee2MQTT

For Zigbee2mqtt - Only the CC2652p based gateway is supported at this time:

No need to pass any devices through to Zigbee2MQTT docker container setups. The docker containers for Zigbee2MQTT do not seem to work well with mdns, so use the ip address of the coordinator here.

in the Zigbee2MQTT configuration.yaml:

```
serial:
  port: 'tcp://IPADDRESS:6638'

```

ESPHome

The ESP32 in the gateway runs ESPHome. Configured in ESPHome are switches in order to prep the zigbee modules for firmware updates if needed. It is Highly Advised to Ignore these entities in HomeAssistant as accidential toggling could rest the zigbee modules.

To access the ESPHome Web Interface on the gateway connect to it in your Browser:

CC2652p based gateways: http://tube_zb_gw_cc2652p2.local EFR32 based gateways: http://tube_zb_gw_efr32.local

Zigbee Module Firmware Updates:

CC2652p based Gateways:
Firmware - use the CC1352P2_CC2652P_launchpad_*.zip based firmware available here:
https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_3.x.0/bin

Be Sure to backup your device before updgrading as the update will erase the zigbee module completely https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#backup-and-restore

Use the cc2538-bsl programmer available here: https://github.com/JelmerT/cc2538-bsl

Ethernet version :

Prep the Module for firmware update:

Click the button to intiate the bootloader mode for the module:

Watch the Debug output and when pompted go to step 2.

Run the cc2538-bsl programmer:

cc2538-bsl.py -p socket://tube_zb_gw_cc2652p2.local:6638  -evw ../CC1352P2_CC2652P_launchpad_20210120.hex
Opening port socket://tube_zb_gw_cc2652p2.local:6638, baud 500000
Reading data from ../CC1352P2_CC2652P_launchpad_20210120.hex
Your firmware looks like an Intel Hex file
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:21:B4:97:D8
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F980
    Write done
Verifying by comparing CRC32 calculations.
    Verified (match: 0xdb4192ef)

USB Version

Connect the module while pushing the BSL button
Run the cc2538-bsl programmer:

 python3 cc2538-bsl.py -evw -p /dev/ttyUSB0 ./CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Opening port /dev/ttyUSB0, baud 500000
Reading data from ./CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Your firmware looks like an Intel Hex file
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:22:98:3A:E0
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F988
    Write done
Verifying by comparing CRC32 calculations.
    Verified (match: 0xddfc152d)

EFR32 based Gateways

https://www.youtube.com/watch?v=zKrISuWEzL4tube-

ckite/tube_gateways