@cnrd any idea what event gets sent once all devices have initialized and platforms set up? Specifically I’m thinking of Zwave where it can take awhile. I’ll need to do some testing with dropping and re-adding devices especially until roomHint works.
I dropped that file into custom_components\http folder but HA failed with multiple errors. I was not sure what part of that file needs to be updated.
I will wait for the official release. Great work 
You can definitely test applications with other users - even with a Google Group. I’m not aware of any limitations regarding the number of users using the application.
Thanks guy, I’ve got it working in 0.55.x with venv, but it is rather hacky:
- put google_assistant in custom_components (so far it is easy)
- put
http/__init.py__insite-packages/home-assistant/components/http/overwriting the one you previously had
Restart HA, then you can follow the very well written guide that has been merged in PR#3657.
Hi, I am very excited about this new component.
I am running 0.55.2 in a docker on unRAID.
Have copied the files into custom_components and the http/__ init.py __ file as well.
Then I followed the instructions and created the app. It shows up for testing in Google Assistant.
But when I open it I only get:
405: Method Not Allowed
No logs and no errors that I can see.
Any idea where to go next?
Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL]/api/google_assistant/auth
You probably misspelled the url, don’t forget the « auth » part at the end.
2 Likes
So this is not published app (not submitted to Google) will that expire in few hours(days?) same as API.IO app and we will have to re-enable the app from the Google console again?
Hello guys,
I’m trying to get this working, however I’m having problems with the “google_assistant:” tag in configuration.yaml.
When starting Hass.io i am having this error:
2017-10-19 18:12:32 ERROR (MainThread) [homeassistant.loader] Unable to find component google_assistant
2017-10-19 18:12:32 ERROR (MainThread) [homeassistant.setup] Setup failed for google_assistant: Component not found.
Do you have any idea of what’s missing?
Thanks
Did you update the custom_component files?
Any idea what domains this integration supports? I listed cover, lock, and script in the configuration, but the only device that assistant asked me to assign to a room was my garage door (which is a cover).
No I didn’t :S What should I do?
By reading the code I see support from the following “switch, light, cover, media_player, group, fan, scene”
That’s correct, you can see the domains in the config.
script is probably super easy to add as a scene. lock could just be a switch but I’d be hesitant to expose by default.
Can we also expose input_boolean like homebridge? Lot of people (including myself) use input_boolean as toggles for automation and it will be nice to be able to expose the same.
I just checked, emulated_hue exposes input_boolean as well.
1 Like
Seems reasonable to me. Should I just create an issue on github with a todo list of things to be implemented so people can keep track of them? (also easier to link to PRs as they come through)
It will be difficult to keep a track on Github, plus it is not really an issue. Feature requests should be posted in the forums. This is easy enough and we can submit a PR right away.
If it is just adding input_boolean to the DEFAULT_EXPOSED_DOMAINS, I can do it now.
Hi @CedricGatay. Thanks for your tip! It solved my problem.
For those who like me are using docker to get this up and running, you can chage this file by running this command:
sudo docker exec -it homeassistant vi /usr/lib/python3.6/site-packages/homeassistant/components/http/__init__.py
Then you need to make the changes to the file and save it.
Then just run:
sudo docker restart homeassistant
And that’s it!
Thanks for all the help guys.
Would the Google Actions be able to respond to a query like “Where is <device_tracker's name>?” and respond with the state of that device?
Nice work, ready for this to be in the release - I sent ahead and setup an oauth server and actions only to find the documentation link where you didn’t need it 
In any case, seems to be partly working, getting this on the dev branch:
2017-10-20 02:36:02 INFO (MainThread) [homeassistant.components.http] Serving /api/google_assistant to 66.249.84.13 (auth: False)
2017-10-20 02:36:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=3044732784-41, service=turn_on, domain=group, service_data=entity_id=group.stairway_lights>
2017-10-20 02:36:02 WARNING (MainThread) [homeassistant.core] Unable to find service group/turn_on