@dramamoose It works with multiple users on the Google Home (speaker), my wife and I are both able to tell it to do stuff. Just like the emulated_hue does. (We have the Google home linked to our individual accounts and trained to our individual voices).
@PhilK I feel like it would be most user-friendly to do a SYNC request on startup, as that is probably the most likely place where changes could happen.
Also a note on the multiple users on Google assistant (Not a speaker), there is some stuff in one of Google’s docs about sharing the test version with other people, I haven’t tested it out, as my wife does not use the Google assistant app anywhere. Not sure how many accounts are able to share the test version, but that may be an easier way than setting up multiple instances.
@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.
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.
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?
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?
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.
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).
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.
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.