• ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    1 day ago

    It’s kind of amazing to think about how none of these products are designed to have a fallback functionality during an outage.

    • purplemonkeymad@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      20 hours ago

      Iirc Amazon has a special tooling for creating iot devices. It’s supposed to make creating the communication easier so you don’t have a bunch badly implemented communication systems. Ofc it uses Amazon’s cloud.

      I would not be surprised if they all failed this way due to using the tool. As in the Dev’s code might not even get to know there was an outage, and the tool just keeps telling it the last state it got.

    • locuester@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      20 hours ago

      It’s gotta be more than just an outage that did this. Like seriously, your internet goes out and your bed breaks? Why didn’t we hear anything about this before? Certainly these people have had home internet go out?!

      I’m just imagining it’s a bug of sorts where the bed can access some things but not some other resource specifically not needs so it got caught in an unexpected condition.

      • eldavi@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 hours ago

        npr did a short segment a few years ago of people with smart homes that had problems like this, water stopped running; lights wouldn’t turn on; people forgot passwords to security systems and entry ways.

        some things shouldn’t be connected like this.

      • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        15 hours ago

        It could be that it did happen before, but it was just individual cases and if the outage wasn’t long then probably wasn’t noteworthy. This time it was a whole bunch of people affected all at once for a prolonged period. And you’re likely right that there’s probably a series of states the device can be in, and it does calls to AWS as it moves through them, so probably got stuck at a particular stage and couldn’t move forward cause it couldn’t talk to the mothership.