Happy to give that a go. I have the coordinator added via the ESPHome integration, but no config or anything for it like I do for the AirGradient in the screenshot:
Shoot me a private message with the ip and the gateway and I’ll compile a binary for you to try.
1 Like
Thanks, sent you a PM
So upon power restoration today, had the same issue (that was with updated firmware, not the custom version with static IP you made for me).
How the issue presents is Z2M being unable to start. When attempting to access the coordinator via browser it times out. Power cycling the coordinator brings it back online again.
I’ll give your custom firmware a go tomorrow. Just updating here for anyone following along
Hi all,
I need some (a lot of) assistance.
I have an old Tube gateway (square model, with ethernet and USB. The PCB says efr32 pro v2.1)
It has started to play up where it would seem to drop off the network (the ESP side of things pin low/reset etc) would become unavailable and then the zigbee devices would drop off the network. To me that points to a network/ESP/power type issue.
I have decided to blow the dust off it and update it’s firmware/recheck all the connections. I have successfully updated the ESP firmware, but I’m struggling with what files I need and how to update the other firmware(s)?
There is NCP and bootloader, and within those there are different files?
I have seen the youtube video about setting the bootloader pin, rebooting the gateway and sending the firmware file, but I don’t get a response in my serial window.
Please help…
Take a look at the hardware - is the usb port on solidly? This can sometime become loose, but this is more common in situations when the device falls with a cable in the port.
Updating the esphome fw is a good start but I’d go a step further and suggest doing it over serial. On the model you have you can do this with the addition of a 2 DuPont jumper wires. (
).
Scroll down here for the hard ware configuration:
The reason to do this over serial is to clear out any “rusty old bits” in the esp32 flash storage, as it does a full erase first vs the OTA where it just copies over the existing fw flash.
For the efr32 flash - I definitely need to update docs. But now recommend this tool:
It can put the module into bootloader and update the fw. The file you would need is the .gbl file ncp folders.
make sure zha is disabled.
the command to flash would be like this, replacing the ip address and path to the fw file.
universal-silabs-flasher --device socket://192.168.1.136:6638 --bootloader-baudrate 115200 --baudrate 115200 flash --firmware ./build/release/ncp-uart-hw.gbl
Changing the ip address and file path/name for the gbl file.
Note I’d try any address the esp32 serial flash before even looking at efr32 firmware updates as I think the esp32 connection is most likely the issue.
I’m away from home this week so don’t have access to hardware etc to do any physical troubleshooting but happy to help the best I can here, but feel free to direct message or email me at [email protected]
Many thanks for the quick and very helpful reply, it’s gratefully appreciated 
The gateway is mounted up on a wall, so for the moment I have just done an ESP OTA update and it seems to be working better 
I’ll see how it goes over the next day or two and look to taking it down to do a serial update and the other firmware.
Many thanks,
J.
Hi Tubes,
I need help please to change the IEEE address of my POE co-ordinator. It seems to work fine, but it always defaults back to the original “b4” IEEE address. Any suggestions?
How did you know it’s reverting? What does the info command from zigpy-cli show?
Wowza - supafast reply - thank you so much !!
I use the zigstar multi tool to read the address.
I have 2 co-ordinators that are poe and they both have the same behavior’s.
I unplug the ethernet cable and then read the address using the tool after.
I also tried flashing the above multiple times and it always shows the default ieee address as the old one.
I 'm sorry I don’t know zigpy-cli is … can you point me to some docs and I’ll get you the answer … I’m a noob with this python stuff !
Thanks again for your help !
Jason
OK - i’ve installed the zigpy-cli tool … whats the command I need to issue to get the info pls?
well on second though zigpy-I will only show info after a network is formed.
What are you trying to do? The 2 coordinators should have different ieee to start.
I’m preparing a backup co-ordinator - and following the instructions here to try and change the IEEE address to the existing co-ordinator.
https://www.zigbee2mqtt.io/guide/adapters/flashing/copy_ieeaddr.html
I am happilly using one of your round POE co-ordinators and it hasn’t missed a beat in over a year.
I bought a spare older round POE one and a newer rectangle poe one earlier this year.
I am just preparing a backup in case of emergency.
No matter what I try, the spare units go back to their original IEEE address rather than the updated/edited address of the existing POE cordinator.
As far as I know you shouldn’t have to do anything. If you need to move to the new coordinator the z2m backup should just get restored to it (assuming it’s completely blank with no network formed).
Ah ok - I’ll give that a go - thank you !
Confirmed the process works flawlessly - thanks for the confidence and clarification Tubez !
For those interested … here’s what I did to swap to a new co-ordinator:
- Do a HASS backup as well as a Zigbee2MQTT backup.
- Stop Zigbee2MQtt add-on and disable ‘start on startup’
- replace IP address of new co-ordinator in 2 places - HASS UI for the add-in and the configuration.yaml under the zigbee2mqtt directory
- shutdown Hass.
- disconnect old co-ordinator and connect the new co-ordinator
- restart HASS
- check in 2 places that the new ip address of the new co-ordinator is updated - HASS UI for the add-in and the configuration.yaml under the zigbee2mqtt directory
- start zigbee2mqtt add-on in hass
- wait patiently till all the devices slowly but surely emerge !!
1 Like
Just rolled out new 2023 design of the TubesZB cc2652 Zigbee coordinator. Stealing a bit from the PoE models form and an increased modular design for upgrades/swap outs of the radio module. Soon with a cc2652p7 variant too!
The efr32 non PoE coordinators will move to this form factor as well. Including new efr32mg24 modules.
CC2652P2 based Zigbee to Ethernet/USB Serial Coordinator 2023 CC2652P2 based Zigbee to Ethernet/USB Serial Coordinator 2023 – TubesZB
5 Likes
New - I set up some addons for doing Firmware updates to TubesZB (or other) coordinators (both efr32 and cc2652!). consider them beta but I’ve tested both successfully. They will work with Network connected coordinators or local USB ones (have not tested). GitHub - tube0013/tubeszb_addons: Home Assistant add-ons for Flashing TubesZB Devices
Walk through of a cc2652 flash here: TubesZB CC2652 Firmware Flasher Addon Walk Through - YouTube
2 Likes
Hi great add on. I used it yesterday on the older style coordinator.
It kept on doing error 16 I think. It was because it somehow couldn’t turn on the switch for prep for firmware. I had selected it to do this in the config.
Anyway I manually did this, but I unfortunately forgot to turn this off before enabling it in zha, it messed up.
Luckily I had download a backup and restored, all was fine then.
Thanks for the add on.
1 Like
Ok, I took my chances and upgraded my cc2652p2 coordinator using the add-on and other having to add in the step to toggle the “Prep the cc2652p2 for firmware update” switch it all went great! Thanks for the new tool.
1 Like