Migrate from ZHA to Z2M

Configuration Zigbee
,
21

Noob question - do you mean you can take a note of the device name, delete, then repair and copy paste the name back in? is that the most efficient approach?

1 Like
22

Yes. As long as you have control over exisiting names, delete them and rename to the old names you should be good

2 Likes
23

Hi folks, sorry for hijacking but chiming in with my woes instead of a new thread :slight_smile:

I too have decided to migrate from ZHA to Z2M. I decided to take the plunge because my 150+ Zigbee devices were sometimes unreliable. Hope Z2M helps…

Did so by a new Coordinator based on the SMLIGHT SLZB-06,
installed Zigbee2MTT and Mosquito Broker:

Having some strange issues with the devices that were working fine in ZHA (or at least had a full feature set).

For example, I migrated one of my Stelpro heaters over. According to Z2M, features appear and work fine.

In HA however, nothing appears functional:

Another example is with a migrated Ikea light switch ( [E1524/E1810]

I’m not getting battery status and according to HA, it’s missing the left arrow button!

Finally, I have a Aqara TVOC Air monitor that’s showing 0% for battery for some reason.

Not sure if there’s a commonality with these oddities or how best to tackle troubleshooting…

24

ZHA and Z2M are only integrations. The Zigbee network will be exactly the same.

25

Please assist, I do not know what to put for serial:

image
image838×530 13 KB

I am using this sonoff zigbee bridge:

image
image505×439 10.6 KB

and it has tasmota, it was previously working on ZHA but I got stuck with the migration at serial

image
image406×825 23.3 KB

Seems too close yet too far…

26

Depending on what Zigbee firmware is flashed

serial:
  port: tcp://10.0.0.119:8888
  adapter: ezsp

or

serial:
  port: tcp://10.0.0.119:8888
  adapter: ember
27

for both eszp and ember i get the following logfile, it does not seem to have started because I do not get the menu to join other devices:

image
image398×276 3.67 KB

here is the config:

version: 4
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquitto:1883
  user: used
  password: password
serial:
  port: tcp://192.168.68.102:8888
  adapter: ember
  baudrate: 115200
  rtscts: true
advanced:
  log_level: info
  channel: 11
  network_key:
    - 3
    - 138
    - 5
    - 180
    - 66
    - 80
    - 102
    - 173
    - 231
    - 228
    - 15
    - 164
    - 250
    - 229
    - 123
    - 101
  pan_id: 19816
  ext_pan_id:
    - 215
    - 14
    - 36
    - 44
    - 40
    - 189
    - 171
    - 97
frontend:
  enabled: true
  port: 8099
homeassistant:
  enabled: true
onboarding: true

what am i doing wrong?

28

stop Zigbee2MQTT, delete this line, restart Zigbee2MQTT

29

Thanks, there is some action albeit with errors:

image
image1385×507 25 KB

30

Too old firmware. You need this

  adapter: ezsp
31

Finally :slight_smile:

image
image1712×438 11.4 KB

Thanks @francisp

32

I decided to test the Z2M since unlike ZHA that I had, it allows me to interact to the devices by MQTT from other applications. :heart_eyes:

Note that for now I only have 10 devices but even so having to repeat the paring of all of them will be a pain in the a** because the majority is inside the walls so I will have to remove a lot of switch/box covers. :rage:

And in the future if I want to make a clean install of HA, I must repeat the re-paring process? :open_mouth:
Where is the pairing information stored?

  • if it is in the coordinator, why can’t we use it again in another integration?
  • if it is in the HA, why can´t we save it to be reuse in a new HA instance?

Regards

33

On the Zigbee2mqtt github, there is a guide to move from ZHA to Zigbee2mqtt without repairing. On the phone right now, so difficult to provide the link

34

Check if your devices can enter pairing mode by flipping the breaker 5-6 times, should say so in the manual. Saves you having to open stuff up.