Recently at Google I/O, we gave you asneak peek at our new Local Home SDK, a suite of local technologies to enhance your smart home integrations. Today, the SDK is live as a developer preview. We've been working hard testing the platform with our partners, including GE, LIFX, Philips Hue, TP-Link, and Wemo, and are excited to bring you these additional technologies for connecting smart devices to the Google Assistant.
Figure 1: The local execution path
The SDK introduces two new intents ,
REACHABLE_DEVICES . The local home platform scans the user's home network via mDNS, UDP, or UPnP to discover any smart devices connected to the Assistant, and triggers
IDENTIFY to verify that the device IDs match those returned from the familiar Smart Home API
SYNC intent. If the detected device is a hub or bridge,
REACHABLE_DEVICES is triggered and treats the hub as the proxy device for communicating locally. Once the local execution path from Google Home to a device is established, the device properties are updated in Home Graph .
Figure 2: The intents used for each execution path
When a user triggers a smart home Action that has a local execution path, the Assistant sends the
Additional features of the Local Home platform include:
Figure 3: Local Home configuration tool in the Actions console
To learn more about the Local Home platform, check out the API reference , and get started adding local execution with the developer guide and samples . For general information covering how you can connect smart devices to the Google Assistant, visit the Smart Home documentation , or check out the Local Technologies for the Smart Home talk from Google I/O this year.
You can send us any feedback you have through the bug tracker , or engage with the community at /r/GoogleAssistantDev . You can tag your posts with the flair local-home-sdk to help organize discussion.