I’m assuming everyone has Zigbee2MQTT, but what do you all have beyond that?

  • vzq@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 months ago

    I run ZHA because it’s the first thing I ran into and moving is a pain. But I’m really curious about the differences, and I’m already running an mqtt broker for other reasons.

    Anyone care to sell me on z2mqtt?

    • asbestos@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      10 months ago

      Nah, I’ve used Z2MQTT for years but switched to ZHA since it’s really mature now, works perfectly fine and is a native “integration”

    • spacemanspiffy@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 months ago

      I moved ZHA -> Z2MQTT earlier this year., mostly due to reading comments in how much better it was. The web interface is better and gives you more control, and setting up Mosquito for an MQTT meant I could use it for Frigate, too.

      Otherwise, device support is basically the same and I notice no difference between the two. For my devices, anyways.

      • corroded@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        I’ve been curious to try Z2MQTT. What’s holding me back is the amount of work involved in switching over. I have 90-something devices paired with ZHA. As far as I am aware, this would require re-pairing all 90 of them individually with Z2MQTT and then re-configuring every automation that uses ZHA (basically all of them). Did you find a way to automate the process?

        • spacemanspiffy@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          10 months ago

          I did it manually (~50 devices at the time). If there is a way to automate it, I am not aware.

          On the bright side, it was a good chance to update the names on all the devices so they follow the same naming convention.

          Then of course, I needed to update all automations and Dashboards to use the new device names.