This integration allows HomeSeer users to control their devices and device features with simple commands using Google Home powered devices. This implementation supports ON, OFF, DIM and THERMOSTAT devices. |
HomeSeer Devices and Features For...
HomeSeer Events
You'll need to add a user account to your HS4 system with your MyHS credentials and you'll need to enable Admin and Local permissions for this account. Once that's done, you'll need to enable voice commands for the HomeSeer devices or device features you wish to control with Google Home. Note that if you have multiple HomeSeer systems and a Premium MyHS account, you'll need to create unique MyHS users for each system. Please follow the steps outlined in this doc: Using Alexa with Multiple HS Systems. Then, follow the steps below:
Open your HomeSeer system's web interface and navigate to Setup > Users. Add a new user with your MyHS account credentials. Enable Admin and Local permissions. 
Devices or features must be manually enabled for voice commands in order to be discovered and controlled by Alexa. In this section, we'll show you how to check the voice settings of your current system and how to edit those settings to yield the best results.
Follow the steps below to determine which devices or features are currently enabled for voice in your HS4 system:
In general, enabling devices is all that will be required for most systems.
However, if you have devices with multiple controllable features, you'll need to enable features for those devices. Such devices include (but are not limited to)...
Use the guide below to determine which method is best for enabling voice with your system. Then use the steps below to enable voice commands for your devices or for your feature(s).
| Enable Devices | Enable Features | Enable Root Device & Features |
|---|---|---|
| Use this option for devices that have only one controllable feature or only a controllable root device. | Use this option for devices that have more than one controllable feature. | This duplicates "Enable Devices" option. |
|
|
|
| If the root device is enabled for voice, the discovered device will use the root name and will only control either the root device or the first controllable feature. In the example above, the Dimmer will be controlled. | If the root device is disabled for voice, and the features are enabled, the discovered device(s) will use the feature names and every controllable feature will be controlled. In the example above, the Candle Lights & the Sofa Lights will be controlled. | If the root device and features are checked, the features will be ignored and the discovery will work as if only the root device was checked. In the example above, the discovered device will be the Dual Lamp Module and only the Candle Lights will be controlled. |
Voice commands can be enabled by editing the settings of of a single device or by using the Bulk Edit feature or HS4.
By default this integration is designed to recognize the Device Name or Feature Name in your spoken commands. However, this may not always be desirable. For example, let's say you have a Floodlight Sensor device with a feature called Switch. Normally, you'd have to speak "Hey Google, turn on the Floodlight Sensor Switch". That's pretty wordy and not very intuitive. To improve on this, we've included a Voice Command field that's designed to override the name field. To use it...
In the example below, "Flood Lights" are entered into the Voice Command field. The resulting spoken command now becomes: "Hey Google, turn on the Flood Lights".
After device discovery is complete, you should be able to control any discovered voice by using any combination of its name and location. For example, if the discovered device is First Floor Living Room Candle Lights, the following commands should work:
If for any reason, you can't control your devices after discovery, here are a few things to check:
If everything is working but you still can't control devices, open a service desk ticket for help.
