• Dremor@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    I had some difficulties too with Zigbee pairing, that’s one of the shortcomings that Matter fixes with their QR Code pairing. On my case it was just about understanding that you have to put both the device and the coordinator in pairing mode for the “interview” to happen. And that is has to be close to any device of the target network that isn’t battery powered (they can do the interview on the coordinator behalf).

    I stopped using WiFi devices for the same reason, but found out about Tasmota, an open-source firmware for ESP devices. It requires a local coordinator, but never send anything to Google and the likes. It can be hard to flash, but some vendor, like Nous, offers pre-flashed devices. Some of them are also Matter compatible (if it has recent hardware as old ESP device has too little rom to handle the Matter code).

    • interurbain1er@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      The only problem I had with my ZigBee network was pairing the lightbulb but that was because the UX to set the bulb in pairing mode required to switch them on and off 5 1/2 time with a too precise timing for a normal human.

      Mostly an issue with the bulb really.

    • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      This is good information. I had a complete failure with flashing Tasmota once, and bricked a $100 device.

      I like the project, though. My biggest complaint is that - at least for what I was trying to flash, the Linux support was iffy. I was trying to flash something for HA, and the instructions assumed I had access to the computer running HA (which is a headless device in a closet in the basement - entirely unpractical for doing fiddly pinning while trying to flash) or using a web browser with webUSB - which Firefox on Linux doesn’t. So eventually I found a completely unrelated set of instructions I could run from the CLI from my desktop over a cable connected to said desktop, and while it appeared successful, the device is bricked. I can’t even get it into flash mode anymore.

      I don’t think any of this has to do with Tasmota, except that the Linux tooling seems either weak, or make assumes people are running Chrome; and if you’re security conscious enough to be flashing a device to run Tasmota, you’re not running Chrome.

      So I’m not doing that again. It’s a hundred bucks and two days of digging around for tooling and instructions I’d like back.

      Again, not Tasmota’s fault, but it’s not super accessible.