# Google Assistant voice commands for window coverings

**URL:** <https://community.homey.app/t/google-assistant-voice-commands-for-window-coverings/116228>\
**Category:** Tutorials\
**Created:** [September 17, 2024, 3:40pm UTC](https://community.homey.app/t/google-assistant-voice-commands-for-window-coverings/116228 "2024-09-17T15:40:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArnoudK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnoudk/32/79084_2.png) [@ArnoudK](https://community.homey.app/u/ArnoudK)\
**Post date:** [September 17, 2024, 3:40pm UTC](https://community.homey.app/t/google-assistant-voice-commands-for-window-coverings/116228/1 "2024-09-17T15:40:19Z")

</div>

Since it took me quite a while to find out which Google Assistant voice commands I could give to control my Hunter Douglas/Luxaflex Powerview windows coverings, I decided to make a list to the commands that work for me (and the wife). I will update this list based on your reactions. They might also work for other brands and other devices.

**CONFIRMED**

The following devices and languages have been confirmed to work:

1. Hunter Douglas/Luxaflex Powerview Horizontal Blinds gen 2 (Dutch)
2. Hunter Douglas/Luxaflex Powerview TopDown-ButtomUp Shades gen 2 (Dutch)

**DEVICE NAMES**

Keep device names as short as possible and try to avoid using numbers (I named mine “_room_ left/middle/right”). If you have 4 window coverings, you could name them “Outer Left/Inner Left/Inner Right/Outer Right”).

In voice commands you can address the devices in various ways:

1. **The exact device name** : e.g. “Outer Left” controls only that device;
2. **Part of the device name** : e.g. “Outer” controls all devices that **contain** that word;
3. **The name of the room** : e.g. “Living room” controls all devices **in the specified room** ;
4. **The brand name** : e.g. “Luxaflex” controls all “Luxaflex” devices **in the room where the voice command received** (does not seem to work for the secondary motor);
5. **Multiple device names** : e.g. “Outer Left and Inner Right” controls those devices.

**VOICE COMMANDS**

You can give the following voice commands (where X is one of the device namings mentioned above and X1-X5 is the specific device naming):

| Voice command | X1 | X2 | X3 | X4 | X5 | Vertical blinds | Horizontal blinds | TopDown-ButtomUp |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Open X | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ Fully open | ✅ Move till top | ✅ Move **bottom** bar till upper bar |
| X up | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ , , | ✅ , , | ✅ , , |
| Close X | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ Fully close | ✅ Move till bottom | ✅ Move **bottom** bar till bottom |
| X down | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ , , | ✅ , , | ✅ , , |
| Open X y% | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ Open y% more | ✅ Move y% up | ✅ Move **bottom** bar y% up |
| X y% up | ❌ | ❌ | ❌ | ❌ | ❌ | ❔ , , | ❌ , , | ❌ , , |
| Close X y% | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ Close y% more | ✅ Move y% down | ✅ Move **bottom** bar y% down |
| X y% down | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ , , | ✅ , , | ✅ , , |
| Open/close X till y% | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ Open till y% (100=open, 0=closed) | ✅ Move till y% (100=top, 0=bottom) | ✅ Move **bottom** bar till y% (100=top, 0=bottom) |
| X on y% | ❔ | ✅ | ✅ | ✅ | ✅ | ❔ , , | ✅ , , | ✅ , , |
| Rotate/tilt/ turn X | ✅ | ✅ | ✅ | ❌ | ✅ | ❔ Turn by ?% | ✅ Tilt by approx. 15% | ❌ Move **top** bar till top |
| Rotate/tilt/ turn X back | ❌ | ❌ | ❌ | ❌ | ❌ | ❔ Turn back by ?% | ❌ Tilt back by approx. 15% | ❌ Move **top** bar till bottom bar |
| Rotate/tilt/ turn X y% | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ Turn by y% | ✅ Tilt by y% | ❌ Move **top** bar y% up |
| Rotate/tilt/ turn X y% back | ❌ | ❌ | ❌ | ❌ | ❌ | ❔ Turn back by x% | ❌ Tilt back by x% | ❌ Move **top** bar y% down |
| Rotate/tilt/ turn X till y% | ❌ | ❌ | ❌ | ❌ | ❌ | ❔ Turn till y% (100=left?, 0=right?) | ❌ Tilt till y% (100=top, 0=bottom) | ❌ Move **top** bar to y% (100=top, 0=bottom) |

Note:

1. For TopDown-ButtomUp shades, the bottom bar doesn’t **physically** push the top bar up and top bar doesn’t push the bottom bar down, but **logically** the position is changed. So if top bar is on 75% and bottom bar is moved to 100%, it will **physically** stop at the top bar, but the percentage is still set to 100%, so moving it down e.g. 10%, will not **physically** move it down until it is less than 75%;
2. I have not yet got the top bar of the TopDown-ButtomUp shades to move using voice commands. Since these are in our guest room and only 4 combined positions are required, I have made flows and attached voice commands to them like “I go to bed/sleep”, “I am awake” and “I am up”;
3. Because my horizontal blinds are sometimes not correctly tilted when closing, I have created a flow per room to set position 2 for each horizontal blind to 50%, wait 2 seconds and set then it to 100% and attached to voice command “Reset _room_” to it. Strangly, this does not only fix this problem, but sometimes also helps if a window covering in the room does not react to previous voice commands.

**TRANSLATIONS**

| English | Dutch |
| --- | --- |
| Open | Open |
| Close | Sluit |
| Up | Omhoog |
| Down | Omlaag |
| on | op |
| till | tot |
| Rotate/Tilt/Turn | Roteer |

Note:

1. Dutch: “rotate/tilt/turn X” can be translated to “roteer/kantel/tilt/draai X” or “X roteren/kantelen/draaien”, but “draai/draaien” is constantly interpreted as an instruction to play a song/video, “kantel” only works for X4 (and may be interpreted as “kantoor”), “kantelen” only for X2/X4/X5, “tilt” only for X2/X5 (and may be interpreted as “teelt”) and “roteren” only for X2/X3. Only “roteer” works for all X1-X5 situations (but may be interpreted as “noteer” so speak clearly).

**DISCLAIMER**

I use Dutch commands for horizontal blinds and TopDown-ButtomUp shades. Please let me know if things don’t work in your language or for your window coverings.