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 
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
Dude! Excellent, I havenāt tried that FW. in that github there are lots of files 20230507 and I grabbed the first one. damn.
So while youāre online, when this is done updating the FW, do you know what the mqtt configuration should be in HA Zigbee2MQTTā¦
server: mqtt://core-mosquitto
user: mqtt-user
password: āpasswordā
Awesome, Iām up and running now.
FYI - the paper that came with the coordinator had 20221226 launchpad as what was pre-flashed. I donāt know what was actually on the device. The main page for the P7 should specifically say CC1352P7_coordinator_20230507.zip because the link goes to the bin full of 20230507ās ā¦ THANK YOU for being so helpful on here.
This thread seemed most relevant but please let me know if I should start a new one.
I just got one of the TubesZB PoE adapters, the āCC2652 P7 Based Zigbee to PoE Coordinator 2023ā one.
I am trying to get it set up with Z2M and I am not having any luck. In the Z2M logs it always fails like this:
2024-02-05T23:01:06.779Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[220,244,213,95,137,77,231,226,132,15,138,222,109,127,226,36],"panID":28825,"extendedPanID":[176,66,41,155,232,77,219,31],"channelList":[11]},"serialPort":{"path":"tcp://192.168.20.27:6638","adapter":"ezsp"},"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-02-05T23:01:06.781Z zigbee-herdsman:adapter:ezsp:uart Opening TCP socket with 192.168.20.27:6638
2024-02-05T23:01:06.789Z zigbee-herdsman:adapter:ezsp:uart Socket connected
2024-02-05T23:01:06.790Z zigbee-herdsman:adapter:ezsp:uart Socket ready
2024-02-05T23:01:06.790Z zigbee-herdsman:adapter:ezsp:uart Uart reseting
2024-02-05T23:01:06.790Z zigbee-herdsman:adapter:ezsp:uart --> Write reset
2024-02-05T23:01:06.791Z zigbee-herdsman:adapter:ezsp:uart --> [1ac038bc7e]
2024-02-05T23:01:06.792Z zigbee-herdsman:adapter:ezsp:uart -?- waiting reset
2024-02-05T23:01:16.800Z zigbee-herdsman:adapter:ezsp:uart --> Error: Error: {"sequence":-1} after 10000ms
Error: Reset error: Error: {"sequence":-1} after 10000ms
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:323:23
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
at Socket.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:152:17)
On the TubesZB side in its log in the web UI I just see a series of:
15:00:50 New client connected from 192.168.20.28
15:00:50 TubesZB Serial Connected': Sending state ON
15:01:00 Client 192.168.20.28 disconnected
15:01:00 TubesZB Serial Connected': Sending state OFF
15:01:06 New client connected from 192.168.20.28
15:01:06 TubesZB Serial Connected': Sending state ON
15:01:16 Client 192.168.20.28 disconnected
15:01:16 TubesZB Serial Connected': Sending state OFF
FWIW, I was able to successfully flash the Zigbee module firmware from within HA using the TubesZB flasher add-on, so the network connection seems to be fine. I flashed the CC1352P7_coordinator_20230507.zip firmware, hoping that would help.
I separately also successfully flashed the ESPHome firmware using a MicroUSB cable.
Both of those firmware updates happened after I first tried to set it up out of the box. So it didnāt work either before or after the firmware update. The error in the Z2M logs is always that same one, Error: Error: {"sequence":-1} after 10000ms.
Any ideas what I can try next?
Looks like you have the ezsp parameter in your z2m config. Remove that and it should work
Oh interesting! I did not notice that and Iām a bit surprised, because in the HA Z2M config web UI, I cleared out the adapter: ezsp line when I switched from a USB dongle to the PoE one.
Iām surprised that it is still using it. All I have left in the serial section is:
port: tcp://192.168.20.27:6638
I will try to clear that out more thoroughly. Thank you for your super quick help!
I double checked that the adapter: line was not present in the config. I had to add it back in with a different value:
adapter: zstack
Now Z2M is starting up and communicating with the network adapter successfully.
Thanks again for the tip!
1 Like
Hello New to TubesZB 
I own TubesZB CC2652P7.
Is there an order to update the firmwares?
Can you update the Esp32 board without updating the zigbee side?
Any side effects of updating the esp or zigbee?
Thanks!
TLDR how can I tell if my CC2652P2 chip is dead? If the chip is dead, is the CC2652P7 a solder-able replacement on the 2022 UEXT board?
The Olimex on my āCC2652P2 Based Zigbee to PoE Coordinator 2022ā recently died (not on the network, not recognized as a USB COM device).
The latest ESPHome firmware for 2022 board flashed to a new ESP32-POE-ISO (didnāt mean to order the ISO, but it should work) and the TubesZB web UI works.
I canāt add the device to ZHA (starting from scratch).
The HA logs look like (I have a download too):
2024-02-27 20:09:36.114 DEBUG (MainThread) [zigpy_znp.uart] Connecting to socket://192.168.1.121:6638 at 115200 baud
2024-02-27 20:09:36.114 DEBUG (MainThread) [zigpy.serial] Opening a serial connection to 'socket://192.168.1.121:6638' (115200 baudrate)
2024-02-27 20:09:41.114 DEBUG (MainThread) [zigpy_znp.api] Connection to socket://192.168.1.121:6638 failed, cleaning up
2024-02-27 20:10:08.398 DEBUG (MainThread) [zigpy_znp.uart] Connecting to socket://192.168.1.121:6638 at 115200 baud
2024-02-27 20:10:08.399 DEBUG (MainThread) [zigpy.serial] Opening a serial connection to 'socket://192.168.1.121:6638' (115200 baudrate)
2024-02-27 20:10:13.399 DEBUG (MainThread) [zigpy_znp.api] Connection to socket://192.168.1.121:6638 failed, cleaning up
The TubesZB UI logs look like:
20:05:00 [D] [streamserver:074]
New client connected from 192.168.2.252
20:05:00 [D] [binary_sensor:036]
'TubesZB Serial Connected': Sending state ON
20:05:05 [D] [streamserver:102]
Client 192.168.2.252 disconnected
20:05:05 [D] [binary_sensor:036]
'TubesZB Serial Connected': Sending state OFF
Iām also unable to update with cc2538-bsl.py and receive the error ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'
Which ESPHome yaml did you flash? There were pin changes between 2022 and 2023. Thatās the only thing I can think of that could cause issues like you see unless there are hardware issue. I do t recall an instance where the cc2652 module died.
Can work out a replacement zigbee module with which ever radio you want - email me at store @ TubesZB.com for that.
Thanks