I know it's early days but it would be nice to have a published API to the service to allow technical users to do things like backup their schedules, integrate with IFTTT, etc. I'm thinking a REST style API via the web - as opposed to any direct interface to the local hardware as I imagine that would be more difficult to provide.
James Saunders commented
For anyone who is interested I have written up a short post which details AlertMe v5 API (which also works for Hive):
Gary Smith commented
Is there any way I can download the actual on/off time that the boiler was called into action? I have a lower temp set overnight, but I'd like to see how much the boiler is actually used during this time period. BG staff have been able to send me a graph for set days, but it would be great to get this data directly.
As an existing Hive heating customer, I should be target market for the new Hive smart plug and other devices. But I won't be buying any of them, and I am now looking at other systems for home automation.
Why am I looking elsewhere? One reason: Hive's lack of a published API or integration with standard services such as IFTTT.
Get that API out there before you miss the boat BG!
There is an un-official API going around on the net can't post on here obviously
There are SO MANY things that could be possible if there was a simple API that allowed developers to read/set schedules, read current temp, set target temp and get notified by callback when the target is changed by the dial control.
NEST has an API so BG are missing a trick my not openning up an API to the community.
James Saunders commented
Please can you release a Hive API? Also is there any plans to upen up the Hive hub for web access much like the Philips Hue API?
This could open up so many possible features and innovations through the dev community (and your own dev team can 'sit back' and watch for the interesting/popular initiatives to help guide you choose which are the most popular to include in your own features).
Let 2016 be the year for Hive to blossom!
I'd like an API to write an Android Wear app to control the thermostat. I'd also like to get historical temperature information.
Any date yet
I'd love a simple REST end point I can poll to get the current temperature of my hive and display on my http://lametric.com
Pete B commented
As posted on the hive FB page, I wonder how long it'll take till we can have an equivalent of this... https://developer.getpebble.com/blog/2015/05/22/timeline-challenge-week-three/?utm_source=Pebble+Developers&utm_campaign=bd00a4097c-News-2015-05-22&utm_medium=email&utm_term=0_9548e2c0aa-bd00a4097c-326064965&mc_cid=bd00a4097c&mc_eid=f579189218
this would be a great feature. provide the flexibility a lot of us want leaving the hive team to add real new features such as add on devices eg wireless trv and external thermometer connection etc rather than add flexible programming to the product itself. api is much easier to implement these days. as mentioned REST would be a good solution as is widely used and open standard. don't go into proprietary APIs. keep it open
IFTT has been mentioned, RESTFUL API would probably open that up but also allows others to create their own tools. I find IFTT has slowed down and I run Pushover notifications through a Raspberry PI. This would with REST be a simple add on for notifications and allow automated off app setting of heating.
AdminHive Product Team (Admin, Hive) commented
It's definitely something we would like to make available in the future and having our own dev community. It comes behind our other key heating and hot water improvements currently. This will make a big difference though: http://www.independent.co.uk/news/business/news/british-gas-to-buy-smart-tech-company-alertme-10044885.html
The Hive team
W C commented
Imagine the load this would take off the dev team if there was an open API folks could leverage their ideas against?
There could even be a dev forum folks could sign up to for access to the API so that the Hive server access could be managed. In much the same way Twitter has access tokens to limit server load.
Matt S commented
Plus one here - would love a chance to customer write my own app to control the heating. Would annoy my wife I'm sure, but it could be fun :)
I too would like an API - but I work in IT and a bit of a techie really, so I'm probably one of relatively few users who would want to program to it directly. However, the real value is that 3rd party apps may start to appear that do some clever things beyond what the standard Hive ones do (although I don't think they're at all bad).
I wouldn't call it an API, but you can of course use the SMS interface with an SMS scheduler to automate some things. For example, yesterday, I knew I was going to be out for about 6 hours during the day, so to save gas I set a constant lowish temp before I went out. But I wanted the house warm again when we got back and didn't want to have to remember to set it remotely. So a used an SMS scheduler (on my Android phone) to send a "heat auto" text to Hive a couple of hours before I expected to be back home. It worked nicely so I'll probably do this sort of thing again.
Crying out for this especially as more devices are added to the Hive platform, let us make those smart plugs work with www.thegengame.co.uk - Let third parties develop cloud based learning functions of Hive won't do it themselves.
Dear Mr Hussain, In September 2013 you said API would come when you are "good and ready". Given that these days delivering even secure API access, is a relatively trivial activity, can I assume that whilst you can easily be ready, you are not GOOD to your word? Or might you be about to publish the API timeline? Starting with IFTT would be a good step, for I can see a number of real advantages, with a sound & movement detector, I could enable an automated heating boost function.
A number of times on the site the Hive team has stated "We don't want to publish dates or promises of updates as we may end up disappointing." It turns out that by allowing your development team to not publically commit to anything you are not only disappointing you are frustrating your customers.
Change the policy: Give your customers the opportunity to vote on the next updated feature then set a date to deliver it, communicating all the time about hurdles and successes, then deliver it; rinse and repeat. You will be amazed at 1) Just how much a focussed de elopement team can do 2) How engaging with your customers in the Co-creation of Hive Features can elate those same customers, and improve your product and brand image. Do NOT allow 5 teams to compete to add the maximum number of updates into the next revision!
Kaizen is by far the best approach to Hive improvement.... Little and often. Next Feature for me IFTT integration, as it releases so much potential.
BTW Signal early when the central control unit is approaching capacity, and give those same customers a chance to vote on the additional functionality of the new unit. There will be beta testers willing to pay for early units... I am one!
Additional Functionality : Wirelessly controlled radiators, electric sockets and light switches. The unit could be dark relying solely on Mobile Device or Tablet Control, but it would still be home based.
This would be fantastic. I could easily add more schedules, boost function, proper geolocation operation, trend and usage reporting over a weekend of coding.
Would love to integrate hive into my home automation system which is custom built right now