Zigbee2MQTT cant find any devices Conbee2 + RPI4

Configuration
,
1

Hello I tried to troubleshoot this but I wasnt able to make it work with anything deConz/Zigbee2MQTT . As a bit of context I was using this exact setup before but then I decided to move to SSD from SD card. After that and loading the backup nothing worked even after multiple tries so I decided to wipe everything and start anew. After fresh install I added mosquito added Zigbee2MQTT added correct serial and i got to the UI but I wasnt able to detect any devicec after accepting joins. I have no errors in log currently. Then I tried the same with deConz and nothing. Then plugged the conbee2 to PC and after few moments I was able to detect and accept the device (both IKEA switch and awara sensor). Then I saw some stuff about newer conbee2 firmware so I downgraded but it didt help. Please fire away any suggestions even the most basic ones thanks.

/config/zigbee2mqtt/configuration.yaml

homeassistant: true
mqtt:
  server: mqtt://core-mosquitto:1883
  user: addons
  password: ahgeir7he8xa8ohhoi9aequieph7xoo6Sohng5paezeedooquasieghai1ohkooH
  keepalive: 60
  reject_unauthorized: true
  version: 4
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2134318-if00
  adapter: deconz
frontend:
  port: 8099
permit_join: true
advanced:
  log_syslog:
    app_name: Zigbee2MQTT
    eol: /n
    host: localhost
    localhost: localhost
    path: /dev/log
    pid: process.pid
    port: 123
    protocol: tcp4
    type: '5424'
  channel: 20
2
  • Does the Z2M log indicate any trouble communicating with the Conbee II?
  • Did you change network key and/or pan id when starting anew?
  • Did you try to factory reset the Zigbee devices?
  • Is the SSD connected via USB3 next to the Conbee?
  • Do you use an extension cord between RPI4 and Conbee?
3

Thanks alot for great points and I probably guess where you are heading with few of them.

Does the Z2M log indicate any trouble communicating with the Conbee II?

dont feel like there is something wrong

[07:19:35] INFO: Preparing to start...
[07:19:36] INFO: Socat not enabled
[07:19:39] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-01-31 07:19:44: Logging to console and directory: '/config/zigbee2mqtt/log/2023-01-31.07-19-44' filename: log.txt
Zigbee2MQTT:info  2023-01-31 07:19:44: Starting Zigbee2MQTT version 1.29.2 (commit #unknown)
Zigbee2MQTT:info  2023-01-31 07:19:44: Starting zigbee-herdsman (0.14.83-hotfix.0)
Zigbee2MQTT:info  2023-01-31 07:19:45: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-01-31 07:19:45: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":88,"product":0,"revision":"0x26580700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:info  2023-01-31 07:19:45: Currently 0 devices are joined:
Zigbee2MQTT:warn  2023-01-31 07:19:45: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2023-01-31 07:19:45: Allowing new devices to join.
Zigbee2MQTT:warn  2023-01-31 07:19:45: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2023-01-31 07:19:45: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-01-31 07:19:45: Connecting to MQTT server at mqtt://core-mosquitto:1883
Zigbee2MQTT:info  2023-01-31 07:19:46: Connected to MQTT server
Zigbee2MQTT:info  2023-01-31 07:19:46: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2023-01-31 07:19:46: Started frontend on port 0.0.0.0:8099
Zigbee2MQTT:info  2023-01-31 07:19:46: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"unknown","coordinator":{"meta":{"maintrel":0,"majorrel":38,"minorrel":88,"product":0,"revision":"0x26580700","transportrev":0},"type":"ConBee2/RaspBee2"},"log_level":"info","network":{"channel":20,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.29.2"}'
Zigbee2MQTT:info  2023-01-31 07:19:46: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2023-01-31 07:19:46: Zigbee2MQTT started!
Zigbee2MQTT:info  2023-01-31 07:23:47: Succesfully changed options
Zigbee2MQTT:info  2023-01-31 07:23:47: MQTT publish: topic 'zigbee2mqtt/bridge/response/options', payload '{"data":{"restart_required":false},"status":"ok","transaction":"1o40l-1"}'

Did you change network key and/or pan id when starting anew?

My lack of knowledge here no idea what that is

Did you try to factory reset the Zigbee devices?

Tried to do that with the official SW looked OK, tried to do that with ZHA and it failed to reset the settings

unfortunatelly yes tried the other USBs also tho, probably should get an extension?

not currently

4

Looks like Zigbee2MQTT is able to communicate with the coordinator device, so no issue with that. The network_key and pan_id are what defines your Zigbee network and devices that joined are paired to this. If you change any of these, you need to re-pair all of your devices. You did not specify any of it, so they are probably at their default.

Easiest is to factory reset the specific device, so it forgets it’s pairing and is ready to pair again. The process usually involves holding a button on that device or turning it off/on in a given sequence. You may want to check the device list on Zigbee2MQTT on how to do it for your devices. Before you do - explicitely set network_key and pan_id to a non-default value. Otherwise any Zigbee device (including malicious) is able to join your network!

Use of an extension cord with USB3 ports is recommended (actually: it’s vital), as USB3 interferes with 2.4GHz networks like Zigbee (or WIFI4).

5

Oh I probably should have stated that i just killed my whole setup and started from scratch. I tried to factory reset aqara temp sensor, Ikea switch and ikea ligh bulb all worked when conbee was connected to PC which i did when I wanted to see what is the problem with my current (reinstalled) setup of RPI. Then i factory reseted Conbee and all the devices too but no were spotted by the Z2M when accepting joining.

6

The extension cord will be vital here. I’m almost certain it’s USB3 interference. Yes you can see comms on the log and it still not be good enwto ‘work’. Mine is even finicky with the extension if the Conbee is too close to the USB3 device…

Get that extension before trying any additional troubleshooting or youll drive yourself nuts trying to figure it out.

7

I will try to find some and give it a try kinda weird that when I was running this setup 3 minths afoi for like 3-4 months with devices in other rooms it worked fine.

8

You ran it for multiple months WITHOUT an SSD. Which is the source of the interference.

1 Like