Expose Vacuum to Google Assistant

That would be better, as a switch it works fine with “on” for start and “off” for dock, but proper Google integration would apparently also add pause, stop and dock, and asking if it’s running. And more flexible commands.

Just added this for a Xiaomi Vacuum - Works fine as a switch and hoping to see native vacuum support in a future revision. Does anyone know if theres a pr to have it added?

Also looking forward for the native integration, would be awesome.

There is a feature request for that, may be you can also vote for it

1 Like

I upvoted that request, also i am wondering about the list of supported devices. I remember seeing that one too when I first set everything up, but cannot seem to find it anymore. The problem is: covers are supposedly exposed and they are, my cover shows up in Google Home. But they are seen as a switch. So saying “Close the cover” actually works, but “Open the cover” does not. I need to say “turn on the cover”. I think I read somewhere that right now, that its only possible to control light and switch-functionality with google home through HA (but would love someone to confirm that).


digging this topic up again since the vacuum cant be exposed as a switch with the new update for the component which got rid of the “type” feature.I think it should be possible with an input_boolean and an automation, I will try my luck and post the results here!

It works as expected. Create an input boolean --> create two automations with trigger on state switch from on to off and vice versa --> expose the boolean to google!

You could also create a template switch and expose that as well. No automation needed in that case.

That is indeed a better way! Works well with less scripting!

My template incase someone wants to do the same sometime(it takes a moment for the switch to turn on/stay on after switching it on, guess its just the response time of the vac):

- platform: template
        entity_id: vacuum.robert
        value_template: "{{ is_state('vacuum.robert', 'on') }}"
          service: vacuum.turn_on
            entity_id: vacuum.robert
          service: vacuum.turn_off
            entity_id: vacuum.robert

I have done it as describled on my customization.yaml file.

It shows on my HA State but I doesn’t list on my google assistant devices list. Have already synced, removed and added again my [test]Device and nothing… any tips?


you can’t expose the vacuum component to GA anymore because the type feature was removed. So you have to use a template switch as explained by @d0nnae in the post before your post…

Is there any news on this?

I see on site below, that vacuum is supported a domain, but can you also do zone map features?

you can create a script or use a webhook in automation, that is how I am using it with neato

Yes, I am indeed now exposing the scripts, but native function would be nicer :wink:

looks like it should be doable now :slight_smile: didn’t notice they updated the site


Oh, that’s nice…
Seems also blinds open/close are now possible…

Who to ask for this development?

wait patiently for someone to develop it? im sure someone will work on it, just need to wait or attempt to do it yourself :wink:

I tried creating a custom component for blinds, but seems more difficult then it looked …
How can we know who created the Google assistant component? Or who is maintaining it?

I am also using the cloud paid edition, for Google assistant… Should have some kind of priority :wink:

is there no one developing this? the start stop trait with zone control is indeed a feature already possible in google assistant :slight_smile:
too bad we cant use it, only the start /stop commands are possible

would be great if we can say like, hey google, vacuum the kitchen …


For now I just use IFTTT to hit a webhook and it works for me…maybe 5 second lag at most?

yeah, i know it can be controlled with ifttt/scripts/switches …
but it would be nice, if we could use it native
then you can control the vacuum device with native words, instead of prepogrammed keywords for activating switches/scrips …
native is cleaner :slight_smile: