I’ve just check status, it’s working! In the log entries has now been published like service did start up just after 40 seconds. But I did wait for minutes including went to coordinator website to check. Then searching this site out befor pulishing and pasting log entries. It’s very strange. Sorry to have troubled you.
Thank You for this post I could not figure out why Z2M would not load and it was because I had the wrong port selected. In all of my infinite wisdom I never thought to actually port scan the IP of my tubeszp and find the open port.
1 Like
I am trying to figure out how to update my coordinator firmware.
I have the TubesZB 2022 EFR32 MGM21 Ethernet/USB Coordinator (this has MGM210PA32JIA2 according to the original documentation.)
I am aware of Tube’s Silicon Flasher Add-on, but I can’t find an up to date .glb file.
Tube’s repo at https://github.com/tube0013/tube_gateways/tree/main/models/current/tubeszb-efr32-MGM210-eth_usb/firmware/esphome has not been updated.
Tube’s other repo at GitHub - tube0013/silabs-firmware-builder: Silicon Labs firmware builder has .patch files but I don’t know what base file we are patching.
Anyone able to help? Thanks.
If it has to be built fresh, so be it, but I would not know where to begin, or even why a custom version is needed if it is a stock radio.
Sorry for the confusion, You can find the builds (if not too old) when you are logged into GitHub and look under the Actions and on the build page, you can scroll down to the artifacts.
I just updated github with 7.3.1 fw - some of the confusion is the PoE model used the same FW, and I had not copied it over to the USB Eth folder.
in the flasher you can just point to the gbl file here:
1 Like
Could anyone point me to how to flash my CC2652P2 version1 (square box). I’ve updated the esp32 ok, just having trouble updating ZB chip. TIA.
Regards
Marc.
not working for me even with the raw URL
I’m trying to use the tubeszb coordinator ( tubeszb-cc2652-poe-2023) as I need a new zigbee network in another floor. I’m trying to use zigbee2mqtt as I’m running a zha instance with another coordinator. The problem seems to stem from the serial connection state being OFF.
Any suggestions?
LOGS from ESPHome
I
NFO ESPHome 2023.12.5
INFO Reading configuration /config/esphome/tubeszb-cc2652-poe-2023.yaml...
WARNING GPIO12 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Starting log output from 192.168.72.53 using esphome API
INFO Successfully connected to tubeszb-cc2652-poe-2023 @ 192.168.72.53 in 0.002s
INFO Successful handshake with tubeszb-cc2652-poe-2023 @ 192.168.72.53 in 0.054s
[20:25:28][I][app:102]: ESPHome version 2023.12.5 compiled on Jan 7 2024, 17:37:42
[20:25:28][I][app:104]: Project tubezb.cc2652-poe-2023 version 3.0
[20:25:28][C][logger:443]: Logger:
[20:25:28][C][logger:444]: Level: DEBUG
[20:25:28][C][logger:445]: Log Baud Rate: 115200
[20:25:28][C][uart.arduino_esp32:137]: UART Bus 1:
[20:25:28][C][uart.arduino_esp32:138]: TX Pin: GPIO4
[20:25:28][C][uart.arduino_esp32:139]: RX Pin: GPIO36
[20:25:28][C][uart.arduino_esp32:141]: RX Buffer Size: 256
[20:25:28][C][uart.arduino_esp32:143]: Baud Rate: 115200 baud
[20:25:28][C][uart.arduino_esp32:144]: Data Bits: 8
[20:25:28][C][uart.arduino_esp32:145]: Parity: NONE
[20:25:28][C][uart.arduino_esp32:146]: Stop bits: 1
[20:25:28][C][switch.gpio:068]: GPIO Switch 'zRST_gpio'
[20:25:28][C][switch.gpio:076]: Inverted: YES
[20:25:28][C][switch.gpio:091]: Restore Mode: always OFF
[20:25:28][C][switch.gpio:031]: Pin: GPIO5
[20:25:28][C][switch.gpio:068]: GPIO Switch 'Zigbee Module Bootloader Pin'
[20:25:28][C][switch.gpio:076]: Inverted: YES
[20:25:28][C][switch.gpio:091]: Restore Mode: always OFF
[20:25:28][C][switch.gpio:031]: Pin: GPIO16
[20:25:28][C][restart.button:017]: Restart Button 'Restart the Device'
[20:25:28][C][ethernet:222]: Ethernet:
[20:25:28][C][ethernet:354]: IP Address: 192.168.72.53
[20:25:28][C][ethernet:355]: Hostname: 'tubeszb-cc2652-poe-2023'
[20:25:28][C][ethernet:356]: Subnet: 255.255.255.0
[20:25:28][C][ethernet:357]: Gateway: 192.168.72.1
[20:25:28][C][ethernet:362]: DNS1: 192.168.72.47
[20:25:28][C][ethernet:363]: DNS2: 192.168.72.46
[20:25:28][C][ethernet:383]: MAC Address: E8:9F:6D:D1:0F:83
[20:25:28][C][ethernet:388]: Is Full Duplex: YES
[20:25:28][C][ethernet:393]: Link Speed: 100
[20:25:28][C][ethernet:225]: Power Pin: 12
[20:25:28][C][ethernet:227]: MDC Pin: 23
[20:25:28][C][ethernet:228]: MDIO Pin: 18
[20:25:28][C][ethernet:229]: Type: LAN8720
[20:25:28][C][ethernet:230]: PHY addr: 0
[20:25:28][C][web_server:168]: Web Server:
[20:25:28][C][web_server:169]: Address: tubeszb-cc2652-poe-2023.local:80
[20:25:28][C][mdns:115]: mDNS:
[20:25:28][C][mdns:116]: Hostname: tubeszb-cc2652-poe-2023
[20:25:28][C][ota:097]: Over-The-Air Updates:
[20:25:28][C][ota:098]: Address: tubeszb-cc2652-poe-2023.local:3232
[20:25:28][C][api:139]: API Server:
[20:25:28][C][api:140]: Address: tubeszb-cc2652-poe-2023.local:6053
[20:25:28][C][api:144]: Using noise encryption: NO
[20:25:28][C][streamserver:110]: Stream Server:
[20:25:28][C][streamserver:113]: Address: 192.168.72.53:6638
You have to set up Zigbee2MQTT and point it to the coordinator’s ip/port
was the device in bootloader mode?
You can try the addon if using HASSOS/Supervised HA.
i
LOGS from the zigbee2mqtt addon (fail):
[22:38:11] INFO: Preparing to start...
[22:38:12] INFO: Socat not enabled
[22:38:13] INFO: Zigbee Herdsman debug logging enabled
[22:38:14] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:debug 2024-01-10 22:38:22: Can't load state from file /config/zigbee2mqtt/state.json (doesn't exist)
Zigbee2MQTT:info 2024-01-10 22:38:22: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-10.22-38-22' filename: log.txt
Zigbee2MQTT:debug 2024-01-10 22:38:22: Removing old log directory '/config/zigbee2mqtt/log/2024-01-07.18-01-41'
Zigbee2MQTT:info 2024-01-10 22:38:22: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info 2024-01-10 22:38:22: Starting zigbee-herdsman (0.30.0)
Zigbee2MQTT:debug 2024-01-10 22:38:22: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[144,217,85,238,235,27,113,225],"networkKey":"HIDDEN","panID":61761},"serialPort":{"path":"tcp://192.168.72.53:6638"}}'
2024-01-10T22:38:23.174Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2024-01-10T22:38:23.179Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[116,174,71,119,139,160,120,222,127,118,147,214,54,166,161,63],"panID":61761,"extendedPanID":[144,217,85,238,235,27,113,225],"channelList":[11]},"serialPort":{"path":"tcp://192.168.72.53:6638"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}'
2024-01-10T22:38:23.181Z zigbee-herdsman:adapter:zStack:znp:log Opening TCP socket with 192.168.72.53:6638
2024-01-10T22:38:23.202Z zigbee-herdsman:adapter:zStack:znp:log Socket connected
2024-01-10T22:38:23.203Z zigbee-herdsman:adapter:zStack:znp:log Socket ready
2024-01-10T22:38:23.205Z zigbee-herdsman:adapter:zStack:znp:log Writing CC2530/CC2531 skip bootloader payload
2024-01-10T22:38:23.206Z zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
2024-01-10T22:38:24.211Z zigbee-herdsman:adapter:zStack:znp:log Skip bootloader for CC2652/CC1352
2024-01-10T22:38:24.216Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-01-10T22:38:24.225Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-01-10T22:38:30.234Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-01-10T22:38:30.236Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32] or paste code here
I don’t see any noticiable errors there, all looks okay, does it just stop there?
sorry for my late reply. Full log starting zigbee2mqtt:
[12:06:18] INFO: Preparing to start...
[12:06:19] INFO: Socat not enabled
[12:06:19] INFO: Zigbee Herdsman debug logging enabled
[12:06:21] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:debug 2024-01-14 12:06:28: Can't load state from file /config/zigbee2mqtt/state.json (doesn't exist)
Zigbee2MQTT:info 2024-01-14 12:06:28: Logging to console and directory: '/config/zigbee2mqtt/log/2024-01-14.12-06-28' filename: log.txt
Zigbee2MQTT:debug 2024-01-14 12:06:28: Removing old log directory '/config/zigbee2mqtt/log/2024-01-10.22-11-45'
Zigbee2MQTT:info 2024-01-14 12:06:29: Starting Zigbee2MQTT version 1.35.1 (commit #unknown)
Zigbee2MQTT:info 2024-01-14 12:06:29: Starting zigbee-herdsman (0.30.0)
Zigbee2MQTT:debug 2024-01-14 12:06:29: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"tcp://192.168.72.53:6638"}}'
2024-01-14T12:06:29.511Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2024-01-14T12:06:29.517Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"tcp://192.168.72.53:6638"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}'
2024-01-14T12:06:29.519Z zigbee-herdsman:adapter:zStack:znp:log Opening TCP socket with 192.168.72.53:6638
2024-01-14T12:06:29.585Z zigbee-herdsman:adapter:zStack:znp:log Socket connected
2024-01-14T12:06:29.586Z zigbee-herdsman:adapter:zStack:znp:log Socket ready
2024-01-14T12:06:29.588Z zigbee-herdsman:adapter:zStack:znp:log Writing CC2530/CC2531 skip bootloader payload
2024-01-14T12:06:29.588Z zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
2024-01-14T12:06:30.595Z zigbee-herdsman:adapter:zStack:znp:log Skip bootloader for CC2652/CC1352
2024-01-14T12:06:30.600Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-01-14T12:06:30.606Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-01-14T12:06:36.613Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-01-14T12:06:36.617Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-01-14T12:06:42.620Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-01-14T12:06:42.623Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
Zigbee2MQTT:error 2024-01-14 12:06:48: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-01-14 12:06:48: Failed to start zigbee
Zigbee2MQTT:error 2024-01-14 12:06:48: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-01-14 12:06:48: Exiting...
Zigbee2MQTT:error 2024-01-14 12:06:48: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:60:27)
at Controller.start (/app/lib/controller.ts:98:27)
at start (/app/index.js:107:5)
Check out the trouble shooting page, https://github.com/tube0013/tube_gateways/blob/e90448c5750cc7e3bcf5c1bc795dc3329fdb4902/Troubleshooting.md
Then go to you products firmware directory and pull down the binary and reflash the esp32 over usb.
1 Like
Just posted over in the z-wave category 
1 Like
Hello - a few hours in and just can’t flash firmware. Nor can I start Zigbee2MQTT.
I get the Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) Below is my system info.
I don’t know how to run python scripts or update the firmware in any way but though the HA addon would save the day. With that I have tried triggering the bootloader from the web interface for the TubeZB Coordinator, also tried just enabling that from the addon. Firmware update error is
16:56:20] INFO: Triggering Bootloader mode on 192.168.42.97
unzip: short read
[16:56:28] INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
**********SYSTEM
Add-on: TubesZB TI CC2652 FW Flasher
TubesZB TI CC2652 firmware flasher add-on
Add-on version: 0.2.2
You are running the latest version of this add-on.
System: Home Assistant OS 11.4 (amd64 / qemux86-64)
Home Assistant Core: 2024.1.5
Home Assistant Supervisor: 2023.12.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
this error looks like you are not use the raw url for the firmware, thus the unzip commend is erroring out.
If you right click and copy the raw url, this will be what you want to use.
I still recommend using the the 20221226 release:
Wow - I didn’t get an email that you replied so just saw it as I was going to post an update. I’ll give this update in case it helps others and then look into your suggestion. So, I put a fresh linux install up and learned how to run python scripts. I tried to flash and got this new fresh error:
cc2538-bsl local variable ‘chip’ referenced before assignment
Some googling led me to
Which led me to
I made this modification to line 853 of the python code and it WORKED. So crazy proud of this result out of the rabbit hole …
I have a fresh firmware and now to MQTT …
I am not able to start MQTT with either firmware. I started with the one listed on the product webpage " The current firmware for the CC2652 P7 is the [Z-Stack Firmware Projcet Version 20230507] which does not yet support the changeable TX Power like the P2 FW and is set to 5 dbi. Future FW releases either from TubesZB or the Z-Stack-Firmware project will hopefully add the changeable TX Power."
Then I installed the 20221226 that you recommend.
With 20221226 I get this output below. Is it the P7 version that is the problem ?
[13:07:50] INFO: Preparing to start…
[13:07:50] INFO: Socat not enabled
[13:07:50] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2024-02-04 13:07:52: Logging to console and directory: ‘/config/zigbee2mqtt/log/2024-02-04.13-07-51’ filename: log.txt
Zigbee2MQTT:info 2024-02-04 13:07:52: Starting Zigbee2MQTT version 1.35.2 (commit #unknown)
Zigbee2MQTT:info 2024-02-04 13:07:52: Starting zigbee-herdsman (0.33.5)
Zigbee2MQTT:error 2024-02-04 13:08:11: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-02-04 13:08:11: Failed to start zigbee
Zigbee2MQTT:error 2024-02-04 13:08:11: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2024-02-04 13:08:11: Exiting…
Zigbee2MQTT:error 2024-02-04 13:08:11: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:60:27)
at Controller.start (/app/lib/controller.ts:106:27)
at start (/app/index.js:107:5)
That’s my bad, didn’t realize then you were on a P7.
You’ll want the 2023.05.07 p7 fw:
CC1352P7_coordinator_20230507.zip