• chaospatterns@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 months ago

    One of the problems with the cloud-polling integrations is that they will frequently poll the back-end APIs to get the current status of that device. A normal user might only open up the app once or twice a day and call the APIs, but these integrations will go 24/7 every 10s-5m. That can add up to a non-trivial amount of traffic. If there’s 100 users opening it up once a day, that’s not a lot of traffic, but 10 users polling every 1 minute is equivalent to 15k people doing something once a day.

    I actually saw one of my integrations I used defaulted to updating every 10 seconds. I decreased that because I didn’t want to draw attention to it.

    A business will look at their usage and ask why there’s more than expected traffic. They could go back and support Matter, that costs money, requires skilled engineers, and cuts into profit margins.

    While it sucks, that is something they could point to in a court about “economic harm”.

    • DeltaTangoLima@reddrefuge.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      I reckon it’s probably not that much. There has to be tens of thousands of customers worldwide that are using their shitty app.

      Forks and stars on the original repo numbered only in the hundreds.

      Cloud services and API gateways usually charge once you get into the millions of requests. Amazon API Gateway doesn’t even charge for having the APIs active - only for the requests that are received and the data transferred out.

      I’m finding it very difficult to believe a few hundred HA users even came close to putting a dent in their cloud bill.