I’ve over 40 zigbee devices and am currently using ZHA but keep seeing people recommending using zigbee2mqtt. But I can’t work out if it’s worth the time re-importing all the devices or not.

What are the benefits of using zigbee2mqtt over ZHA and is it easy to move over if that’s the best way to go?

  • thehatfox@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    Zigbee2MQTT supports more devices, and has better support for some devices that ZHA only has basic support. For example I have some vibration sensors which ZHA supports for basic vibration detection, but Zigbee2MQTT can set vibration sensitivity levels as well as detect vibration.

    Zigbee2MQTT also has a more advanced interface with more configuration options, displays more information, and has better network visualisation.

    Another advantage is that Zigbee2MQTT can be run on a different system from Home Assistant. That way the Zigbee coordinator can be placed in optimal location of the home, while the Home Assistant can be located elsewhere.

    If you are already comfortable with using ZHA I there isn’t much need to switch, unless you need support for devices only supported in Zigbee2MQTT or really need to relocate your Zigbee coordinator. Migrating a whole Zigbee network can be a bit of a pain. If you are curious about it you could always buy second Zigbee coordinator and run both.

  • looping@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    When I arrived at home assistant, I appreciated the simplicity of zha, without knowing z2m. When I switched from sonoff v1 (no matter) to skyconnect, I wanted to test z2m out of curiosity. Apart from the slightly longer configuration, it’s a real pleasure. The support for firmware updates is very practical. There are far more parameters available for each device. The only negative point is that it takes longer to start up than zha, but that’s not really a big deal. I don’t regret switching from zha to z2m at all.

  • fixmycode@feddit.cl
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Some things that you might notice are devices going through battery much faster than you might expect, this has to do with the implementation of battery reporting on some devices under ZHA, I can’t say who’s fault it’s it, but at least on Z2M you can even set the reporting intervals manually (if the device supports this)

  • SomeRandomWords@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’m shocked nobody has mentioned it, but the primary advantage of Zigbee2MQTT is the ability to run Z2M on a machine different from HA. ZHA unfortunately doesn’t allow for this, which is a shame because my Z2M box (RasPi) is centrally located but my HA box is not.

  • Napatwork@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Thanks for all the input. It seems that since everything is working fine for me I should just keep using ZHA. Maybe when I have plenty of free time I’ll migrate to get the extra features but it’s not something that I’ve missed.

    • unknowing8343@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Yeah, I just started and the fact that ZHA was “already there” was a huge plus for me.

      I just hope Matter catches up before I find a limitation in ZHA.

  • Technodad@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Is there any difference in network performance, e.g. reliability of communication, or is that all down to the hardware?

    • tehcpengsiudai@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      There’s difference in the implementation of quirks and converters. I found ZHA quirks support less than what Z2M already has, especially when dealing with manufacturers like Aqara.

      Performance wise both felt similar.