Zigbee2MQTT:error 2021-03-16 18:51:13: Error: Failed to connect to the adapter

Configuration Zigbee
,
1

Hello,
I have installt the zigbee2mqtt addon and it failed to start with error. Does anyone possibly have an idea how I can solve the problem? Many Thanks in advance!
Werner

These are the error messages:

19:02:38] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start /app
> node index.js
Zigbee2MQTT:error 2021-03-16 19:03:02: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-16 19:03:02: Failed to start zigbee
Zigbee2MQTT:error 2021-03-16 19:03:02: Exiting...
Zigbee2MQTT:error 2021-03-16 19:03:02: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
    at Generator.throw (<anonymous>)
    at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-16T18_03_02_678Z-debug.log

This is my konfiguration:

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.2.110:1883'
  user: mqtt
  password: mqtt
serial:
  port: >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  options: '-d -d'
  log: false
2

Did you try another usb-port ? And an usb extention cable ?

3

Does it exist?

ls -l /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
4

Hi Francis,
many thanks for your quick response and the ideas.
Yes I just tried to use the second USB 2 port of my pi. But after restarting the server I got the same result.
Unfortunately I have no extension cable at hand.
But it has had worked with an older Hass installation.
Thanks, Werner

5

Hi Nick,
many thanks for the hint to check this, but it exist.
I got the same response to the “ls - …” command for both USB ports of my Pi.
Thanks Werner

6

Hi folks,
found some strange lines in the supervisor log. Apparently, the adapter is always removed and then added again:

21-03-17 11:33:54 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
21-03-17 11:33:54 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE usb hardware /dev/bus/usb/001/116
21-03-17 11:33:56 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD usb hardware /dev/bus/usb/001/117
21-03-17 11:33:56 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
21-03-17 11:34:18 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
21-03-17 11:34:18 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE usb hardware /dev/bus/usb/001/117
21-03-17 11:34:20 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD usb hardware /dev/bus/usb/001/118
21-03-17 11:34:20 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
21-03-17 11:34:42 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
21-03-17 11:34:42 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE usb hardware /dev/bus/usb/001/118
21-03-17 11:34:44 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD usb hardware /dev/bus/usb/001/119
21-03-17 11:34:44 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E86BB0-if00
7

Hi all,
Now I fear the zigbee dongle could be defect. How could I check whether it is working properly?

Thanks in advance for your help!

Werner

8

You could try to flash it again.

9

Hi Folks,
got a new cc2531 Usb stick today and zigbee2mqtt is starting now without errors. :smile:
The dark side is that some devices aren’t recognized any more … I have to investigate …
Thanks, Werner