I used to just update stuff when I could see an update was available. This changed dramatically when a few months ago, I updated Zigbee2mqtt to version 2 and my whole house stopped working. That marked the moment when the other inhabitants in my house decided that the home automation project had gone too far.

Since then, when I saw an update was available, I’ve waited - preferably until I had seen other people reporting that stuff still worked. But now I’ve realised, that if I wait too long with an update, another update just comes along…

Can I somehow configure HA to always automatically install e.g. update 2.1.3 once update 2.1.4 becomes available? Or is that a nogo too? I realise that the only sure-fire way to do this is with a staging environment, where everything is tested out before updating the production environment. But how many of us has that kind of a setup?

  • chaospatterns@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    12 hours ago

    update 2.1.3 once update 2.1.4 becomes available

    I wouldn’t use that policy because what if 2.1.4 includes a fix for an issue in 2.1.3?

    My update policy is wait until a month comes put, then update to the newest previous month’s version. Patches for bugs go into mainline and are backported so this minimizes bugs in the new features.

    • Ulli@mstdn.social
      link
      fedilink
      arrow-up
      1
      ·
      8 hours ago

      @chaospatterns
      It is interesting how many people think that an update could not contain previous bugs, if they just wait long enough for the installation…