This week has a bunch of updates on old favorites for the smart home with a third generation thermostat from Nest and a new home hub from SmartThings. We start the show with Kevin and I discussing the slimmer Nest thermostat with a bigger screen and software upgrades. Our decision? There is no need to upgrade, but the Nest is still a winner. We also review the reviews of the new router from Google and Kevin decides if he can find one, he’ll try it out and report back. But the biggest news on the smart home front is probably the upgrade to the SmartThings hub, which I’ve had in my home since 2013 and is getting an upgrade on Thursday.
Our guest is SmartThings CEO Alex Hawkinson, who covers some of the changes and the new services model the company first unveiled at CES. We also talk about how it is handling Apple’s HomeKit and competition after its acquisition by Samsung last summer. The company has handled the challenge of being open while also trying to make a consumer-friendly product, which isn’t easy, as any Android user can tell you. This iteration may be the one that pushes it into the mainstream. Listen up and see what you think.
Hosts: Kevin Tofel and Stacey Higginbotham
Guest: Alex Hawkinson, CEO and founder of SmartThings
The new Nest is skinner and can double as a clock with Farsight.
Reviewing the OnHub reviews. Should Kevin buy Google’s router?
SmartThings’ new hub is finally here!
How to walk the line between open and usable.
Why SmartThings isn’t supporting Apple’s HomeKit.
As a note to this show, there’s a slight ghosting on Hawkinson’s voice that I couldn’t quite take care of in editing. I apologize.
Technical skills are important when it comes to deploying a new connected manufacturing plant or designing a just-in-time inventory management system. But equally important is developing a management culture that can really take advantage of the data transparency that connectivity can offer a business, according to this week’s guest on the IoT podcast. Satya Ramaswamy of Tata Consultancy Services shares his thoughts about a recent report on the Internet of things and how companies can adapt to really take advantage of this business shift.
This week’s podcast explores how sausage gets made. Actually we explore how roast chickens, cookies and salmon get made. Ryan Baker is the research chef at June, a company making a $1,500 connected oven. When he’s not appearing on the IoT podcast he spends his days baking 15 batches of cookies or 20 batches of salmon trying to figure out how to train the artificial intelligence inside the June oven how to build recipes for certain types of food. It sounds like an amazing job, and he’s in a prime position to explain how technology and food prep can come together to change how people learn how to cook and how the internet of things might invade the kitchen.
We now have four devices for Apple’s HomeKit and about as many slides detailing Google’s own entry into the Internet of things with its Brillo operating system and Weave communications platform. Kevin and I discuss what we know about the Google strategy and more importantly, what we don’t yet know. We also discuss some new research on the use of consumer connected devices in corporate IT networks from OpenDNS and use our 5-minute review slot to talk about the Ecobee 3 and the Lutron Caseta devices that just launched in new, HomeKit compatible versions.
After the break, I interview Chet Pipkin, the CEO of Belkin, which makes the WeMo line of connected devices. We talk about WeMo’s future in the connected home, why connected devices cost so darn much, and how long we can expect until our smart home experience become more automated. I also ask why my WeMo experience seems so glitchy compared to others. For all this and more, listen up.
Hosts: Stacey Higginbotham and Kevin Tofel
Guest: Chet Pipkin CEO of Belkin
Why don’t we know more about Brillo’s details and Weave?
A brief interlude about corporate security
The 5-minute review on Lutron lighting and the Ecobee3
Why WeMo doesn’t always work like you want it
When will our connected devices get cheaper?
Please note, that after we recorded, the Ecobee folks let us know that existing Ecobee3 thermostats are not HomeKit compatible, so you would have to buy a new one.