The visualization is not real-time. Best is to see if the devices work or not.
For the tubes routers you can go in the manage clusters and read an attribute like model or manufacturer.
Some people have had issues with the cc2652/z-stack routers and Sengled bulbs. But it seems to be more the mix of devices and has been pretty rare. In those cases though the sengleds fall offline, not the router.
I moved the tubes router back into my office with the coordinator, reset the router power several times and still cannot query the attributes. READ ATTRIBUTE returns an error.
Thanks for the help!
Try to pair it again, add zigbee device and open case and tap the button labeled BSL
Do you mean to āAdd devices via this deviceā?
Iāve removed it from the coordinator, pressed BSL and rejoined the router. It still fails to READ ATTRIBUTE.
so itās joining and then falls offline immediately? Iāve never seen this happen before. can you enable debug logging - you can do this via the 3 dot menu on the ZHA card uder Devices and Services.
after logging is on rejoin the router again, and once it falls off again disable the debug logging and send it to me via DM here or email [email protected]
thanks.
Sorry for a basic question but where can I check what the current version of my Tubes ZB CC2652 Ethernet Coordinator?
I see the links to the newest firmware but I do not find any mention of how one can check what version the coordinator is currently on.
PS: it was shipped to me in Jan 2023.
Thank you!
It depends on what platform you are using.
I believe itās on a settings page in z2m, on zha you can find it in the diagnostics report for zha if you pull that down.
But shipped in Jan 2023 would have the 20220219 version.
The 20221226 had just come out and I was not shipping it yet.
Thanks @tube0013. In Z2M and under Settings / About it indeed shows the coordinator is indeed 20220219.
I will attempt to update it to 20221226.
Is there a release note available somewhere so that I know whether itās work the risk of me breaking the system? 
I have the Ethernet coordinator. This page says that:
adapters WITH Ethernet the flashing of that module is described in the [ESP32 Flashing section]
My CC2652P2 coordinator has Ethernet but the ESP32 flashing page shows no firmware version 20221226.
Could you please reconfirm which page/firmware I should be reading to upgrade the firmwareon the Ethernet coordinator?
If there is a video guide or clear step-by-step instruction that you could share, that would be hugely appreciated.
Sorry, I am not as experienced with this part and reading through all these pages it is a little uncertain/confusing what one needs to do to update this particular Ethernet coordinator.
Many thanks!
Hi sorry for the confusion.
Every TubesZB ethernet device has 2 modules an ESP32 and a Zigbee module each has their own firmware.
this is the section describing the flashing of the CC2652 Zigbee module.
Thanks for the clarification.
According to this, I have to download the cc2538-bsl which has a number of dependencies (Python, etc. ) and it also says:
To communicate with the uart port of the SoC you need a usb to serial converter:
Sorry, I am lost between all the things listed further below here.
Cannot I just simply use that OTA Update option?
I donāt see any reference to the OTA option among these documents.
I have no experience in Pyhton and donāt want to do something wrong and brick / break the coordinator for good.
Many thanks.
The OTA in the web interface is for the ESP32 / ESPHome firmware.
to do the zigbee fw, follow this:
https://github.com/tube0013/tube_gateways/tree/main/models/current/tubeszb-cc2652-eth_usb#network
The Prep the cc2652p2 for firmware update is the script that runs on the esp32 to put the zigbee cc2652 module into bootloader mode to accept the fw from the flasher tool.
I swear I tried my best to understand this maze of never ending Github links and their circles of dependencies . I am lost.
Run the cc2538-bsl flasher
cc2538-bsl.py -p socket://IP:6638 -evw path_to_firmware_file/CC1352P2_CC2652P_launchpad_coordinator_20220219.hex
Questions:
This script uses the pyserial package to communicate with the serial port and chip (pyserial Ā· PyPI). You can install it by running pip install pyserial .
Sorry for all these questions but as a newbie at t these things, this is super confusing even though I consider myself fairly tech savvy. A step-by-step, clear set of instructions would be super helpful.
I do appreciate you taking your time to help!
You run these commands on the command-line.
In Windows 11 you can open a command-terminal-window or a powershell-terminal window:
Hello, I have one of your ethernet coordinators. Currently I am using ZHA, but I want to switch to z2m. I have installed the z2m add-on in HA and after disabling ZHA, when I attempt to start the z2m add-on I get the below logs. My config setup is shown in the attached screenshot, but I have a feeling there is something simple I am just missing here.
Zigbee2MQTT:error 2023-05-19 11:18:33: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-05-19 11:18:33: Failed to start zigbee
Zigbee2MQTT:error 2023-05-19 11:18:33: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-05-19 11:18:33: Exiting...
Zigbee2MQTT:error 2023-05-19 11:18:33: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open tcp://http://192.168.5.209:6638'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:146:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:76:22)
at /app/node_modules/@serialport/stream/dist/index.js:112:18
get rid of the http:// in the port address.
I knew it was going to be something dumb I did. Donāt know how I missed it.
Thanks! It started up fine now.
Just got my EFR32 and migrated the radio from a conbee.
All of my mains powered devices work fine, but my aqura door and humidity sensors showed unavailable.
Iāve repaired the senors and they get discovered, but they become unresponsive.
are these original aqara devices, not the zigbee 3.0 E and T series? if so that sounds like normal behavior for them. Youāll want to insure when you join them you are joining them through the nearest mains powered routing device (as long as itās known to tolerate the aqaraās behavior) - otherwise they just join to the first thing the see and it likely is not the best path for them.
They are the Original aqara devices. I donāt have any compatible main powered devices, but I didnāt need them before to reach the conbee.
all of your mains powered devices are known not to work with aqara?