• Buddahriffic@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    6 hours ago

    Ah that’s interesting. If you can swap the devices from one pi to another, try powering it all up on machine A, then swap the devices to machine B and power that on. Might tell you if the issue is with on the pi side or with the devices.

    Is latency higher on the first boot than on subsequent ones? I’d be looking into race conditions if you’re seeing a bit of lag cascade out into bigger problems. Race conditions are the worst, especially when the race most often goes the right way and just occasionally goes the wrong way. Though you can force the wrong way by adding delays in your code, if you have an idea of where the race is happening.

    • ramenshaman@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      5 hours ago

      We have 3 theoretically identical systems here and this same issue occurs on 2 of them. The 3rd one… has bigger issues right now. That would be interesting to see what happens if I swap the Pis around but I’d give it >95% chance the same thing happens.

      • Buddahriffic@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 hour ago

        The important bit is to power one on first before the swap, then you’ll have one setup where the pi was recently powered on and another setup where the connected devices were recently powered on. You might see the issue on only one of the devices, at which point you can say if it’s the pi being off for a while or the devices that triggers the issue.

        • ramenshaman@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          19 minutes ago

          Good point. I disabled the internet on both systems so when I come in on Monday hopefully I can confirm whether or not the date/time aspect is a problem. I’ll try this as well.