Since installing this router, I have had a far better experience with my zigbee mesh. The router, within hours, had hooked up to other routers (mains devices) as neighbors. While I don’t see any neighbors that battery powered devices, I’ve also not experienced a single mesh issues, since.
Well done on this device. Thanks!
Question. I used these Routers (2), but currently need to move one to another Zigbee network (other home). How do I set the router in joining mode. (I removed it from the old zigbee network, but cannot get it to join/advertise on the new network). How do I do this?
To factory reset, open case (it’s a friction fit) and a single press of the BSL button will reset the device.
(from https://github.com/tube0013/tube_gateways/tree/main/tube_cc_router)
Thank you. That worked! (I looked at the shop site, but couldn’t see any info on it there. I didn’t realize there is also a GitHub site)
I just added the router documentation link to github to the shop’s router desctiption.
thanks all!
Hi - may a daft question, but do I need to do anything to activate 20db tx level on router like we do with coordinator (with config). Or is it full power out of the box?
Thanks.
The router FW does not yet support 20db for the tx, it is set to 5. I believe I saw an untested FW floated by someone that had it set to 20db, I will try and find that link.
Great thanks, that would awesome 
.
Do we need any additional hardware for usb to serial connection for flashing (e.g. like usb uart) or just standard USB cable ? Cheers!
You need a serial to usb uart converter. Headers are exposed with pins installed.
I found it - it’s linked in the issues of the z-stack firmware GitHub but the hardware is not defined so not sure which board it is for exactly.
Thanks for confirming and speedy replies! Cheers, 
Hi @tube0013 , not having any luck flashing the router - would you mind seeing if I’m missing something? Here’s my steps:
sudo ./cc2538-bsl.py -p /dev/ttyUSB0 -ewv r_genericapp_CC1352P_2_LAUNCHXL_tirtos_ccs_2.hex
Get the following:
Opening port /dev/ttyUSB0, baud 500000
Reading data from zr_genericapp_CC1352P_2_LAUNCHXL_tirtos_ccs_2.hex
Your firmware looks like an Intel Hex file
Connecting to target...
ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'
Looking at the cc2538-bsl project notes and issues suggest that the bootloader is not being unlocked. They mention that on the cc2538 after it’s been flashed once you need to toggle the select button as well as the BSL one to flash, so I’ve been trying with the RST button but no luck.
I’ve confirmed the serial over ttyUSB0 is working by setting up a screen on that device and catting it, and I can see typing come through.
Any ideas? Thanks.
usually it works for me on the first or 2nd try. I’ve flashed everyone at least twice so I know it works. There should not be a need for anything special like the notes you saw for the 2538.
I typically keep my serial converter powered on and line up the 4 female jumper cable ends, and slip them all on to the pins at the same time while holding the bsl button (I know this should make no difference). Count a slow 10, then release wait another 1 or 2 seconds and fire off the fw command.
I currently have a hue bridge with 45 devices, which works very well. I plan to add more devices, so will be getting closer to the 64 device limit. I am thinking of adding a EFR32 coordinator to my setup for new devices. Should I be worried about using 2 coordinators in near proximity?
Any benefit of switching to EFR32 coordinator over hue bridge?
Secondly, will the router work with the hue bridge?
Any comments?
Thanks
As long as the hue and other zigbee network are on different channels it shouldn’t be an issue. Hue let’s you change the channel too (at least it used to when I last used it)
A non hue coordinator will give you further options for devices, as hue will only support explicitly supported devices and compliant lights I believe.
I don’t think the router would with hue, but have not tested either.
I decided to test this and no, the router didn’t get picked up by my 2nd gen Hue bridge after multiple resets.
Ordered myself another router yesterday evening. @tube0013 thank you so much for your assistance yesterday.
@tube0013 - Good morning - after a glowing review from @code-in-progress (while helping to troubleshoot an issue with my Nortek Zigbee radio) I am looking to find an “easier” (configuration/supportability) radio to use with Zigbee2MQTT.
I THINK I have the concept - but before ordering I wanted to make certain. With a “net new” install, I need a COORDINATOR not a ROUTER. Routers augment and expand an existing network correct? To connect Home Assistant → Zigbee → devices I first have to have the Coordinator (specifically https://www.tubeszb.com/product/usb_coord/11?cp=true&sa=false&sbp=false&q=false&category_id=2 ) then if I needed to extend the range at the fringes/edges add Routers?
(Side question - what is the general range of the “Tube’s CC2652P2 USB Coordinator”?)
yes this is correct, first you need a coordinator, then routers which include most mains powered zigbee plugs/bulbs. (some are better than others, and some are horrible - cough cough osram). I also make a stand alone router.
I’m able to connect to devices across my modestly small house from the coordinator. But I also have a very noisy zigbee/wifi home so I do not know how that effects it. The cc2652P2 has an onboard power amplifier which can be enabled in the z2m or zha config, but things to note with a PA, is it’s only 1-way (sending) power - so if you have a distant sensor it is not going to help much in receiving it’s signal for example. The ethernet connected gateways use the same radio, but allows you (if you have ethernet available) to centrally locate the coordinator to get more even coverage. For example I use ZHA, and my HA Blue is in the back corner of the lower level of my house, not the the ideal spot for the coordinator).
I should probably rename the title of this thread so it’s more generic 
