Im falling down a hole here. Long story still long, but it started when got a Tuya remote and trying to integrate it. Im currently using the plain old Zigbee Home Automation (ZHA). The new remote got recognized fine, I could see button presses in events but I didnt know hot to use those to trigger events (nothing shows up when try to create an automation).

I found some Zigbee2MQTT blueprints that look like they might work. So I went to install that. Z2M failed starting and is telling me I have a version 12 and I need to update my firmware. So I go to find out the manufacturer wants me to update via a webpage https://smlight.tech/flasher/#home

How the hell do I do this on a headless raspberry Pi? I gotta install a fucking DE for this? ZHA doesnt recognize there is a update needed, hell I cant even tell what firmware version is installed (not that there is any indication what version the update will install).

This is frustrating as hell.

  • pipe01
    link
    fedilink
    English
    arrow-up
    5
    ·
    23 hours ago

    Can you not plug the slzb into your PC and update it there?

    • HessiaNerd@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      That was going to be my next attempt, but it seems risky. Will home assistant recognize it as the same device when I plug it back in?

      All the backups in the world won’t save me in that case. I haven’t eve n been able to confirm what firmware versions there are. I don’t want to have to start from scratch sawping the dongle back and forth.

      I guess I was hoping I was just missing something.

      • ropatrick@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        I think this is the way too. I have never updated firmware on a device via the Pi. Always connected to a PC.

        Can you confirm that you do not have ZHA and Z2M running at the same time?

        • Disable ZHA
        • Uninstall Z2M
        • Reboot device
        • Reinstall Z2M
        • Try to run it again.

        That’s what I would do next.