<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Building for the Home - Medium]]></title>
        <description><![CDATA[Building innovative products for the home that are simple, beautiful, and affordable isn’t easy. Nest‘s designers and engineers are dedicated to creating thoughtful products and solving all of the challenges that get in their way. This blog is for sharing our stories. - Medium]]></description>
        <link>https://medium.com/building-for-the-home?source=rss----c1ee1ae3c1c6---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Building for the Home - Medium</title>
            <link>https://medium.com/building-for-the-home?source=rss----c1ee1ae3c1c6---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:32:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/building-for-the-home" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing a new member of the thermostat family]]></title>
            <link>https://medium.com/building-for-the-home/designing-a-new-member-of-the-thermostat-family-36c81ebc5cb9?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/36c81ebc5cb9</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[nest]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[thermostats]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Mon, 30 Oct 2017 21:05:38 GMT</pubDate>
            <atom:updated>2017-11-13T16:24:10.788Z</atom:updated>
            <content:encoded><![CDATA[<h3>By Diane and Benjamin</h3><p>Since the Nest Learning Thermostat launched in 2011, its highly recognizable design has become an icon for the connected home and shaped how the world thinks about connected devices. The original product was intended as a focal point. It draws attention to itself, showcasing its technology and innovation much like other screens and displays in our lives. And as it grabs our attention, it serves as an active reminder of the benefits it brings: energy savings, cost savings, and peace of mind.</p><p>Over the last five years, our team has iterated, added new features, and fine-tuned the thermostat’s rich interactive experience in pursuit of helping our Nest customers get more from our product and ultimately consume less energy. But, more recently it’s become obvious that we’ve overdosed on attention-grabbing screens and our collective consciousness is asking for other options. As experts in designing for the home, we understand that many people view their home as a sanctuary. It’s a place to shut down, step away from the chaos of our days, and reconnect with those that are most precious to us. With that in mind, our Design team set out to create another option for our customers. Our starting point: How could we create an equally advanced product that blends seamlessly into the home, calling attention to itself only when necessary?</p><p>The first step in solving this was to identifying screen technologies that provide equally compelling robust capabilities as a full LCD screen but that could transform the quality and appearance of screens as we know them. Our industrial design (ID) and hardware engineering teams took the challenge head on, entertaining multiple new and emerging technologies, resulting in a decision to use a <a href="https://nest.tech/the-film-based-materials-science-behind-nest-thermostat-es-ambient-display-5b701a661219">film-based, frosted-display solution</a>. In partnership, the user experience design and software engineering teams validated the screens capabilities and set out to optimize our beloved features on this new canvas.</p><h4>What goes into a thermostat experience?</h4><p>Our user experience team doesn’t just think about what’s in the app. We design our products as a full system, equally addressing the feature development, the physical interaction, the device user interface (UI), the app experience, and even details like the audio design. To that end, we started this process by addressing our new technology and exploring concepts with a wide range of directions. Some were small visual tweaks, while others questioned the entire architecture of our existing thermostat. It was important that we allowed ourselves this space (conducted over a two-week period) to avoid making any wrong assumptions about the best possible experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XeRaZQmwk4ajzHZ1." /><figcaption><em>A peek into some explorations and brainstorming</em></figcaption></figure><p>After that phase of idea generation came to a close, it became immediately clear to us that this new product needed to feel like a natural evolution of our thermostat product line. The physical design had already created a precedent of this new thermostat being a sibling to the original, so it felt intuitive to treat the interface similarly. At this point, our attention shifted. We dove deeper into our chosen direction and began to question how we could strategically allow for the product to achieve two things simultaneously:</p><ol><li>Differ in areas where their form, design and intent suggested they should naturally diverge.</li><li>Maintain a connection of similarity such that a single household could house both devices without causing any confusion to the family living there.</li></ol><p>We began a period of editing,meticulously combing through each of the existing product components and applying our emerging goals: clarity and familiarity.</p><h4><strong>The Thermostat Interface Experience</strong></h4><p>At the core of our design effort was the UI of the main dial screen on the device. Here, we put an emphasis on reduction. If you break down the screen on the Nest Learning Thermostat, much of the design is leveraging a pixel-dense, detail-driven screen. Visual elements are used to provide specificity, but at the same time, they add a layer of visual complexity. In applying our principles, we approached the new product by removing UI elements that weren’t critical to the interaction of adjusting temperature. This allowed us to reduce visual complexity and align closer to our new screen’s capabilities.</p><p>For example, we reduced the amount of written information on the main dial screen, allowing space for the more important temperature value elements to be enlarged and to use bolder characters with more saturated colors. We removed detailed elements like the ticks that mark the temperature gauge. And we created more meaning from maximizing and leveraging the white space itself. Additionally, we combed through our secondary screens and templates to increase type size overall and reduce the use of motion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Nm5ai_3QdAmI-LpI." /><figcaption><em>Several UI elements were removed on the Nest thermostat E to achieve simplicity while maintaining clarity</em></figcaption></figure><p>Given that the new frosted display not only influenced what we put on the screen, but also influenced how users might perceive these elements differently, we ran a series of user studies. These focused on understanding overall usability implications of this new technology and they were able to highlight nuances that were critical to the fine-tuning of our designs. But most critically, this process allowed us to understand the overall legibility as it correlated to screen brightness.</p><p>The frosted display technology that we’re using creates a barrier filtering out light emitted from the screen. However, the legibility for the customer is directly related to that brightness. Since the device uses an ALS (Ambient Light Sensor) to determine the light in the room and adjusts our screen accordingly, our team along with the engineering team set up camp in a very dark room, and with great patience, we slowly adjusted the room light and the device brightness until we calibrated a brightness curve suitable for all key environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eVSFO2kAVug6ijjm." /><figcaption><em>The Nest Thermostat E has proportionally larger type, brighter colors, and simpler visuals</em></figcaption></figure><h4>The App Experience</h4><p>As a team, we treat the Nest App experience as an extension of the device. Interactions on the app should remain familiar to the hardware interactions. And you should always be able to tell which app controllers mirror which devices. Despite phones not having a rotary control or a frosted display, we looked to use a similar visual language to enforce this intended connection.</p><p>Our Nest App designs balance skeuomorphic visuals with abstracted controls to retain cohesiveness with our devices. For the Nest Thermostat E, we chose a soft gray background to match the device, designed a subtle edge to represent the lens and provide a guide for the rotary movement of the UI elements, and aligned content to ensure consistent messaging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YCywOqRjmS9qwTiQ." /><figcaption><em>The App experience changes with the device across heating (left), idle (middle), and cooling (right) states</em></figcaption></figure><p>One of the main ways customers use the app is to control the thermostat when they’re away from home, so we needed to communicate clearly when the HVAC system is running and when it’s not. The Nest Learning Thermostat’s screen is blue when the air conditioning is running, and orange when the heat is on. For consistency with the thermostat design, we decided to keep the orange and blue numbers and opted instead to introduce soft background gradients as representation of system activity.</p><h4>The Audio Design</h4><p>When it came to the sound design of the original Nest Learning Thermostat, we took a “less is more” approach. This is evident with the subtle, yet satisfying and surprisingly rich “click” sound that emanates from the device when turning the outer ring, corresponding visually to individual temperature degree hashmarks on the screen. It sounds like the mechanical output of the parts, but it’s not — it’s actually a digitally controlled element.</p><p>For Nest Thermostat E, it was imperative that we enhance the user experience with delight beyond the screen. We introduced a new audio UX that highlights and underscores the UI and ID, while at the same time retains the satisfying thermostat audio UX that our customers have come to expect.</p><p>The solution: an ascending and descending pitched click sound that perfectly matches with both the visual UI and the buttery smooth turning of the outer ring when adjusting the temperature up or down. Using the same underlying audio circuitry, we were able not only to add a new bit of innovation and delight, but also to maintain consistency across devices.</p><p>Once we settled on the ascending/descending pitched click idea, the next step was to begin prototyping so we could hear what this would actually sound like. We collaborated closely with the embedded software team to create a process that allowed us to bypass the normal SW implementation pipeline and quickly iterate builds on device. This was a crucial step that enabled us to easily try out and review ideas without burdening our engineering team. This also let us hear how the sound was affected by the inherent acoustic resonance of the new device (which is a different material than the original thermostat), and make quick adjustments to the frequency parameters in order to optimize the resulting click sounds.</p><p>One big challenge was to design the frequency response of the clicks so that they struck just the right balance — noticeable and impactful, yet not so overt that the result felt too whimsical or off-brand. Thinking about this through a music theory lens, we started with beginning and ending frequencies that were well over three octaves apart. After some initial excitement at hearing this on device, we realized that this sounded a bit too much like a toy, not a trustworthy piece of home technology. Next we tried a single octave spread. This felt closer but wasn’t quite hitting the sweet spot yet. Finally we implemented a frequency interval of a perfect fifth (in this case, the “notes” were C and G), and this struck just the right subtle-yet-delightful chord that we were looking for.</p><p>After a relatively short time of gathering input and continued iterations, we gained a very strong consensus supporting a final design.</p><p>So, in the end, Nest Thermostat E was a many-person, multi-faceted challenge to truly design technology that can recede to the background of our lives. Rather than aspiring to an experience that captures your attention, we were able to balance the amazing technology with a quiet and serene effect. And with this we’ve been able to give our customers options that best suit their lives. This marks the beginning of a journey for Nest Design as we explore and define ways to cater product experiences for different needs. It’s one step closer on our journey to create thoughtful experiences for all people and homes, everywhere.</p><p>Join us in our mission <em>to create a home that cares for the people inside it and the world around it</em>; click <a href="https://nest.com/careers/life-at-nest/">here</a> to learn more about us and to check out our open career opportunities.</p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c81ebc5cb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/designing-a-new-member-of-the-thermostat-family-36c81ebc5cb9">Designing a new member of the thermostat family</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The film-based materials science behind Nest Thermostat E’s frosted display]]></title>
            <link>https://medium.com/building-for-the-home/the-film-based-materials-science-behind-nest-thermostat-es-ambient-display-5b701a661219?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/5b701a661219</guid>
            <category><![CDATA[nest]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Mon, 02 Oct 2017 16:35:22 GMT</pubDate>
            <atom:updated>2017-10-06T18:17:26.898Z</atom:updated>
            <content:encoded><![CDATA[<h3>By Giancarlo &amp; Kevin</h3><p>When our industrial designer, Sung, showed a first conceptual rendering of the new Nest Thermostat E, we were blown away. It was a seamless glowing pebble, floating on a white wall, with warm glowing numbers on the screen.</p><p>The design intent really resonated with us. Instead of making more “smart” products that fill your walls and tables with harsh and technical black screens, we would be creating a product with understated intelligence, a product that gracefully blended into the background, a product that was as much a design element as a piece of technology, a product that echoed the materials of the home, all while being priced for less than the company’s other thermostat offering.</p><p>Our first reaction was, “Wow! This is amazing!” and our second reaction was, “Well… how are we going to make this happen?”</p><p>Based on the renderings, it looked like we wanted to have some sort of dynamic glowing interface that could live behind a smooth light-colored surface — something that would not be visible when the interface was off, but where dynamic numbers or other elements could glow, almost as if they were magically floating on the surface of the product. There was no clear indication of where the display began or ended — it was as if the entire product was a display.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mURAQHPKZGjpsl_N." /><figcaption><em>Experimental Setup for Testing Film</em></figcaption></figure><p>After searching for any products that had hidden displays, we couldn’t find anything out on the market that came close to meeting our goals, so we knew that we would have to develop some new technology.</p><p>We broke the problem down into two areas:</p><ol><li>Generating the dynamic glowing images</li><li>Finding light-colored materials that could not only hide the display’s boundaries but also allow sharp images to shine through</li></ol><p>We gathered a wide range of display technology samples and materials. However, after countless prototypes, we still hadn’t found a way to recreate the drama of the ID rendering. We found images were either too dim, the boundaries of the display too obvious and dark, or the image became unreadable. Every change that improved one aspect came at the cost of degrading another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hq0Yar2ekVVqyNC6." /><figcaption><em>Irene (in yellow) debugging lens assembly fixtures</em></figcaption></figure><p>Eventually, just as we were about to give up, we tried a material that was historically used for an entirely different application. This film, when combined with a white ink layer, and laminated to our front lense allowed more of the desired light to pass through from the LCD, while still remaining opaque and light-colored enough to hide the boundaries of the system when off. Of course, this was only the starting point. We found creative ways to situate the display as close to the film as possible in order to keep the image sharp, while preventing the materials from wetting out against each other, which would create dark spots. We worked with teams across Nest to make the product both manufacturable and beautiful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f-QuA69ezEWOsPTB." /><figcaption><em>Sung comparing material colors of Nest Thermostat E display in a light booth</em></figcaption></figure><p>And so, after a long and arduous process, we’ve built a product that is truly unique, innovative and thoroughly Nesty. We’ll know we’ve done our jobs if Nest Thermostat E owners <em>don’t </em>notice the product. And of course, when it helps people save energy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/0*EdoEsvY018dLu9KM." /><figcaption><em>Kevin and Michael cleaning the Nest Thermostat E display</em></figcaption></figure><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b701a661219" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/the-film-based-materials-science-behind-nest-thermostat-es-ambient-display-5b701a661219">The film-based materials science behind Nest Thermostat E’s frosted display</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beautiful products & the engineering behind them]]></title>
            <link>https://medium.com/building-for-the-home/beautiful-products-the-engineering-behind-them-1034d0bc6510?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/1034d0bc6510</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[nest]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Fri, 22 Sep 2017 02:57:24 GMT</pubDate>
            <atom:updated>2017-09-22T02:57:26.418Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Nik</h4><p>This week we revealed <a href="https://nest.com/alarm-system/overview/">Nest Secure</a> — our simple, beautiful, feature-packed home security solution. Making products that are simple and intuitive to use takes a lot of hard engineering.</p><p>There were innumerable technical challenges along the way, and we are fortunate to have an amazing team of Nesters who worked hard on innovative solutions to bring these capabilities to life. I hope you all enjoy this short video that provides insight into one component — Nest Detect, our universal sensor — and the team that made it possible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FENutUDrxZXw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DENutUDrxZXw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FENutUDrxZXw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/414e45143a735fe3f4e467bc9d3ef23b/href">https://medium.com/media/414e45143a735fe3f4e467bc9d3ef23b/href</a></iframe><p>Join us in our mission <em>to create a home that cares for the people inside it and the world around it</em>; click <a href="https://nest.com/careers/life-at-nest/">here</a> to learn more about us and to check out our open career opportunities.</p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1034d0bc6510" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/beautiful-products-the-engineering-behind-them-1034d0bc6510">Beautiful products &amp; the engineering behind them</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hinging on Design: Nest Cam IQ’s Hinge]]></title>
            <link>https://medium.com/building-for-the-home/hinging-on-design-nest-cam-iqs-hinge-22efb899ce76?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/22efb899ce76</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[cameras]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 20:02:16 GMT</pubDate>
            <atom:updated>2017-09-13T20:53:00.750Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>By Rafat and Tristin</strong></h4><p>In June, we introduced the Nest Cam IQ. Well-proportioned and seamless, it brings out the best in Nest hardware design and engineering innovation. When we started design work, we looked at it as a wide-open opportunity to define the new generation of indoor camera. Our objective was to design an <em>evolution</em> of the existing Nest Indoor Camera and make it feel even more Nesty.</p><p>To us, <em>evolution</em> meant keeping the aspects that people love and adding values that make their experience better, with a friendlier and more approachable design that blends well into homes.</p><p>After an in-depth evaluation of our own indoor camera and user trends, one of our top insights was that offering huge hinge articulation was one of the key differentiators that made our Indoor Cam so successful in the market. Camera users want this range of articulation to handle all the ways they use the camera, where they place it and what they want to see from each location.</p><p>With this learning in mind, we explored ways to make it even better by introducing more integrated and balanced design with the new generation.</p><h4><strong>Design Choices</strong></h4><p>One of the first things you notice when setting up your Nest Cam IQ is that the power cable plugs into the base, not the camera head, allowing for clean routing away from your device. We challenged ourselves to have the cable routing go through the hinge mechanism and have the power plug into the base for seamless look and solid stability. If we could do that, we’d create one of the slimmest, most versatile, and most elegant hinges on on any consumer device.</p><p>This was an important design choice we made in building Nest Cam IQ, but it also brought major design and engineering implications. How do power and data signals get from the base to the head through a tiny hinge? And how can the hinge move through such a large range of motion without any wires ever being seen?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*9_FQMOLHZH_pfTFjISQVSA.png" /><figcaption>Evolution of the Nest camera hinges</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CEsAVpN02dOTI5WB." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H3JCnTXOvxL04uaQ." /><figcaption>Early from Nest Cam IQ hinge design</figcaption></figure><p>We explored several mechanism designs to solve these problems. Ball joints were a natural design choice with our device form factor, but we quickly realized we couldn’t achieve the range of motion we wanted without pinching and exposing wires. Pogo pins, spring contacts, and flexible goosenecks are other common ways to route electrical signals through a moving joint, but each of these concepts either lacks the full range of motion we desired, or was aesthetically unacceptable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*HtLFlv8m-GYk4Sc1vyr3pw.png" /><figcaption>Early ball joint concept</figcaption></figure><p>Flexible printed circuits (FPCs) are another common technology to route electrical signals through tight spaces. However, FPCs are thin and flat, which means they are suitable for bending in one direction. Since our hinge swivels up and down, as well as left and right, we found our FPC concepts cracked internally with this combination of bending and twisting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*4jBHx_h4eljri0ai." /><figcaption><em>FPC concept. The combination of bending and twisted proved unreliable.</em></figcaption></figure><h4><strong>Finding design solutions — and more challenges</strong></h4><p>Eventually, we concluded that we needed to pass wires through the axle of the hinge to hide them through the full ± 90 degree range of motion.<em> </em>However, routing a concealed wire through the side of the hinge would surely cause the total width of design to grow. To get around this size constraint, we came up with a custom wire bundle that is round going through the hinge, but flat when it exists the hinge axle, saving precious space. This custom multi-section wire bundle gives us the best of both worlds — a slim external hinge profile and hidden wires through the full range of motion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zJXXnt8FrMkEGpNo." /><figcaption><em>The hinge wire bundle has multiple unique cross sections depending on the external size constraints</em></figcaption></figure><p>Wire routing wasn’t our only challenge. The head of the Nest Cam IQ is made of a thick plastic shell, and packs a huge speaker, multiple metal chassis and heat spreaders, and a 4K camera module. In total, the head weighs over 200 grams. All the technology packed into the head created big challenges for the hinge. How could we hold a heavy, densely packed head in place with the friction from such a small hinge mechanism? How could the hinge mechanism be strong enough to survive daily wear and tear?</p><p>Friction hinges usually have a stationary component and a moving component. Large stretches of area on the two components are compressed against each other with high force to create friction when the hinge moves. The holding torque from a friction hinge is generally correlated with the size of the hinge, since larger surfaces can support higher compression forces.</p><p>In the Nest Cam IQ hinge, we only had about a 10x10 mm envelope for our friction mechanism (including space for wires), so we had to think outside the box to get enough holding torque in such a small space. In the end, we created what we call a double-friction mechanism, which allowed us to have an unusually high torque density. First, we use the cosmetic “ball” surface as one friction interface by pushing against it with a plastic friction block and a high force spring. However, inherent in the mechanism design, we have a bonus friction source on the side of the mechanism by keeping the moving metal surfaces compressed together with a screw. This allows us to essentially double the holding torque without increasing the hinge size.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/0*z2wiVu2wLJI1_ZeO." /><figcaption>Double friction mechanism</figcaption></figure><h4><strong>Material strength</strong></h4><p>When it comes to strength of the hinge assembly, the major factors are part geometry, part material choice, and loading path between parts. With such a small hinge and thin individual parts, we knew we could not achieve our design goals through just part geometry, so we focused heavily on materials selection and creating a robust assembly design.</p><p>The internal hinge mechanism components are precision machined out of stainless steel and phosphor bronze. These are very strong materials which can withstand a lot of stress before deforming or cracking. The cosmetic shell around the hinge, which we call the Stem, looks like the plastic head and base enclosures, but is actually an extremely stiff steel tube which provides structural reinforcement to the entire hinge mechanism. It is a great example of how we can achieve the beautiful form conceived by our Industrial Designers without compromising on functional engineering requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*2fhWR4yBcEfuD_whYusA-g.png" /><figcaption><em>Hinge internal parts (left). Hinge with external stem (right)</em></figcaption></figure><p>Speaking of the stem, it is actually one of the most interesting parts in the entire device from a manufacturing perspective. This is a painted steel part that is formed by a process called deep drawing. It is incredible to think this long, slender tube with complex 3D features started out as a flat, circular sheet. Essentially, the metal sheet is stretched little by little over about a dozen stages until it reaches its final shape. Forming metal parts is a common manufacturing process, but seeing a part with this extreme of an aspect ratio is rare for a consumer electronics device, and a great testament to the work of our Manufacturing Operations team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*mVQcGRnCKYPdiBMSYwsicw.png" /><figcaption><em>Stem deep draw stages</em></figcaption></figure><p>Thanks for reading about some of the design and development considerations around the hinge, and stay tuned to this blog for other cool Nest engineering and design posts!</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22efb899ce76" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/hinging-on-design-nest-cam-iqs-hinge-22efb899ce76">Hinging on Design: Nest Cam IQ’s Hinge</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building for the Home. And Designing for the People & Families Who Live There.]]></title>
            <link>https://medium.com/building-for-the-home/building-for-the-home-and-designing-for-the-people-families-who-live-there-a56995d6f4b?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/a56995d6f4b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[nest]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[alphabet-inc]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 03:36:20 GMT</pubDate>
            <atom:updated>2017-06-30T17:04:16.323Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Matt R.</h4><p>Nest set out to tackle difficult problems with simple, effective technology. We started with energy consumption and the thermostat, which controls heating and cooling systems — generally the largest source of energy usage in the home. Today, the Nest Learning Thermostat has been invited into millions of homes and saved billions of kilowatt hours of energy. And while hardware and software engineering were key to reinventing the thermostat, the intuitive, human user experience we created has proven crucial, too.</p><p>Creating thoughtful interactions that resonate with all of Nest’s users requires deep partnership between our Engineering &amp; Design teams. Both teams understand and appreciate the significant technical challenges. Each keeps the users we’re serving at the center of our work. Most of our engineering achievements have a companion design story, and vice versa.</p><p>For example, you’ve <a href="https://nest.tech/seeking-100gb-of-video-how-we-made-sightline-c498af316ca4">read</a> about the technical challenges we faced when building Sightline: making 100 GB of video history load quickly using a thumbnail video stream we call Scrubby Stream. But this technical challenge was the second part of our team’s innovation. It was the result of solving a fundamental, customer-based, design challenge.</p><p>When the Sightline team began development, the first design challenge we faced was daunting. How could we build an experience contained within a mobile device that allowed homeowners to intuitively traverse 10-to-30 days of 24/7 video coverage? That’s up to 720 hours of footage. And beyond that, how do we call attention to the events that are <em>actually interesting</em> amidst hours of footage?</p><p>Our teams kicked around a lot of ideas — from calendars to lists of events — before we finally landed on the core of Sightline: A vertical representation of events, allowing users to easily scrub through their enormous video history. You can move your finger slowly along the events, and the video advances slowly to mirror your interaction, tracking your place in time. Scroll quickly, and you can get through your video in no time at all.</p><p>When Nest Cam notices something it thinks you’d like to know about, the thumbnail of the event appears in the corresponding place on your timeline. This design allows users to digest a lot of information without breaking a sweat.</p><p>When I first saw the design team’s proposal, I was incredibly impressed. It was so natural that I couldn’t imagine a simpler way to interact with that quantity of data. The team went on to share the proposal with the product engineers, who were inspired to come up with amazingly innovative Scrubby Stream, enabling us to process massive amounts and bringing the design idea to life.</p><p>This level of collaboration around shared challenges between design and engineering is indicative of what makes Nest — and the experiences we build for users — so special.</p><p>That’s just one of the innovative experiences that our incredible designers have built. Ever wonder how Nest designed the voice of Protect, our smoke and CO detector, before voice interactions were popular? Or how we chose which thermostat interface features to develop for our iconic Learning Thermostat? How has Nest built and maintained the iconic aesthetic of our product line? I’m excited for our team to share posts from Nest’s designers here on “Building for the Home.” These folks are working hard to shape our technological advancements into approachable and delightful interactions. We’ve accumulated plenty of stories and insights over the last seven years. We’re excited to share that work with you. I hope you’ll continue to stop by to read more about them.</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a56995d6f4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/building-for-the-home-and-designing-for-the-people-families-who-live-there-a56995d6f4b">Building for the Home. And Designing for the People &amp; Families Who Live There.</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing Machine Learning to the Connected Home]]></title>
            <link>https://medium.com/building-for-the-home/bringing-machine-learning-to-the-connected-home-73c3251a4780?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/73c3251a4780</guid>
            <category><![CDATA[tensorflow]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[googleio]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[smart-home]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Thu, 18 May 2017 20:49:35 GMT</pubDate>
            <atom:updated>2017-06-30T01:08:58.486Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Aren</h4><h3>A TensorFlow &amp; Nest Cam Codelab</h3><p>Machine Learning and Artificial Intelligence are exciting topics with developers, but few of us have actually gotten our hands dirty and built something with these technologies. This week at <a href="https://events.google.com/io/">Google I/O</a>, we wanted to offer developers an inside look at how to build something useful with Google’s Machine Learning library, TensorFlow.</p><p>So we’re deploying a <a href="https://codelabs.developers.google.com/codelabs/nest-camera-api">Nest Cam &amp; TensorFlow Codelab</a>. Read on for additional resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/0*cofjp0MenVfXcPSx." /></figure><p>Google released <a href="https://www.tensorflow.org/">TensorFlow</a> in 2015. Since then, it has seen industry-wide usage in a variety of applications, including Optical Character Recognition (OCR), recommendation engines (Google search results, Facebook news feed), and image recognition. The library has drastically reduced the complexity involved in setting up and training neural networks, which has turned incredibly complex tasks into everyday activities.</p><p>So, how does it work? When working with neural networks, you repeatedly train the network with known inputs and expected outputs. The output is effectively the network “learning.” The more the network learns, the stronger the output. To save developers from having to train all inputs themselves, TensorFlow provides a series of open-sourced, pre-trained resource models. This eliminates the tedious step of training the neural network; instead, we use one of the provided models called <a href="https://github.com/tensorflow/models/tree/master/inception">Inception-v3</a>.</p><p>Inception-v3 was trained to classify images as part of the Large Visual Recognition Challenge from 2012. The challenge was to classify images into 1000 discrete classes at a large scale, and focus on image indexing and labeling, including things like “golf ball,” “tennis ball,” “broccoli,” etc.</p><p>In the Nest TensorFlow codelab, developers build a small Python web application. The app is designed to fetch imagery from a remote Nest Cam. The JPEG image is fetched via the Works with Nest REST API (<a href="https://codelabs.developers.google.com/codelabs/wwn-api-quickstart/#0">learn about our API</a>). In front of the Nest Cams field of view, we have placed objects that the Inception model is trained to recognize.</p><p>So, for instance, given the following image in front of the Nest Cam, the codelab application is able to say with near certainty that this image is a teddy bear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yDB4GNDEB6DalowL." /></figure><p>It is important to note here that the Inception model has been trained with imagery <a href="http://image-net.org/synset?wnid=n07753592"><strong>drastically different</strong></a><strong> </strong>than what Nest Cams see in the codelab–that’s what makes this truly incredible. The neural network is able to recognize the image contents in a fashion similar to a human brain.</p><p>There are all sorts of cool things that could be built with Machine Learning and Works with Nest. The Nest API offers access to a rich data set for our thermostats, cameras, and smoke + CO alarms.</p><p>Machine Learning is an area of rapid development with game-changing impact in software development — including in the connected home. Our hope is that this codelab serves as an interesting intro to TensorFlow and Works with Nest, and as a starting point for your curiosity.</p><p>If you’re in Mountain View, California this week for Google I/O, visit us at the Codelab space. <a href="https://codelabs.developers.google.com/codelabs/nest-camera-api/#0">Or find it here</a>.</p><p>I can’t wait to see what you will build.</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73c3251a4780" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/bringing-machine-learning-to-the-connected-home-73c3251a4780">Bringing Machine Learning to the Connected Home</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Open Foundation for the Connected Home]]></title>
            <link>https://medium.com/building-for-the-home/an-open-foundation-for-the-connected-home-1070a8e41e34?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/1070a8e41e34</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[googleio]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[smart-home]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Thu, 18 May 2017 20:48:40 GMT</pubDate>
            <atom:updated>2017-12-19T20:16:55.102Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Jonathan</h4><h3>The Origin of Thread</h3><p>The moment Nest expanded our product line beyond the Nest Learning Thermostat, we were in new territory. Multiple smart home devices not only needed to talk to users, but also to each other in a reliable and secure manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*72P2pIgvs0jKI4hvGxRLnA.png" /></figure><p>Imagine a home with multiple Nest Protects — one upstairs, one downstairs. It’s night. Everyone’s asleep. The downstairs Protect detects smoke, but no one hears the alarm — perhaps it’s too far away, or doors are closed. However, if all Protects are connected together, they can talk to each other. The upstairs Protect can also sound an alarm, successfully alerting everyone upstairs.</p><p>Why not just use Wi-Fi to do this? Nest Protects are low-power devices — some operate only on batteries. Using Wi-Fi to send messages, to and from the cloud or even locally, requires power that makes it less suitable for battery-operated devices. Why not Bluetooth? Bluetooth is a point-to-point communication protocol, which makes it less suitable for efficiently communicating messages across a network of devices, and lacks IPv6, which limits its longevity.</p><p>To facilitate reliable communication between Nest Protects, we built a networking protocol that requires less power and overcomes the limitations of point-to-point and hub-and-spoke communications. And to enable robust, remote connectivity in a rapidly growing IoT ecosystem, we built in IPv6 from the ground up, while simultaneously baking-in strong link-layer security. With these requirements in mind, and in collaboration with a number of like-minded revolutionary partners, <a href="http://threadgroup.org/technology/ourtechnology">Thread</a> was born.</p><h3>Going Open Source</h3><p>We could have limited our Thread contributions to specification development within the Thread Group. However, after seeing the value proposition of Thread, we wanted the benefits of Thread technology to be more broadly adopted — to accelerate the development of products for the connected home and beyond. It was clear that we needed to make Thread technology widely available to our partners and the IoT community.</p><p>So, in 2016, Nest released an open-source version of Thread, called <a href="https://openthread.io/">OpenThread</a>. It is the first open-source <a href="http://threadgroup.org/technology/ourtechnology#certifiedproducts">Thread Certified Component</a>, implementing all features defined in the <a href="http://threadgroup.org/technology/ourtechnology#specifications">Thread 1.1.1 specification</a>.</p><p>OpenThread is OS and platform agnostic, with a narrow platform abstraction layer and a small memory footprint, making it highly portable to a wide spectrum of hardware system architectures. Due to this flexible design, OpenThread has been ported to multiple hardware platforms, such as Dialog’s <a href="https://openthread.io/platforms/da15000">DA15000</a>, Nordic’s <a href="https://openthread.io/platforms/nrf52840">nRF52840</a>, NXP’s KWx1Z, Silicon Labs’ <a href="https://openthread.io/platforms/efr32">EFR32</a>, Texas Instruments’ <a href="https://openthread.io/platforms/cc2538">CC2538</a> and <a href="https://openthread.io/platforms/cc2560">CC2650</a>, and Microsoft’s <a href="https://openthread.io/platforms/windows10">Windows</a> 10, by both the OpenThread team and the community.</p><h3>The Benefits of Open Source</h3><p>Source access makes it easy for both silicon vendors and the developer community to port OpenThread to new hardware platforms, resulting in more silicon choices. It also results in a single code base that can be used across multiple hardware and product designs (more on that later). This enables developers to support each other more efficiently.</p><p>Open source creates transparency when it comes to testing and security audits — something you may not get with a proprietary product. Not only are our <a href="https://openthread.io/testing/">testing tools</a> and security features public, the community can add new tests, easily notify us of issues and contribute to the hardening of OpenThread.</p><p>From a business perspective, using open-source firmware reduces business constraints. It allows silicon vendors to easily incorporate and extend OpenThread for their customers. Developers can easily include OpenThread in their products, thus allowing them to easily create value-added products and services.</p><p>We’ve released OpenThread under a permissive open-source BSD-3 copyright license. This license makes it painless for users to debug issues and provide feedback and enhancements to the project.</p><h3>How does it work?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*YRp1Xp8mglGSUb2vFCyH0Q.png" /></figure><p>OpenThread is designed with portability and flexibility in mind. The code is portable C/C++ (C99 and C++03) that’s system architecture-agnostic due to a narrow abstraction layer. This abstraction layer means that OpenThread can run on either bare-metal or an OS. To date, OpenThread has been demonstrated to run on FreeRTOS, RIOT-OS, Linux, macOS and Windows.</p><p>OpenThread’s portable nature makes no assumptions about platform features. OpenThread provides the hooks to utilize enhanced radio and crypto features, reducing system requirements, such as memory, code, and compute cycles. This can be done per platform, while retaining the ability to default to a standard configuration.</p><p>The portable design is also why it’s so flexible. OpenThread has a configurable build system with which a developer can enable or disable features as needed. Beyond the default GNU toolchain, the source is designed to work with a number of other popular toolchains like IAR and Visual Studio.</p><h3>Platform designs</h3><p>OpenThread supports both system-on-chip (SoC) and network co-processor (NCP) designs.</p><p>An SoC is a single-chip solution that has the combined RFIC (802.15.4 in the case of Thread) and processor, where OpenThread and the application layer run on the local processor.</p><p>An NCP design is where the application layer runs on a host processor and communicates with OpenThread via a serial connection using a standardized host-controller protocol we call <a href="https://openthread.io/guides/ncp/#spinel_protocol">Spinel</a>. In this design, OpenThread can run on either the radio or host processor.</p><p>Let’s dive into the different flavors of these designs.</p><h4><strong>Single-Chip, Thread-Only (SoC)</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*9W7_lWmvGEnLNPUsCgsxVA.png" /></figure><p>In this design, the application layer and OpenThread run on the same processor. The application directly uses the OpenThread APIs and IPv6 stack.</p><p>This is the typical SoC design most commonly used for end devices. Because it is highly-integrated into a single silicon, it has the lowest cost and lowest power consumption.</p><h4>Single-Chip, Multiple-Interface (SoC)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*eHiY2NAj0IyTSU93NPuvSg.png" /></figure><p>Even when a SoC has multiple radios, such as 802.15.4 and Wi-Fi, or 802.15.4 and Bluetooth Low Energy (BLE), the application layer and OpenThread still run on the same processor. In the multiple-interface design, OpenThread leverages the shared third-party IPv6 stack via a raw IPv6 datagram interface.</p><h4>Network Co-Processor (NCP)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*hu5mlmn3G1A6F3S9TpAZTw.png" /></figure><p>The standard NCP design has Thread features on the SoC and runs the application layer on a host processor, which is typically more capable (but has greater power demands) than the OpenThread device. The host processor communicates with the OpenThread device via a serial interface (typically SPI or UART) over the Spinel protocol.</p><p>The benefit of this design is that the higher-power host can sleep while the lower-power OpenThread device remains active to maintain its place in the Thread network. And since the SoC is not tied to the application layer, development and testing of applications is independent of the OpenThread build.</p><p>This design is useful for gateway devices or devices that have other processing demands like IP cameras and speakers.</p><h4>Host / 802.15.4 Controller</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*ZwFtFaLKHqn4FMarWGzkmw.png" /></figure><p>There is a variant of the NCP design where the core of OpenThread lives on the host processor with only a minimal “controller” on the device with the Thread radio. The host processor typically doesn’t sleep in this design, in part to ensure reliability in the Thread network.</p><p>The advantage here is that OpenThread can utilize the resources on the more powerful processor.</p><p>This design is useful for devices that are less sensitive to power constraints. For example, the host processor on a video camera is always on to process video.</p><h4>Other features</h4><p>With OpenThread, you get more than just the Thread 1.1.1 Specification. We’ve added a number of features and enhancements ranging from APIs to additional protocols that facilitate host/NCP communications.</p><p>For example, our <a href="https://openthread.io/reference/">complete APIs</a> allow you to integrate OpenThread with a third-party IPv6 stack, build application layers that rely on UDP messages, or resolve DNS names to IPv6 address. With CoAP client and server support, you can share the same CoAP implementation between OpenThread and CoAP-based applications.</p><p>We’ve added a <a href="https://github.com/openthread/openthread/tree/master/src/cli">Command Line Interface</a> (CLI) for easier configuration and network management. The CLI can also be used by automated test scripts.</p><p>We’ve also included the <a href="https://github.com/openthread/openthread/blob/master/doc/draft-rquattle-spinel-unified.txt">Spinel protocol</a> for NCP designs, which enables communication between the host device and the NCP. <a href="https://github.com/openthread/openthread/blob/master/tools/spinel-cli/SNIFFER.md">Sniffer</a> support is exposed by Spinel, and the <a href="https://github.com/openthread/wpantund">wpantund</a> daemon provides an IPv6 interface to the NCP.</p><h3>Interested in OpenThread?</h3><p>There are multiple ways to learn more and get involved:</p><ul><li>Check out this <a href="http://threadgroup.org/Portals/0/documents/resources/presentations.zip">workshop from March</a></li><li>Run through our <a href="https://codelabs.developers.google.com/codelabs/openthread-simulation/index.html">Simulation Codelab</a>, which covers all the basics of OpenThread, without the need for test hardware — all you need is a Mac or Linux machine</li><li>Get a devkit — explore the <a href="https://openthread.io/platforms/">platforms OpenThread already supports</a></li></ul><p>You can also catch us in the IoT Sandbox at <a href="https://events.google.com/io/">Google I/O</a> this week in Mountain View, California.</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1070a8e41e34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/an-open-foundation-for-the-connected-home-1070a8e41e34">An Open Foundation for the Connected Home</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Dataflow In the Smart Home Data Pipeline]]></title>
            <link>https://medium.com/building-for-the-home/google-cloud-dataflow-in-the-smart-home-data-pipeline-5ae71781b856?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/5ae71781b856</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[smart-home-automation]]></category>
            <category><![CDATA[alphabet-inc]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 21:50:42 GMT</pubDate>
            <atom:updated>2017-06-05T20:40:56.182Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Matt &amp; Riju</h4><p>Building the Thoughtful Home means reinventing products that are important to safety, security and comfort. Traditionally, devices ranging from thermostats, smoke detectors and security cameras to lights, locks and appliances have been self-contained, operationally independent units in the home. But Nest’s cloud service platform opens up a wide range of possibilities for how these devices can interact and coordinate when they are operating in a connected mode.</p><p>One of the challenges in scaling a platform is developing a reliable data service architecture to support high-volume, real-time and batch logging from devices. In this post, we’ll discuss ideas for leveraging Google <a href="https://cloud.google.com/dataflow/">Cloud Dataflow</a> at a performance level required for such data intensive applications, including terabyte-level daily data ingestion and processing, and petabyte-level storage.</p><h3><strong>Device Logging Behavior</strong></h3><p>Nest products log different types of data to the service, ranging from state events (e.g. heater turned on, alarm went off) to time series data (e.g. room temperature, CO readings) to system data that describes how a device is functioning.</p><p>This information can be used in a variety of tools and formats to present data to users, including within direct reports like our monthly <a href="https://nest.com/support/article/About-the-Nest-Home-Report">Nest Home Report</a>, to measuring energy and money savings such as in our <a href="https://nest.com/support/article/What-is-Rush-Hour-Rewards">Rush Hour Rewards</a> and <a href="https://nest.com/support/article/What-is-Seasonal-Savings">Seasonal Savings</a> programs, to supporting <a href="https://nest.com/downloads/press/documents/co-white-paper.pdf">important field studies</a>, and generally for the continued development of products. In a more real-time example, devices emit sensor events that are inputs into service-based features such as <a href="https://nest.com/support/article/Learn-more-about-Home-Away-Assist">Home/Away Assist</a>. This feature is used to adjust device settings based on an estimate of whether or not users are at home, allowing, for example, Nest Protect to run a monthly sound check to test its audio alert systems only when the home is unoccupied.</p><p>One of the perennial problems smart home developers face is that devices in the home are subject to a wide range of conditions in their environments. As a result, the quality and reliability of the data can be unpredictable. For example, factors such as poor WiFi/network connectivity, power loss and battery drain can impact a device’s logging stream. To further complicate things, the devices themselves are subject to stringent battery budgets, which limits available processing power and time spent connected to the network.</p><p>The solution to this universal challenge: a robust data architecture and corrective processing downstream to account for data loss, late-arriving data, data duplication, invalid data and even corruption.</p><h3><strong>Overviewing The Data Pipeline</strong></h3><p>The following diagram depicts — at a high-level — the main components of a data architecture suitable for applications like Nest’s.</p><p>In this system, devices present their logs and real-time events to the service through logging endpoints which provide authentication, basic data validation, and delivery for downstream processing.</p><p>The data pipeline begins with stream processing components that convert events in various formats to Apache Avro. These Avro data are streamed to Apache Kafka topics, with a separate topic for each Avro schema. For instance, one topic may contain temperature data from thermostats. A system with millions of devices could result in several hundreds of topics, with the total event arrival rates into the millions per second.</p><p>Some of these data persist in HDFS using a system comprising Apache Storm and Hadoop. Although ideally one might want to persist all of these data in HDFS, the cost and scale of the system required to achieve this, from an infrastructure and operational perspective, becomes unsustainable as systems scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnHhqTZihXVmFuzJSMm31Q.png" /></figure><p>Also, the tools available to the users of this data need to evolve with the needs of users. If ad-hoc access to this data is required, Apache Hive is a common approach. Regularly scheduled jobs use a combination of Cascading, Scalding and Apache Spark. Managing resources to service all the users with a reasonable latency on a non-elastic cluster is challenging.</p><p>One last area we identified to advance the original pipeline: data backfill. Although rare, it’s not unheard of to run into cases where we need to reload past data. Since the existing pipeline is primarily based on a streaming architecture, supporting backfill requires building and maintaining a separate set of systems that can run in batch mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHvW74PM8jDOjaIGbg8gXQ.png" /></figure><h3><strong>Introducing Cloud Dataflow into an Architecture</strong></h3><p>If you want to evolve a data architecture like the one above, without disrupting the existing pipelines or duplicating the entire pipeline, you might introduce Cloud Dataflow and Google BigQuery into the architecture.</p><p>Using Cloud Dataflow, the Avro events can be read from Kafka, thereby creating a parallel pipeline to the HDFS ingest pipeline. These events are converted to BigQuery format and streamed into daily BigQuery tables. The snapshot below shows an example of a Cloud Dataflow streaming pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*us3gUa_5N8VQzdrjDveg4A.png" /></figure><p>If you look closely, you can see that this Cloud Dataflow job consists of several parallel “pipelines” (DAGs) with no interdependencies. All but two (we’ll talk about these TickIO pipelines later) of those DAGs do similar transformations, with the exception that they are processing different event types. The first block in these DAGs show the Kafka source that reads from several Kafka topics matching the same event type. The next two blocks do various transformations to map these events to a BigQuery schema for that event type. The last block is the BigQuery sink, which writes these events to daily tables. The target daily tables are determined based on the time the event actually occurred. Note that the event time may be very different from wall clock time because of inherent and unpredictable latencies in the event streams of IoT devices. For instance, devices with poor connectivity or power constraints may buffer events in local memory until they reestablish a connection for upload.</p><p>The same pipeline (leveraging shared code with a few modifications) is also run in batch mode for backfilling. The main difference between these pipelines is the data source. In batch mode, the data sources are Avro files stored in Google Cloud Storage or HDFS. There are also some minor differences in how these are parsed and transformed. In batch mode, the BigQuery sink internally uses BigQuery load jobs. BigQuery load jobs are free and can do atomic updates. However, the bottom line is that both streaming and batch jobs are launched from the same Java class (with different arguments). Typically, one might run the batch jobs per event type for a date range. See below for the snapshot of one such job. Each DAG in this job loads data into a single daily BigQuery table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_G0SeV4iBxEvMJdotJnLJA.png" /></figure><p>Earlier, we referred to TickIO DAGs in the context of streaming pipelines. TickIO is a <a href="https://cloud.google.com/dataflow/model/custom-io-java">custom source</a> that handles periodic tasks. In the streaming pipeline, there are two TickIO sources — TickIO-5Min and TickIO-Daily. As the names imply, the former performs periodic tasks every five minutes and the latter performs tasks every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SeleWE_sedrGnNTu5buyUA.png" /></figure><p>Some pipelines deal with large enough volumes of streaming data that they could exceed per table streaming quota limits in BigQuery. For such event types, one can stream data into multiple daily tables per event type. To hide this from consumers of these data, we provide daily views over these split tables. As a result, consumers can have a consistent interface across widely varying event volumes and types. The CreateBigQueryView transform run as part of the TickIO-Daily DAG is responsible for the creation of these daily views.</p><h3><strong>Monitoring the Cloud Dataflow Pipeline</strong></h3><p>Our Kafka source periodically checkpoints the current consumed offset to a Bigtable table. The TrackKafkaSourceOffsets transform in the TickIO-5Min DAG makes use of this information to compute the Kafka consumer lag for each partition and emits those metrics to Stackdriver. We have set up Stackdriver alerts to alert us whenever these lags exceed certain thresholds.</p><p>For example, the following Stackdriver chart shows one such metric which is configured to alert when the Kafka consumer lag exceeds 5%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*ZsLxTyXrrhr3B-rYsE_pbA.png" /></figure><p>Following is an example of another metric which is set to alert when the read rate from a Kafka topic drops below a certain threshold [Note that the alert policies are set elsewhere in the Stackdriver console. These charts are just visual representations].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*hV_fkoq2HBoRZBRl7zZ0oQ.png" /></figure><p>In addition to the above Stackdriver metrics, we also make use of Cloud Dataflow custom counters to keep track of event level metrics (event counts, error metrics etc.). We have a monitoring system which pulls these data periodically from the Cloud Dataflow job and publishes them to Stackdriver.</p><h3>Conclusion</h3><p>By integrating Cloud Dataflow into the data ingest pipeline, a system owner can create flexibility and scale capacity to handle the wide variety of logging conditions and challenges presented by a large-scale fleet of data-logging devices. This also creates a foundational data architecture for leveraging other Google Cloud Services such as Cloud Pub/Sub and Cloud Bigtable.</p><p>For large-scale IOT architectures, Cloud Dataflow may be primarily useful for streamlining ingestion, but the easy integration between Cloud Dataflow and Google BigQuery also opens up other uses as well. For example, Cloud Dataflow can be used for data set curation, fleet health monitoring, algorithm performance verification and customer report generation.</p><p>We have discussed the basics of data movement and the use of Cloud Dataflow. In reality when dealing with private or sensitive data, security considerations need to be layered on top of any data infrastructure to ensure appropriate measures are in place.</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ae71781b856" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/google-cloud-dataflow-in-the-smart-home-data-pipeline-5ae71781b856">Google Cloud Dataflow In the Smart Home Data Pipeline</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seeking 100GB of Video: How We Made Sightline]]></title>
            <link>https://medium.com/building-for-the-home/seeking-100gb-of-video-how-we-made-sightline-c498af316ca4?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/c498af316ca4</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[alphabet-inc]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 19:26:04 GMT</pubDate>
            <atom:updated>2017-06-30T01:06:45.981Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Kevin</h4><p>Nest Cam can record up to 30 days of video (with Nest Aware subscription), which is great for capturing everything that happened, but with all that content, it can be difficult for our brains to figure out which moments are worth our attention. The volume simply isn’t digestible.</p><p>To solve this problem, in September 2016, Nest launched Sightline, a new interface to Nest Cam on iOS and Android. Sightline introduced several new features, but the biggest breakthrough was the ability to quickly rewind and fast forward through all recorded video simply by scrolling on the vertical timeline.</p><p>When the design team first demoed the concept, everyone got really excited. It felt like your thumb was connected to the video as you smoothly moved through time — as opposed to the previous experience of guessing where you move a slider and then waiting several seconds for buffering before seeing if you were close to what you wanted to find.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/0*XNRtt372nkcR10x5." /><figcaption>Early drawing</figcaption></figure><p>But was it even technically possible? How can you smoothly scroll through up to 30 days of video history stored in the cloud, which can be over 100GB of data, from a phone?</p><p>It was clear that we would need to subsample the video, but would that be enough? Even if we could make it 1000 times smaller, it could still be on the order of hundreds of megabytes. Just getting that much data to a phone is problematic. After all, phones have limited disk space, flaky internet connections, and capped cellular data plans.</p><p>We formed a small engineering team to explore the problem, and we prototyped the kernel of a solution: extract thumbnail frames from the HD video stream and transcode them into condensed video chunks that can be downloaded in batch and aggressively cached. From there, we could tune the various parameters controlling the stream to achieve the performance characteristics necessary. We call this condensed thumbnail video stream the Scrubby Stream.</p><p>Our services process a lot of new video everyday –- even more than YouTube does. That makes transcoding and serving the video difficult to do in a low-latency and cost-effective way. But that’s another article. For now, we’ll focus on the tradeoffs we made in order to dial in the Scrubby Stream to get the Sightline experience just right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*3CmpqfjTmTMKKRB4." /><figcaption>Paper prototypes from design sprint</figcaption></figure><h3><strong>Frame density vs scroll distance</strong></h3><p>There are two parameters that primarily control the user experience. One is the frame density, which is the number of frames displayed during a period of time. The other is the scroll distance, which is the physical distance the user must scroll on the phone to move through a period of time.</p><p>The frame density and scroll distance complement each other. If scrolling one pixel seeks by one second, then having more than one frame per second would be wasteful.</p><p>Frame density and scroll distance also have a widespread impact on the overall system design and UI. The frame density affects the design of the transcoding service, including the impact it will have on other services. The scroll distance controls how much real estate is on the screen for other UI elements, and how quickly we expect the device to be consuming video from the service.</p><p>Through prototyping and testing, we settled on a frame density of approximately one frame per minute and a scroll distance of 3pt per minute. This gives a nice balance between showing enough detail about what happened throughout a day of video, while also making it easy to scroll back several days quickly.</p><p>With these essentially fixed in place, we began thinking about how best to encode the Scrubby Stream.</p><h3><strong>Seek speed vs file size</strong></h3><p>A key aspect to the Sightline experience is being able to seek through the Scrubby video stream with very low latency. This meant that all the Scrubby data would have to be cached locally on the device, but there was still more work to do to get great seek performance on the wide range of devices we support. To do that, we had to look at how H.264 is decoded.</p><p>One way that H.264 achieves high compression is by grouping consecutive frames into a Group of Pictures (GOP.) The first frame in the GOP contains the entire image, and the rest just contain delta information, making them much smaller. To decode a particular frame, you must generally decode all prior frames in the GOP.</p><p>Therefore, we can improve the seek performance by shortening the GOP length, since it decreases the decode time. However, the shorter the GOP, the more GOPs are required to cover the same number of video frames. And since each GOP has one frame that contains the entire image, the overall file size goes up.</p><p>After a lot of testing on an array of devices, we found that 20-frame GOPs made the Sightline scroll experience very responsive. Luckily, by carefully tuning other encoder parameters, we were also able to rein in the file size.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*V3K74CMfuvfpUWCpK-CXRw.gif" /><figcaption>Early prototype</figcaption></figure><h3><strong>Quality vs file size</strong></h3><p>The overall file size of the Scrubby Stream is extremely important. It impacts the download speed, the disk space consumed by the cache, and the network usage. Both the frame density and the GOP size affect the file size, but so does the quality.</p><p>With the x264 encoder, the two primary controls over the quality are the resolution and the Constant Rate Factor (CRF). Since the Scrubby Stream is just used for thumbnails for the HD stream, we can carefully dial down the quality to dramatically reduce the file size. This makes the download speed very fast, even on slow networks, and reduces the amount of disk space consumed by the app.</p><p>The average size for a full day of Scrubby data is just 5 MB. And to be extra considerate to users on capped mobile data plans, who may even have multiple cameras or occasionally need to download multiple days worth of Scrubby data, we encode an additional lower-quality stream that averages a mere 1 MB per day.</p><p>We also take special care to avoid ever unnecessarily re-downloading Scrubby data. Each individual GOP in the Scrubby Stream is cached to disk, so even if the connection dies partway through the download, the app never needs to download the same data twice. One exception, however, is that any lower-quality Scrubby data downloaded while on a cellular connection will automatically be replaced with high-quality data next time the user is on WiFi.</p><h3><strong>Frame density vs motion events</strong></h3><p>Some readers may note that a frame density of one per minute may not be enough to capture short motion events. Indeed, if there is motion in the scene that only lasts for say, 10 seconds, naively sampling one frame every 60 seconds will usually miss it.</p><p>Luckily, for subscribers to Nest Aware, we already perform computer vision analysis on all recorded video to help users identify the most interesting events, like when there is motion or a person in the scene. This is the basis for our intelligent alerts.</p><p>Now we also use this information to pick out the best frames to include in the Scrubby Stream. So while the frame density averages one per minute, it actually varies slightly because every frame is chosen by considering all of the interesting activity that occurred over the time period. This way we can capture even the short lived events with a thumbnail in the Scrubby Stream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*PUQyWgksc0xMg6CEgB5KpQ.gif" /><figcaption>Sightline 1.0</figcaption></figure><h3><strong>Wrapping up</strong></h3><p>With Sightline, we managed to bring an idea to life that we didn’t think would be possible at first. It took a lot of talented individuals from several teams working together to launch this to all our users on both mobile platforms. It’s now fun and easy to flick through the video captured with Nest Cam and see all the interesting activity that happened during the last 10 or 30 days of cloud recording, and we’re very happy with the early feedback we’ve received. And while Sightline is a great new experience, it’s really just the start of many new features we have planned for Nest Cam.</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c498af316ca4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/seeking-100gb-of-video-how-we-made-sightline-c498af316ca4">Seeking 100GB of Video: How We Made Sightline</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to Building for the Home!]]></title>
            <link>https://medium.com/building-for-the-home/welcome-to-building-for-the-home-e7c2450c2925?source=rss----c1ee1ae3c1c6---4</link>
            <guid isPermaLink="false">https://medium.com/p/e7c2450c2925</guid>
            <category><![CDATA[nest]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[alphabet-inc]]></category>
            <dc:creator><![CDATA[Nest engineering & design]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 19:25:27 GMT</pubDate>
            <atom:updated>2017-06-30T01:09:58.039Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Nik</h4><p>Welcome. We’re engineers at <a href="http://www.nest.com/">Nest</a>, focused on creating a home that takes care of the people inside and the world around it. We call it the Thoughtful Home. Thanks for being here!</p><p>We’re excited to kick off this dialog. To give you a peek behind the scenes at Nest. Share our stories. Our lessons learned. And to give details on the technologies that make things tick.</p><p>I’m Nik and I head up this amazing group of engineers. At Nest, we are passionate about the idea of reinventing products in the home that could be so much better, smarter and more helpful with the right technology and a great user experience. If you stopped by my house, you’d see several different connected ‘things’ in every single room. Unfortunately, while each device does a nice job, not everything works well together yet — so my family is on this journey with me!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*QWLoO7kfR0JNEHql0VrFiw.jpeg" /></figure><p>Our team members come from a variety of backgrounds and most have been building consumer products for a long time. But building for the home is a lot harder than it looks. Because our products are part of the infrastructure of the house, the expectations are higher: low latency, high reliability, easy to set up and use, tight security, and a really long lifetime.</p><p>Making a product that meets those requirements — and still looks great in your home — compounds the challenges. For example, the Nest Thermostat’s ambient temperature sensor sits next to a heat-producing chip while encased in steel and glass. Or, the Nest Protect’s passive infrared motion sensor needs to live inside the big button, which then becomes both a button and a PIR lens.</p><p>Our incredible engineers solve these and other interesting problems every day. And in spite of the challenges, we have had a lot of success at building products that are easy to use, beautiful and impactful on the comfort, safety, security, and energy savings of people’s homes.</p><p>Products are only half the story. We’re not going to make every device in the house but we do want to enable many different kinds of products to take part in our vision of a thoughtful home. We’re building a platform to extend the technology that underpins Nest products to developers. We’ve tested and approved hundreds of product integrations and worked with thousands of developers, from startups to large companies, who are part of our Works with Nest community. We’re uniquely positioned to share what we have learned about designing and building products that you choose to bring into your home.</p><p>For our <a href="https://nest.tech/seeking-100gb-of-video-how-we-made-sightline-c498af316ca4">first post</a> here on Medium, we’re sharing details about Sightline, a new feature of Nest Cam. We’ll have many more things to share over the coming months. We’re looking forward to your participation and feedback. Come join us at Nest’s <a href="http://nestdevelopers.io/">Developer community</a> to get involved in the conversation. Thanks for reading.</p><p><em>Join the conversation at Nest’s </em><a href="http://nestdevelopers.io/"><em>Developer community</em></a><em>. Get started with </em><a href="https://developers.nest.com/"><em>Nest Developers</em></a><em>. Or explore </em><a href="http://nest.com/careers"><em>careers with Nest</em></a><em>.</em></p><p><em>The information contained in this blog is provided only as general information for educational purposes, and may or may not be up to date. The information is provided as-is with no warranties. This blog is not intended to be a factual representation of how Nest’s products and services actually work. No license is granted under any intellectual property rights of Nest, Google, or others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7c2450c2925" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-for-the-home/welcome-to-building-for-the-home-e7c2450c2925">Welcome to Building for the Home!</a> was originally published in <a href="https://medium.com/building-for-the-home">Building for the Home</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>