Terrible time migrating from ZHA to Z2M problems, help needed

I recently migrated my ZHA network to Zigbee2mqtt and so far i’ve had nothing but problems.

I have managed to pair most of my devices with the exception of the following:

Hue Motion Outdoor Sensor I have two of these and one of them is not being found at all when put into pairing mode.

I also have a bunch of device that have been found but the interview never succeeds.

Tuya Zigbee rechargable contact sensor
Sonoff SNZB-03 - (I have 7 of these and 2 of them never succeed at interview)
Sonoff SNZB-04 - (I have 2 of these and one fails interview)

For all the troublesome devices I have changed the batteries and brought them right to the coordinator to pair.

The devices that are paired are not performing very well at all. They frequently don’t update there state and commands are often not sent to HA.

I’m new to Z2M so not sure if this is just a tweak of the config or anything but here is what I have:

I’m using HA Blue with
core-2021.12.8
supervisor-2021.12.2
Home Assistant OS 7.1
ZZH stick from Electrolama

This is my Z2M config:

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
serial:
  port: /dev/ttyUSB0
advanced:
  log_level: warn
  pan_id: 6754
  channel: 25
  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: {}
availability: true
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
zigbee_herdsman_debug: false

I am just curious because I do not use Zigbee. What is your reason for migrating?

I did it because Z2M is compatible with way more devices than ZHA.

1 Like

Thank you. That is understandable.

I left HA 3 years ago due to similar issues with OZW & Z-Wave and just recently came back because of zwavejs.

How’d you get on with this? How did you migrate, dual coordinators or straight up switch leveraging the db on the dongle?

I’m looking to move from ZHA to Z2M, but don’t want to remove and pair 70 devices.

As I understand it, even if you can get the dongle to bring it’s zigbee network over from ZHA to Zigbee2MQTT (which I don’t think can happen), at the next ‘levels up’ the way ZHA and Zigbee2MQTT define/control devices and how they materialize them to Home Assistant are different. IMHO, even with the pain of conversion, I think you will find Zigbee2MQTT a better place to control that number of devices. I would purchase two new zigbee dongles and set up both a ‘production’ and ‘test’ Zigbee2MQTT environment, this is what I have. Going forward, this gives you a way to test new devices and new releases of zigbee2mqtt without effecting your production zigbee2mqtt. If your ZHA network is working ‘well enough’ for a while, I would move at not too fast pace groups of devices from your current ZHA to your production zigbee2mqtt. Make sure to both ‘remove’ each device from ZHA and do a really solid (maybe a couple) resets of each device before adding each to zigbee2mqtt. I’ve used both ZHA and zigbee2mqtt for a pretty long period, and I think you will find a solid environment in zigbee2mqtt. Good hunting!