Local API

Add an API server to the internet bridge (even if it requires newer, more powerful hardware) that supports controlling devices within the local network. Philips Hue provide a great example of how it can be achieved.

My justification is twofold.

Firstly, a local API can be accessed in the event of my internet going down. Ideally the app would be able to detect the internet bridge using something like mDNS. Alternatively its IP can be specified or its "last known" private IP used - this would not be perfect in most cases, but gives options.

Secondly, my main concern when it comes to large investments in smart home is longevity. I do not want to have to shell out for a new heating system anywhere near the frequency I do for a new phone (or even TV or laptop). At some point maintaining support for old hardware will become problematic for Tado - just look at what is currently going on with Sonos and they've been relatively kind in the longevity of their support. A local API would allow owners to continue to use their products in the event that cloud support ends. It would have reduced functionality, but I as the owner would still be able to make the call as to whether I feel it worthwhile to re-invest - and create a whole load more e-waste in the process.

46 votes

Active · Last Updated


  • HGB
    HGB ✭✭✭
    edited February 2020

    Great idea, should have been implemented long ago. Do you mind if I copy it to the Dutch community? Or could you post it there yourself?

  • A local connection to the hub would be great. I currently use a Homey to integrate door and window sensors for precise open window detection plus individual presence detection, etc. That is great and works well provided the internet connection is working.
  • itavero
    edited May 2020

    You could probably use the HomeKit API (if your bridge is new enough) via the HomeKit Controller component in Home Assistant, for instance.

    Of course, a dedicated, well documented, open/public API would be better. 😉

    (PS: besides being an Apple user, the local control is one of the reason I'm a fan of HomeKit)

  • I'd also like to throw in the occasional "security" point of view.

    As you already pointed out, maintaining old hardware is a problem for every company especially from a security point of view. If a local API exist the Phone app could still be capable of connecting locally but access from the internet can be blocked (or non applicable), when security issues with certain EOL hardware arise (or if the user preferred it only being accessible within the same network!)

  • I have the same concern. Indeed, buying the system with 12 radiator valves is not something you want to do as frequent as buying a new smartphone.

    I'm in the process of building a custom internal website hosted in a Raspberry PI to control and monitor my Philips HUE and Siemens LOGO. I would like to add this Tado system to it to reduce the risk of having a non-supported version of the system in a few years.

    Philips opened up their HUE API's.

    Tado, please do the same.