Local Technologies for the Smart Home
summary
Local Home SDK runs provider JavaScript on Google Home/Nest devices so commands go over LAN instead of round‑trip cloud, cutting post‑server latency to <300 ms and pushing success rates above 99.9%. It matches cloud SYNC otherDeviceIds to local discovery (mDNS/UDP/UPnP), uses IDENTIFY/REACHABLE_DEVICES/EXECUTE intents, and communicates via TCP/UDP/HTTP sockets. Developers build a TypeScript app, debug with chrome://inspect, and can enable seamless BLE setup flows that install C by GE bulbs in ~30 seconds.
AI-written summary · about
chapters (12)
- 0:00Introduction to local home
- 2:51Smart home API overview
- 5:49Local home SDK benefits
- 9:56Technical architecture
- 12:27Device discovery flow
- 16:16Implementing the SDK app
- 20:30Local identification process
- 24:36Executing commands locally
- 28:15Debugging and testing
- 30:40Certification and launch
- 32:32Seamless device setup
- 37:11Future and conclusion
related talks
18mBuilding, testing, and deploying smart home devices for Google Home
26mThe complexity of integrating more than 150 devices
30mOffline IoT - Building Resilient Connected Devices without the Internet
25mBuilding great experiences with Smart Home | Developer Keynote
35mAgainst all odds, a cloudless smart home
25mStreamlining IoT Systems: SmartThings Cloud-to-Cloud Device Integrations
51mSmart home from scratch - a little C#, a little C++ and cheap Chinese electronics
18mEnriching Your Smart Home Experience With Voice Assistants