diff --git a/atom.xml b/atom.xml index e28fbca718..ec450f75ed 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
chmod +x gactions
to make it executable on Mac or Linux.project.json
(in the same directory you downloaded gactions
to) and replace the [YOUR HOME ASSISTANT URL]
below with the URL you use to access Home Assistant.
-Note: This must be an HTTPS URL to work.project.json
(in the same directory you downloaded gactions
to) and replace the [YOUR HOME ASSISTANT URL:PORT]
below with the URL you use to access Home Assistant.
+Note: This must be an HTTPS URL to work. Don’t forget to include the port number if you’re not using port 443.{
"actions": [{
@@ -206,7 +206,7 @@ Note: This must be an HTTPS URL to work.
"automation":
{
"name": "automation",
- "url": "https://[YOUR HOME ASSISTANT URL]/api/google_assistant"
+ "url": "https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant"
}
}
}
@@ -257,10 +257,10 @@ Note: This must be an HTTPS URL to work.
The request_sync service may fail with a 404 if the project_id of the Homegraph API differs from the project_id of the Actions SDK found in the preferences of your project on developer console. Resolve this by:
- Removing your project from the developer console.
- - Add a new project to the cloud console. Here you get a new project_id.
+ - Add a new project to the cloud console. Here you get a new
project_id
.
- Enable Homegraph API to the new project.
- Generate a new API key.
- - Again, create a new project in the developer console. Described above. But at the step ‘Build under the Actions SDK box’ choose your newly created project. By this, they share the same project_id.
+ - Again, create a new project in the developer console. Described above. But at the step ‘Build under the Actions SDK box’ choose your newly created project. By this, they share the same
project_id
.