iOS开发者指南：掌握Apple HomeKit智能家居

需积分: 9 83 浏览量更新于2024-07-20 收藏 6.52MB PDF 举报

《在iOS上学习Apple HomeKit》是一本详尽的指南，专为理解并利用Apple的智能家居技术——HomeKit而设计。该书全面介绍了HomeKit平台架构，以及它如何支持现有和未来的设备，同时深入探讨了新应用如何在安全和创新的环境中实现新一代的家庭自动化。作者Jesse Feiler以其在移动和位置应用方面的专业知识，为读者提供了从设备开发者、DIY家庭网络用户到程序员、对iOS设备与物联网设备整合感兴趣的各类人士提供了全面的学习资源。书中涵盖了多个章节，包括但不限于： 1. **入门篇**：引导读者步入家居自动化的世界，阐述HomeKit的基本概念和应用场景。 2. **探索世界**：深入剖析HomeKit的结构，包括家庭、房间和配件，以便设备能通过单一、简单的源和界面进行管理。 3. **场景构建**：讲解如何实际操作HomeKit来创建实用场景，提高生活便利性。 4. **开发环境**：指导开发者如何配置和利用HomeKit进行应用程序开发。 5. **配件管理**：详细介绍如何与各种配件交互，实现家居设备的智能化。 6. **面向开发者、设计师和制造商**：这部分章节着重讨论了针对不同角色的专业内容，如核心编码问题、设计理念和硬件制造。 7. **配件深化**：进一步探讨配件的开发和创新可能性。 8. **想象空间**：介绍事件、触发器和动作，如何通过HomeKit创造更多智能功能。 9. **云服务与用户管理**：探讨如何与iCloud协作，以及如何确保用户数据的安全与隐私。对于开发者来说，这本书教会他们如何利用HomeKit框架构建易于管理和控制的设备，发挥无限创新潜力。非程序员也能从中找到理解和掌握HomeKit强大功能的便捷途径。无论你是想升级你的智能家居体验，还是希望开发新的产品和服务，这本书都是不可或缺的参考资料。整个指南以Plattsburgh, New York, USA为背景，遵循国际版权法，并提醒读者关于商标使用的注意事项。

CHAPTER 1: Bringing Home Automation Home2

Welcome Home

Projects at Apple (and everywhere else in the technology world) don’t

happen overnight. Often, they take shape gradually as engineers and users

experiment with new ideas and technologies. Many times, a new product’s

evolution is dependent on one, more, or many outside factors. (Just think of

how many technologies went into the first iPhone). HomeKit is a project that

brings together a number of technologies not all of which are under Apple’s

control. The story begins in 2014, but we’ll skip to the critical moment at

Apple’s World Wide Developers Conference (WWDC) in 2016 when Home

App was first shown to the public (at least that part of the public that

comprises developers and the technology media).

“Internet of Things ” (often referred to as IoT) is one of those phrases that

floats around for a while and then starts popping up everywhere as if it

were something brand new. Before long (well, not too long), it seems as if it

has always been with us. Apple’s HomeKit project was announced in June

2014 at Apple’s WWDC. Unlike announcements of Apple products, there

was nothing for consumers to rush out and buy. What was available (to

developers only) was an API (application program interface —the blueprint

for code that developers would start writing to develop with HomeKit). There

were some early devices, but not much beyond that.

Then, HomeKit went quiet for a while.

2015: Apple Unveils New Technologies

Although HomeKit was fairly quiet, Apple engineers and third party

developers were busily at work.

CarPlay Revs Up

Meanwhile, in another part of Apple’s busy campus, engineers were hard

at work on CarPlay which had first been announced a year before HomeKit

at WWDC in 2013 as iOS in the Car. Early implementations on some

models began soon after the announcement. At an event in March 2015,

Chief Executive Officer (CEO) Tim Cook announced that CarPlay would

be available on vehicles from all the major manufacturers by the end of

that year. Sure enough, as the new lines of 2016 models started to hit the

showrooms in the fall of 2015, CarPlay was available on many of them.

CHAPTER 1: Bringing Home Automation Home 3

Although some of the early CarPlay implementations were on high-end

cars, the rollout was across a wide range of vehicles as this quiet project

suddenly (after only several years of development!) moved front and center.

CarPlay lets you integrate your data with your car so that you can listen to

your music, use Siri to update or query your calendar, and otherwise bring

your digital life with you no matter where you’re traveling (provided there’s

an Internet connection).

Turning On Apple TV

