• 2nd Gen.

    The scenario was that Hive had the outage on their APIs but my internet was up... Hive doesn't like this failure mode. It checks internet and if it's available assumes the APIs must be available... when they aren't, the only thing you can do is fully manual boiler control.

    It was a multi-day outage last Autumn.

  • Tado doesn't like it when your internet goes out either, although it does allow manual local control of TRVs / thermostat, and does act as a regulator - it's just the programming that stops, and everything switches to dumb mode.

    I've not checked what happens to water though - I guess it defaults to the last known stated (i.e. on or off).

    I'd love it if they released a self-host option.

  • I'd love it if they released a self-host option.

    The one advantage of the pricier Nest... the thermostat is basically a computer and so the knowledge and control is actually done local.

    This is a bit like Philips Hue... all of the scenes, knowledge of lights, etc... are actually contained in the hub itself so it's local and continues to function when there's an outage.

    The annoying things about some of these IoT systems is the way that they really just want it to be a UI over an API on the internet... but the way those fail during power outages, internet outages or their API going down are just terrible.

    My whole IoT investment now starts with the question: How will this fail? Could this work if deployed off-grid with a shitty power supply? If yes, then I'm all in. I expect to have internet and power... I just don't assume it's always the case.

About