Exposed input_button not seen in shared houses in google home

Configuration
1

Hi everybody, i dunno where I’m making mistakes, but this is the situation:

I created several input_buttons, everyone of them is working, which activates automations that I need .

In the configuration.yaml file I exposed to Google home (which I already use for sensors and switches) these buttons, for the second part of the job which is to integrate these buttons in Google Home’s automations(they appear in google as “scenes”) that I need.

things have to be made in this way for reasons that are useless to show now.

From google home, I created these automations in a shared house, where other users can see the automations as shared ones, I checked twice, the automations are not personal.they belong to the house.

Anyway, from the other users devices, I can see the automations, which don’t include the scenes (that is, the input_buttons in home assistant), and when I tried to set them manually in Google Home, the scenes neither appear among the single automation options.

I can’t figure out where is the mistake.

Can anyone help me?

this is an example of input_button

google_assistant:
  project_id: myprojectid
  service_account: myhiddenfile.json
  expose_by_default: false
  entity_config:
    input_button.bottone_salotto_tv_metti_sky_tg:
      name: cambia canale su Sky TG in salotto
      expose: true
      room: Salotto

I underline, i already use google assistant for switches and sensors and it works like a charm, this trouble is only about input_buttons… :sweat_smile:

2

I have the same. I have a fingerbot and I made an input_button to have it behave like a simple push button. Works perfectly in HA. It is in my google home config file. All other switches, lights and sensors work and are available as configured in the Google home app.
The strange thing is that I can activate the button by voice. “Ok Google, Turn on espresso”. But it is not visible as a button in Google home app.

I also have this in my config file:

Exposed domains:
  - switch 
  - light 
  - sensor 
  - script 
  - input_button
3

Hi, as from documentation, I found out that binary_sensors are excluded from google-assistant integration exposure(at least officially)

I decided to move ahead like a mule, and see what happens:

after I exposed (in my case) some door sensors, which are of course binary, I made my usual magic to let them appear in google home, and they showed up.
the trouble is about the status update, which doesn’t happen if you don’t refresh google home app.

By reading here and there , somebody was suggesting to use helpers that instead should work, according to the reason that you would use vocal request to check if a door is open or closed, and virtual switch displayed in the google home 's interface wouldn t be involved ,so you couldn’t create a situation where the sensor is on and the switch could potentially be off.

I find this unacceptable so I tell you what I -WILL- try(in the future).

by using automations and an input_button helper, I’d try to create a turnaround to the binary sensor state which retrieve the sensor’s status and if the condition “on” is true, then it triggers a vocal answer to the device i’m asking the window/door status.same thing about the other automation and input button, about the “off” status. after that, from google home, i’d set an automation for the vocal query that should activate the input button(helpers are recognized in google assistant integration) so at least about the cool thing of the voice commands, you can get the job done.

hope this can help.

Regards