In yet another part of the Apple campus, engineers and designers were

plugging away at Apple TV, turning what had been described as a “hobby”

for Apple into a new way of thinking about television. In the announcement of

Apple TV at the beginning of September 2015, CEO Tim Cook said, “The future

of television is apps.” That sentence was repeated many times in the course of

the presentations at that time. The key point is that television has been a linear

medium: you turn it on and watch a show that has a beginning and end. For

archived or recorded shows, you play them and watch them—perhaps from

beginning to end and perhaps jumping around with fast forward and reverse.

No matter how you watch traditional television, it’s a linear process.

Apps are inherently nonlinear. You jump into an app and do what you want,

and then you jump out to do something else that may be in another app,

on another device , and even something unrelated such as going for a walk,

having a meal, or discussing something with friends or colleagues.

Watching the Time

The Apple event in March 2015 at which the CarPlay announcement was

made was focused on Apple Watch.

Putting It Together

You may be wondering why a book on HomeKit starts by talking about

CarPlay, Apple TV, and Apple Watch as well as HomeKit. The answer is

simple: it’s all part of the same thing. It’s a new way of working, playing,

learning, and going about your life. Apple’s implementation of IoT isn’t one

thing over here and another over there. What Apple is doing now is what

it does best: it is integrating products (its own as well as products from

others). Along with the integration, it’s simplifying a total picture so that it

makes useful sense. As many people have pointed out, Apple tends not to

be an innovator in technology. Its forte is innovating in the use of technology

and its integration into our lives so that new technology becomes something

we can’t imagine how we lived without.

CHAPTER 1: Bringing Home Automation Home4

This book shows you how to work with HomeKit as a developer of HomeKit-

compatible apps , a maker of devices, or an integrator of home automation

technologies (a contractor, architect, or designer), or as a user of HomeKit

devices who wants to delve deeper into the issues and technologies that

just get things working. The focus is on HomeKit, but from time to time you

may see how the HomeKit structure shows up in CarPlay and Apple Watch ,

particularly in the design patterns in the software that are extraordinarily

message- and event-driven rather than linear. This shouldn’t be surprising,

because Apple is just as aware as you are that someone can pay attention

to the tap on the wrist from the Apple Watch that reminds him or her that

it’s time to leave work to drive home for that dinner party. Turning into

the driveway on an autumn evening with the early evening settling in, it’s

reassuring to see the HomeKit lights turn on in the house. If it’s starting to

snow, it’s definitely nice not to have to get out of the car to open the garage

door (thanks to HomeKit). Not everything is automated in this little scenario.

The dog barks a welcome so you don’t want to dally in the car even though

you’re listening to some music you like. As you open the door, the music

follows you from car to your speakers in the house. It’s a nice welcoming

scenario, and the dog’s wagging tail may suggest that he had something to

do with it all and please give him a biscuit.

HomeKit, CarPlay, Apple Watch. . . . Yes, you can think of them as great

examples of the Internet of Things. What Apple has been thinking about

is how they all fit together in your life. We are moving away from a world

of huge monolithic apps into one in which small components of apps fit

together. So if you’re expecting to learn how to build a big “killer” HomeKit

app in this book, tamp down your expectation. What you’ll build for HomeKit

are targeted small apps that fit together within the HomeKit framework. If the

user winds up assembling those pieces into a “killer” and convenient home,

that’s just fine, but what we developers do today is build the pieces that

make it possible for users to put together their technology their way.

As noted in the Introduction, the first part of this book (Chapters

1 through 3 )

provides you with background of the technology and ideas behind it. Then,

in Chapters 4 and 5 , we’ll move on to the details of implementation and the

use of HomeKit, focusing on how you can use it yourself. Finally, in Chapters

6 through 9 , you’ll see how to write code that performs the manual tasks

you did in the previous chapters.

If you want to jump ahead, feel free to do so, but make sure to come back to

these introductory chapters. They will help you to understand what you have

to do in the later ones. Otherwise, it may seem like a collection of unrelated

ideas and processes. It’s true that in working with HomeKit (and with IoT in

general), you’re constantly switching from one device to another and one

technology to another, but as long as you keep your mind on the principles

in these first three chapters, it should stay a unified and coherent whole.

CHAPTER 1: Bringing Home Automation Home 5

Moving Beyond Talking Refrigerators

“Connect your refrigerator to the Internet, and it will let you know when

you’re running out of milk!” In June 2000, LG introduced the Internet Digital

