Quantcast
Channel: Configuration - Home Assistant Community
Viewing all articles
Browse latest Browse all 105688

Can't connect to CC2652RB stick after unplugging a different USB adapter

$
0
0

I run zigbee2mqtt in a docker container on a Pi3 separate from my Home Assistant instance.

I recently upgraded to Slaesh’s CC2652RB stick to replace my old coordinator. Everything was working fine until I unplugged my Wyse Sense dongle from the Pi. Now the container can’t connect to the zigbee stick:

Zigbee2MQTT:info  2021-10-11 14:25:29: Starting zigbee-herdsman (0.13.138)
Zigbee2MQTT:debug 2021-10-11 14:25:29: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM0"}}'
Zigbee2MQTT:error 2021-10-11 14:25:50: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-10-11 14:25:50: Failed to start zigbee
Zigbee2MQTT:error 2021-10-11 14:25:50: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions
Zigbee2MQTT:error 2021-10-11 14:25:50: Exiting...
Zigbee2MQTT:error 2021-10-11 14:25:50: 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:102:27)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
    at Zigbee.start (/app/lib/zigbee.js:66:27)
    at Controller.start (/app/lib/controller.js:110:27)
    at start (/app/index.js:95:5)

Here’s how the adapter is mapped to the container:

devices:
      - /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_23_93_33_33-if00-port0:/dev/ttyACM0

I’ve tried everything I can think of short of re-flashing the firmware on the adapter. I’m stumped as to what I’m missing here. Any ideas on what I could try to troubleshoot this before I try the nuclear option?

Thanks in advance.

2 posts - 2 participants

Read full topic


Viewing all articles
Browse latest Browse all 105688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>