17

SmartHome Integration

I am seriously looking at iKettle3 and would like to integrate it into my SmartHome.

In oder to avoid too many Apps and Tools, I would like to integrate iKettle via WEB/REST-API into my FHEM or OpenHAB or OpenAssistant.

Is there an API-description you are able/willing to share with me/developers?

Would be a nice promotion for your product in that community.

Thanks!

Bernd

38 comments

  • Avatar
    Dinique Official comment

    Hello Bernd, 

    Currently the API for the 3rd Gen is closed. 

    Our developers are considering opening it in the future, but this has not been confirmed. 

    Best wishes, 

    Emma 

    Smarter Support

  • 4
    Avatar
    Sebastiaan Jansen

    Hi Emma,

    Quick question, have your developers decided yet on opening a bit of the connectivity on the V3 yet (like with the older versions)?

    I bought an iKettle with the assumption that I could hook it up to my domotica (did a quick google, found a nice github page, didn't realize V3 completely threw away with the nice interface).

    So currently i'm somewhat disappointed and probably going to return the device and look for a used V2 version.. (really don't want to have to do this).

    My two cents on why I think the decision to close the API is somewhat of a bad one in the IoT world, when Smarter would no longer exist (give or take a few years), IFTT would no longer work nor would the google/alexa integration.

    By having an open API you pretty much give your device an additional selling point since lots of developers at home build integration into tons of home automation systems (for free!).

    Can you please check with the development team again? also ask how serious they are considering it (and in what time frame)? 

    Thanks,

    Sebastiaan

     

  • 3
    Avatar
    Torsten

    Hello Emma,

    Sorry about my bad English.

    So why in the future?

    In the future, the Melitta, WMF, etc., will do the same.

    only now you have an opportunity through the SmartHome Community external development and input.

    Help the developers !

     
  • 3
    Avatar
    Nick Clemmons

    I'll throw my vote on this feature! I'd love to control it directly from Samsung SmartThings, especially if temperature and keep warm time were integrated.

  • 3
    Avatar
    Joachim Sörensen

    I also give this feature a vote, Most that i would love to control my smarter coffee, WEB/Rest API

     

  • 3
    Avatar
    bernd

    I see no change or innovation with respect to that subject......

    too bad.

    I am off this company now.

    Sorry!

  • 3
    Avatar
    Ian White

    Gareth, I’m not sure what your point about ‘not opening up’ is.

    Nobody is asking for unfettered access to your platform. Obviously an authentication key would only provide access to our devices, that’s not a moonshot idea, that’s a basic security principle your platform already supports, nothing new is being invented here.

    All we’re asking for is the same access the app currently provides, in api form.

    Assuming you have a half competent dev team that entire infrastructure is already in place bar a potentially different key than the api already authenticates with.

    I can control my entire aws, Azure, gcloud, openshift, blah blah cloud platform with a key and an api. Authenticated api access is a solved security problem.

    I don’t think anyone (and you’re right in that they should be dissapointed) is expected an open http port given your new infrastructure.
    But providing secured api acccess isn’t some new 2019 idea, at best it gets you to 1999?

    You have a great physical product. I still maintain you’ll be ousted long term by a pretty product and decent connectivity - home automation *will* become more mainsteam, and with it the requirement to interconnect. One app per product is not going to cut it past medium term.

    I look forward to the beta , though the need for one puzzles me. I do hope your app is already authenticating securely, using a non binary api, and only has access to ‘my’ devices..

  • 3
    Avatar
    Zoran Sanković

    Hi Gareth,

    instead of looking for excuses why not to have open API, I suggest you to look at other IoT solutions and implement them before it will be too late. IFTTT and talking speakers are not REAL home automation and besides Alexas, Googles and all other talking speakers are very unsafe solutions. If you don't believe me just wait for any commercial on internet radio where Alexa name is mentioned and wait to see what your Alexa speaker will do.

    All I need is that gateway such as Fibaro Home Center 2 can talk to your coffee machine on local network (no internet if possible). As example please see what LIFX did with their API and integration possibilities. I have integrated their bulbs with gateway in one afternoon using their LAN protocol. Benefits for all, me,  LIFX and FIBARO.

    The only question remains is your team actually capable of doing such API integration?

    BTW I have integrated your Smarter Coffee first generation with Fibaro and it works perfectly (found some info about binary comm. of your machine thou). Having coffee ready in the morning when my gateway Alarm clock wakes us up without needing to use any other mobile application I call real home automation. Any other solution is immature because can you imagine if user needs to keep his mobile phone always at reach so can go trough many apps to get his HA gadgets controlled? Stupid.

     

  • 3
    Avatar
    sux bud

    IFTTT are now charging for their service, might be worth opening up that API now cause that's the only reason many of us bought your kettles. If you opened up your API / allowed fully local connection then you'd have a whole new customer base.

  • 2
    Avatar
    Keen Fann

    I want this as well! Please give it to us!

  • 2
    Avatar
    Tim Nesham

    We too would be interested in better API integration for our app. IFTTT is not very good. I imagine there are legal concerns with a 3rd party app sending commands directly to your iKettle?

  • 2
    Avatar
    Charlie Haley

    I am also putting in my support for this, I was disappointed to learn the API has been shut off on the latest version...

  • 2
    Avatar
    Mike Gibbs

    Any update on the Local API?? +200 votes, please. 
    I would like to monitor Water Level (no of cups) , current Temperature, set temperature and Boiling Status. 
    I would also like to be to configure Temperature, start a boil and keep warm timer
    Also, anything else you want to throw in? Maybe Network connectivity status to? 

  • 1
    Avatar
    Christopher Wansing

    Would love to see that! We are a small smart home startup and would sell this device a lot more often if we would be able to integrate it with our system properly!

  • 1
    Avatar
    Michael Hübner

    I'am using the iKettle3 in a privat setting and it's a wonderful device, but I'am a developer too and from that point of view it would add so much more value if you'd open the api/ give keys away. I'm in particular interested in getting the current Temperatur of die iKettle3 via Amazons Alexa or Goggle Assistent  by asking them. Therefore I have to open up the app each time, which is a bit annoying. 

  • 1
    Avatar
    Dinique

    Hi Michael, 

    With the Alexa and Google Home integrations, you can ask them the temperature of the kettle. :) 

    To control with integration you use the name you gave the kettle in the app, if you called the kettle 'kettle' you can do the below. 

    For Alexa simply say "Alexa, what is the temperature of the kettle?" and Alexa will let you know the temperature live temperature of the water in the kettle! 

    The same with Google Assistant but the phrase is “Ok Google, what is the temperature of the kettle?”. 

    Best wishes, 

    Emma

     

  • 1
    Avatar
    Ian White

    I'll throw my vote in for this. 

    Closed IOT products will eventually die to open ones - smart home integration is NOT going to work using an app for every device.

    First(ish) to market is great but the moment an open API competitor comes along anyone serious about home integration is going to drop you and not look back (or simply not purchase in the first place).

    I really like the iKettle 3.0 but it'll be donated the moment an open API product that looks about as good as the iKettle comes along. 

    I wish more companies would understand this, IFTTT integration is simply not good enough.

  • 1
    Avatar
    Gareth

    Hi,

    As I was just pointed to this by someone in the IFTTT thread, let me make our position clear.

    Our current generation products form part of a ruggedised IoT platform, all of which has to comply with various international standards regarding hardware, and many security considerations for the software, firmware and back end infrastructure. There are a number of APIs available to first and second parties, obviously IFTTT, Google and Amazon are examples, but also other organisations who provide Home/ IoT based solutions. All of them work with us under a mutual NDA and are (obviously) able to provide and demonstrate a very, very  serious security focus.

    We have mentioned that we'd consider providing a user API, but this is not 'open' nor is it 'opening up'. The only way we can see this working is that you would apply for an authentication key - this would correspond with your Smarter access and provide you access to the devices you have access to, either on your own device networks, or shared networks to which you are the owner.

    Judging by some of the comments, this isn't going to be what you expect. You're not going to just be able to open a socket and communicate directly with a kettle or coffee machine on your network - not even close. Our devices communicate to the cloud via their own VPN-like connection, which is how our products are safe even on a public network. You will need to communicate via HTTPS with a cloud-based API, with correct authentication, and of course, only access to your own devices.

    We'll consider rolling this out in beta soon, with a limit number of testers. If you're interested, contact us and we'll go from there. 

    But once again I'll point out that this is an enhancement we are considering providing long term - commercial IoT products have no obligation to provide open APIs so don't expect it from everyone, otherwise you're going to be very very disappointed in future as the market can and will tighten up in response to security issues, where the typical outcome is going to be 'Why take the risk?'.

    Cheers,

    Gareth

     

  • 1
    Avatar
    Christopher Wansing

    Hi Gareth,

    thanks for clarifying some of the reasons. I am very positive about your decision to bring this forward by doing a first beta test soon. It is only logical, that the communication will happen secured through your cloud via for example an OAuth authentification.

    I would be comfortable with that and are familiar with this kind of API, so if you´re beta testing it please consider me for a slot.

    Regards, Christopher

  • 1
    Avatar
    Christopher Wansing

    For me it sounds about good. Thanks for the recap.

    Is there already a schedule for the start of the beta that you can share with us?

    Regards,

    Christopher

  • 1
    Avatar
    Tyler Pruce

    Hi Gareth,

     

    Thanks for the info. Any further information on the start of the beta or ways that we could sign up for it?

     

    Cheers,

    Tyler

  • 1
    Avatar
    Jan Werner

    I would never consider buying such a product unless it offers an open API. This API has to be accessible locally and use authentication mechanisms that don't rely on the vendor's server infrastructure.

    We've seen this countless times: a smart device (more or less so) is released, only offering a proprietary API. A year or two later, the vendor goes bankrupt or is sold to another company that has no interest in supporting "legacy" products. Servers are shut down and/or proprietary smartphone apps don't receive any updates and will stop being supported on iOS and Android. End of story.

    Edited by Jan Werner
  • 1
    Avatar
    Serhii Aksiutin

    Public API is a must. See how smart light from Philips Hue made it https://developers.meethue.com/

  • 1
    Avatar
    Roelof Kooijman

    I'm selling my smarter coffee second generation. Looking for something with a public API to connect it with the rest of the smarthome!

  • 1
    Avatar
    o.cape

    I bought this coffee machine because I saw the possible integration with my smart home and was pretty disappointed when I figured it wasn't possible anymore with the 2nd generation. I'm then using IFTTT but native and local integration would made that great machine a perfect machine

  • 1
    Avatar
    Jorijn Smit (Jacko)

    So any news on that API? @Gareth?

  • 1
    Avatar
    Ian White

    IFTT is pricey too . I stopped using it given the speed issues but even if they resolved that, at $10 a month that's yet another non-free 3rd party that shouldn't be needed.

     

    It seems the whole api discussion has basically gone nowhere, which is a shame. 

  • 1
    Avatar
    Serhii Aksiutin

    The issue is this: Few years back, when Smarter was just starting out, they had a major security flaws, where anyone with little command line knowledge could access your wifi password in minutes. Received lots of criticism. So no wonder they are over precautious now. Another thing their support is not very placental to deal with so I assume there is a gap in company's culture and consumer-business relationships. 

    By the way my kettle had died in August (less than a year from day of purchase) and in October they might have another one in stock to replace it 🤯 So you can get a sense of what I am talking about here..

    P.S. I use Siri Shortcuts to go about smart part of this product.

  • 0
    Avatar
    Charlie Haley

    Is there any update on this at all? I find it absolutely insane that this still hasn't been done in nearly 12 months... I'd like to be using this to develop apps and the current limitations are extremely frustrating. 

  • 0
    Avatar
    Gareth

    Hi,

    To help put it in context, we've had no responses based on this - this is what we need to prioritise on.

    Cheers,

    Gareth

Please sign in to leave a comment.