DIOS refrigerator that promised to fill this need in the world of consumer

appliances.

As has been demonstrated over the years, the launch of a major new iPhone

or other device from Apple draws crowds of people who sometimes camp

out hours or even days before the Apple Store opens. The Internet Digital

DIOS refrigerator didn’t draw crowds of that size or enthusiasm. In fact, the

$20,000 Internet refrigerator did not succeed in the marketplace. (iPhone is

a different story.)

It is interesting to compare iPhones and Internet refrigerators. In their first

incarnations, they both could be seen as demonstrations of what could

be done with new technologies. In that perspective, the products are

pretty similar. From another point of view, they were very different. Internet

refrigerators promised to put those new technologies to use to do tasks that

were familiar to people (e.g., checking to see how much milk is left on the

shelf). iPhone used those new technologies to do tasks that hadn’t yet been

invented. In fact, many of the tasks that are part and parcel of iPhone today

weren’t even invented by Apple: they’ve been invented and discovered by

people using the technologies and iPhone.

Now it’s time to look at what’s here in the present with HomeKit (and related

Apple automation initiatives). The rest of this chapter brings you up to speed

on the technology of HomeKit and what’s behind it.

How It Works—The View from the

Mountaintop

“Connecting a refrigerator to the Internet” conjures up various images and

possibilities, but, as many consumers have realized, when you start thinking

about why you would do that and how it would work, things are a little murky.

This section is an overview of the connection process. You’ll see that

connecting something to the Internet and HomeKit is a bit different from

connecting a computer to the Internet. What’s important to note is that

this is an overall view of most home automation. The details of HomeKit

are specific to Apple’s approach to home automation, but the overall

architecture is not unique.

Remember that this is the high-level view. In other chapters, you’ll delve

more deeply into the details that make all of the HomeKit environment

work together, and you’ll see what you can do to make HomeKit and your

appliances do exactly what you want.

CHAPTER 1: Bringing Home Automation Home6

Introducing Accessories

What exactly is it that you connect to the Internet and HomeKit? As of

this writing, it can be a light switch, a thermostat (such as the compatible

ones from Ecobee), an electrical plug (the iHome Control Smart Plug is one

and iDevices Switch is another), sensors that can check the weather or

the status of doors and windows (Elgato makes several), or a hub such as

Insteon Hub pro or one of the Lutron bridges.

Before we move on, we need to know how to refer to these in general. You

can call them “devices,” of course, or even “things” (as in Internet of Things).

For this book’s discussion of HomeKit, we’ll refer to them as accessories ,

which is the term that Apple uses. There are some other HomeKit terms that

matter, but they require no special introduction (words like home and room

are used in the everyday senses).

HomeKit Hubs

Now that we know what to call these things (accessories), it’s time to move

on to see how they can be integrated into HomeKit. Within the home, you

have at least one hub. A hub can be an iPad or an Apple TV. It should remain

in the home and be powered on at all times. The hub can communicate over

the Internet so that remote users can get to it and manage the HomeKit

home. If there is more than one hub in the home, they can communicate

with one another as well as with the Internet.

Within the home, an accessory communicates using Bluetooth LE

(low energy) or the WiFi network. Hubs are often referred to as remote

access devices in HomeKit documentation.

Tip See “Setting Up Hubs” in Chapter 9, “Working with iCloud and Users with

HomeKit” to see how to set up an Apple TV or iPad as a HomeKit hub that never

sleeps. The display can sleep, but the device and its network connection needs

to always be available to HomeKit. If you have a TV connected to your Apple TV,

it can go to sleep or even be powered off: It is the Apple TV device itself that

must remain awake and reachable.

剩余136页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

iOS开发者指南：掌握Apple HomeKit智能家居

Arduino-esp8266_homekit_temp.zip

homekit.1.1.4.mpk

ESP8266 Homekit 1路继电器和1个触摸开关模块下载包

from tensorflow.contrib import learn换成import tf_slim as slim后，learn.preprocessing.VocabularyProcessor报错

from tensorflow.contrib.learn.python.learn.preprocessing.categorical import *报错

learn.get_preds

tf.contrib.learn.preprocessing.VocabularyProcessor报错module 'tensorflow' has no attribute 'contrib'

learn.preprocessing.VocabularyProcessor

Input In [211] from scikit-learn.linear_model import LinearRegression ^ SyntaxError: invalid syntax

Consider defining a bean of type com.itheima.learn.demo01.mapper.UserMapper in your configuration.

最新资源