answer from MY google home
“Sorry I don’t understand”
Ah. Now I get. Sorry for being a bit slow on the uptake.
For me it works (just checked again).
Maybe a feature that is gradually rolled out and has not reached your Home yet?
Is that your case?
It was when I set it all up, though since then I’ve purchased a Home Mini.
This could be a regional/rolling out issue (I think you’re in Italy?). I’m in Canada and the answer back from Google Home last night to “Hey Google, sync my devices” was “Sorry I don’t understand”. I just tried it again now and it replied, “OK, syncing [my hass test app name]”, and checking the Google Home app under Home Control shows an updated and accurate list of my devices (I marked one as hidden in HASS before trying it just to test).
So I think you just have to keep trying, it will eventually work once the feature gets to you.
No, you don’t. You probably do need the Home app which contains Home Control. Having said that you can reach Home Control through Settings in Google Assistant - not sure if that screen is provided by Home app or the Assistant app.
I am looking for a little help with the Google Assistant integration. I have Xiaomi Temp sensors that are working with HomeAssistant and I would like to get data from them through my Google Home.
I have the Google Assistant setup completed successfully and I have the following added to my customize.yaml for the sensor:
sensor.temperature_158d0001b952a3:
friendly_name: 1st Floor Temp
google_assistant: ‘true’
google_assistant_type: climate
aliases:
- living room temp
I have also added the sensor to the “Living Room” in the google home app.When I ask my Google Home “What temperature is it in the living room?” she replies “Sorry, I am unable to reach living room temp right now”
Any ideas on getting this working?
Thanks!
Sorry to post again, but any advice on this?
Will surely try the sync tonight. Until now it was a bit of a pain having to unlink, relink and re-add location for each component.
Thanks for the heads up
slightly off topic, I’m trying to get GH to run a script, but it doesn’t seem to be recognised.
- How can / should I name the script - Currently set to “Radio” which I understand may be a reserved keyword
- How do I make GH actually recognize and run the script? So far it seems happy with my lights and a couple of input_boolean that I set as switches, but doesn’t like the script
Thanks
It currently isn’t implemented yet. There is an open pull request to add this on the github
Im in Argentina. Ended up buying a couple of Mini as they are rather cheap now. Let’s see in a few weeks then i get them if it’s regionally blocked or just by language.
Crap, just got 2 minis.
HI. I have it working fairly well. However, every time i ask the assistant to turn on/off a switch. I get the wollowing reply AFTER the switch was activated:
You got it, turning on the Kontoret Ljys. I’m sorry, there was an error and I’m unable to control your home device.
So it does do the correct thing, but the answer is wrong.
Any idea what this is and how it can be avoided?
hmm, turns out groups don’t have on/off like I thought, I’m going to have to rethink that one and fix it. I think I can solve it by using homeassistant.turn_on instead of trying to figure it out myself (since ha turn_on already does that). Sorry about that
I know this command works with groups of mixed device types. Have you made this change?
I’m on 0.57.3, and I’ve just grouped all of my downstairs switches and dimmers together to try to tell google to turn off the downstairs lights, but it fails due to: Unable to find service group/turn_on.
I was having the same issue with google not turning off a group of lights. I just added
group.kids_lights:
google_assistant: true
google_assisteant_name: Kids Lights
google_assistant_type: light <-------
to customization.yaml and it works perfectly now.
1 Like
I solved it with a workaround with scripts.
For each of my light groups I have two scripts
all_office_lights_on:
sequence:
- service: homeassistant.turn_on
data:
entity_id: group.office_lights
all_office_lights_off:
sequence:
- service: homeassistant.turn_off
data:
entity_id: group.office_lights
Which I expose too google. Not perfect, but working. After implementing that I realized that I could have defined a template switch for each light group to have a more elegant solution.
Maybe I’ll re-factor when I have some time left.
Simple idea. Thanks for the tip
group.kids_lights: google_assistant: true google_assistant_name: Kids Lights google_assistant_type: light <-------
I’m not so sure this would work in my situation. This would call light.turn_off which wouldn’t work for the switches in that group, would it not?
I solved it with a workaround with climate component
climate: - platform: generic_thermostat name: climate1 heater: switch.demo1 target_sensor: sensor.temp_fahrenheit
where sensor.temp_fahrenheit is temperature sensor and switch.demo1 is fake mqtt switch
The only problem is that Google Home replies “It’s currently 81 degrees and climate 1 is off”
I have HA running in Docker on version 0.59.2. I setup the google_assistant component but I receive this error when the service starts or when I run the check config script:
Failed config
General Errors:
- Component not found: google_assistant
- Setup failed for google_assistant: Component not found.
I thought this component was now available in the latest release? Is this not the case? If it is not yet available then why is it not noted in the components directory at home-assistant.io.
Here is the relevant config section in my yaml file:
google_assistant:
project_id: !secret google_cloud_project_id
client_id: !secret google_cloud_client_id
access_token: !secret google_cloud_access_token
# agent_user_id: [a string to identify user, default is auto-generated]
api_key: !secret google_homeassistant_api_key
exposed_domains:
- switch
- light
- group
It is available and your config looks good. Are you certain you are running the latest 0.59.2?