Smart Home: These 82 device classes can be controlled natively with Google Assistant and Google Home

The Google Assistant in conjunction with the Google Home app has long since become the smart home center for many people, via which all connected devices are controlled. The range of compatible devices is not just limited to the standard components but has grown into many special areas. We show you all 82 device classes that can be controlled by Google Assistant.

join us on telegram

For some users, it is already a smart home if they can switch the light on and off by voice command, via an app or even automatically. Other people, on the other hand, would like to control many other devices and furnishings, for which the connection to the smart assistants is increasingly becoming an important sales argument. The Google Assistant has been greatly expanded in recent years and can control a large number of device classes that cover all rooms and occasions, both by voice command and via the Google Home app, so that hardly any wishes remain unfulfilled.

With the “Actions on Google”, the Google Assistant can control all imaginable things if the manufacturers provide the appropriate routines. However, this only becomes really smart when the Google Assistant can control the devices themselves and call up and define all important details. Only then can the user issue commands such as “cool the living room” without having to talk to the air conditioning app and the smart windows and their shading beforehand. It is precisely in this area that a great deal of work has been done in recent months.

The Google Assistant can now natively control more than 82 device classes without the need for bridge technology. Of course, some requirements must be met for this and the manufacturer must support the Assistant connection, but Google’s infrastructure will no longer fail with the device classes listed below.

The Google Assistant supports these 82 device classes

  • Alarm system
  • Audio Video Receiver
  • Bathtub
  • Batteries & rechargeable batteries
  • Bed
  • Pressure cooker
  • Dehydrator
  • Extractor hood
  • Shower
  • Window
  • Remote control (for TV)
  • TV
  • fryer
  • garage door
  • dishwasher
  • grill
  • pet feeder
  • heating
  • louvre
  • yogurt maker
  • coffee machine
  • camera
  • stack
  • boiler
  • air conditioning
  • hob
  • refrigerator
  • Charger
  • speaker
  • light
  • humidifier
  • dehumidifier
  • air freshener
  • air cooler
  • air cleaner
  • awning
  • microwave
  • mixer tap
  • mixer
  • mop
  • multicooker
  • oven
  • pergola
  • radiator
  • smoke detector
  • mowing machine
  • roller shutter
    routers
  • Switch
  • Castles
  • cabinet
  • Drawer
  • sensors
  • set top box
  • sound bar
  • sous vide
  • sprinkler
  • hand blender
  • vacuum cleaner
  • Power outlet
  • streaming box
  • Streaming sound bar
  • streaming stick
  • thermostat
  • freezer
  • Gates
  • dryer
  • door
  • door bell
  • Valve
  • fan
  • Curtain
  • Washing machine
  • water treatment
  • water softener
  • Kettle
  • Wifi access point

Interface there, device not available

For each individual device class, there is a set of predefined methods and limits that are understood by Google Assistant. Theoretically, this limits the range of functions, but there is currently no other way to implement it, because the assistant should understand the user’s request as universally as possible and forward the corresponding commands to the connected devices. Much of this could also be controlled beforehand with the Assistant Actions, which can be offered by the manufacturers – but this is less convenient because the user has to establish a conversation with the respective app or device before each command.

Native integration is to be preferred in any case, and Google is currently working with many manufacturers in order to be able to cover as many functions as possible.

The fact that a device class is supported by Google Assistant does not mean that these options can be used directly. As already mentioned, this requires the support of the manufacturers, who have to use the interfaces created by Google. The advantage of the native control is that the Google Assistant can be informed with simple words to switch on the kettle. With the Assistant Actions, on the other hand, you would first have to say that you want to talk to the kettle and then give the command to switch it on.

The complete list including all descriptions and options can be found on this page, which also contains a number of possible commands and programming examples.

Leave a Comment