Zigbee2MQTT cannot connect to Conbee 2

Configuration Zigbee
1

I am running Supervisor in Promox as a VM. I have tested the Conbee adapter with deCONZ and it works. However I am not able to get Zigbee2MQTT to work with the adapter. I get the following error in the log. What am I missing?

Zigbee2MQTT:error 2021-07-29 16:36:33: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-07-29 16:36:33: Failed to start zigbee
Zigbee2MQTT:error 2021-07-29 16:36:33: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions
Zigbee2MQTT:error 2021-07-29 16:36:33: Exiting...
Zigbee2MQTT:error 2021-07-29 16:36:33: 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:93: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-07-29T06_36_33_966Z-debug.log
[16:36:34] INFO: Handing over control to Zigbee2mqtt Core ...
1 Like
2

Did you change the path to the device in the config?

And because it’s a VM, did you make the device available to the HA VM?

3

The device is available since deCONZ works. I tried the following (one at a time) in Zigbee2MQTT , but to no avail.

/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2435776-if00

/dev/ttyACM0

test -w /dev/ttyACM0 && echo success || echo failure

reports success :thinking:

my configuration is as follows:

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  user: mqtt-user
  password: password
serial:
  port: /dev/ttyACM0
advanced:
  log_level: warn
  pan_id: 6754
  channel: 15
  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
4

You run Zigbee2MQTT as an addon? So did you with Deconz?

And can you also see the device in the UI? (Supervisor => System => Host (three dots) => Hardware)

And do you run Supervised or HA OS?

5

Both deCONZ and zigbee2MQTT was added to HA as an add on in supervisor


Version
supervisor-2021.06.8
Newest Version
supervisor-2021.06.8
Channel
stable

Yes I can see the device in HA under hardware

6

You can try to set the path to the by-id and force adapter type to deconz

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  user: mqtt-user
  password: password
serial:
  port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2435776-if00
  adapter: deconz
advanced:
  log_level: warn
  pan_id: 6754
  channel: 15
  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

User and pass for MQTT should not be necessary.

5 Likes
7

I set the adapter to deconz and it worked :+1:

thanks for your help

1 Like
8

Running

ls -l /dev/serial/by-id

helped me here to understand that my configuration was wrong and the port was different … the numbers at the end.