# Virtual devices not selectable as trigger in Google home

**URL:** <https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272>\
**Category:** Questions & Help\
**Created:** [October 29, 2024, 5:11pm UTC](https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272 "2024-10-29T17:11:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dvk8](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dvk8/32/17154_2.png) [@dvk8](https://community.homey.app/u/dvk8)\
**Post date:** [October 29, 2024, 5:11pm UTC](https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272/1 "2024-10-29T17:11:03Z")

</div>

Hi,

I haven’t added devices in a while and wanted to set a few things up. I have got some devices set up in Google home which I want to control from homey. Before, I used to make a virtual device in Homey and add it as a trigger for an automation in Google Home. However, when I want to create a new automation in Google Home, the virtual device is not visible as a trigger for the routine.

Is this a recent thing and is there any other way around this?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 29, 2024, 5:33pm UTC](https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272/2 "2024-10-29T17:33:37Z")

</div>

Yeah it seems to be more restricted.  
Which virtual device do you use? The onboard ones?

To trigger automations it still works with (advanced) virtual devices of the “Kettle” class

> [@Controlling devices at Google Home from Homey?](https://community.homey.app/t/controlling-devices-at-google-home-from-homey/73201/20):
>
> I ended up finding a better option. Essentially, use the device for kettle. And then a button with on/off will allow running Google automation with on and off

---

<div class="post-metadata">

**Author:** ![dvk8](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dvk8/32/17154_2.png) [@dvk8](https://community.homey.app/u/dvk8)\
**Post date:** [October 29, 2024, 6:25pm UTC](https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272/3 "2024-10-29T18:25:26Z")

</div>

Thank you, this worked. I was using the default virtual devices app from homey. I now downloaded the device capabilities app. I chose an on/of template and changed the type to kettle

---

<div class="post-metadata">

**Author:** ![izekube](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/izekube/32/79653_2.png) [@izekube](https://community.homey.app/u/izekube)\
**Post date:** [June 26, 2025, 8:40pm UTC](https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272/4 "2025-06-26T20:40:48Z")

</div>

I also noticed that only some device classes work.  
Outlet does not work.  
Button does not work.  
Fan (with on/off) works excellent.

Not very intuitive.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 27, 2025, 12:04am UTC](https://community.homey.app/t/virtual-devices-not-selectable-as-trigger-in-google-home/119272/5 "2025-06-27T00:04:26Z")

</div>

No, it’s about what’s supprted by Google and what isn’t.  
But, sometimes they add device types.  
I noticed Presence sensors f.i. are also usable now.

But thanks, I’ll add _Fan_ to my list of “geez, that works!”