Amazon can even create routines that use the sound of babies crying, dogs barking, coughing and snoring as triggers. I can create routines that not only don’t need me to actively trigger them, but can run themselves based on inputs from other devices in my house. For example, if my Ecobee smart thermostat senses motion, I can have HomeKit automatically turn the lights on in that room, and even specify when that action should occur. You can also trigger an automation if a sensor detects something. In HomeKit, you can trigger this event by the location of your phone, or if a smart home device is activated - such as locking your front door or turning off the lights. In Google Home, if you want to trigger this routine, you either have to set a specific time, say a command to Google Assistant, or dismiss an alarm. Let’s use the “Leaving Home” routine as an example. This is good - Google lags far behind both Amazon and even HomeKit in what you can do with those devices once connected.
While some of these issues are a result of competing companies not wanting to work with each other, some of it is also due to networking issues.ĭuring its Developer’s Conference, Google said that it would be releasing new tools next year to enable third-party developers to work with Google Home and other Matter devices. In order to get a Zigbee device to talk to, say, a Z-Wave device, or to connect either to the cloud, you’d need a smart home hub.Įven then, there are other compatibility issues - for example, none of Nest’s products work natively with HomeKit, and Ring’s cameras don’t fully work with Google Home. Currently, there are a number of competing standards, including Zigbee, Z-Wave, Bluetooth, and even to some extent, Amazon Sidewalk.
0 kommentar(er)
