refactor: fixed paths to images on google integration page
@@ -1146,7 +1146,7 @@ theme = "doc-theme"
|
||||
weight = 90
|
||||
|
||||
[[menu.main]]
|
||||
name = "Getting Started with Pybytes"
|
||||
name = "Getting Started"
|
||||
url = "/pybytes/getstarted/"
|
||||
identifier = "pybytes@getstarted"
|
||||
parent = "pybytes"
|
||||
@@ -1223,7 +1223,7 @@ theme = "doc-theme"
|
||||
weight = 20
|
||||
|
||||
[[menu.main]]
|
||||
name = "Visualise data from your device"
|
||||
name = "Visualise data"
|
||||
url = "/pybytes/dashboard/"
|
||||
identifier = "pybytes@dashboard"
|
||||
parent = "pybytes"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Google Cloud IoT
|
||||
|
||||
Whenever one of your integrated devices sends a signal to our broker, we republish the binary payload to the Google endpoint specified for the integration by the MQTT protocol.
|
||||
Whenever one of your integrated devices sends a signal to Pybytes, we republish the binary payload to the Google endpoint specified for the integration by the MQTT protocol.
|
||||
|
||||
## Integrate your devices
|
||||
|
||||
@@ -8,35 +8,35 @@ Whenever one of your integrated devices sends a signal to our broker, we republi
|
||||
2. Make sure to [enable billing](https://cloud.google.com/billing/docs/how-to/modify-project) and [the Cloud IoT Core API](https://console.cloud.google.com/flows/enableapi?apiid=cloudiot.googleapis.com&redirect=https://console.cloud.google.com&_ga=2.236270149.-51976751.1517992223) for the project.
|
||||
3. On the Google IoT dashboard, you should be able to see that your project is correctly bound to Google IoT services
|
||||
|
||||

|
||||

|
||||
|
||||
4. Now let's access Pybytes and click _Integrations > New integration > Google Cloud_
|
||||
|
||||

|
||||

|
||||
|
||||
5. You'll see that Pybytes requires you to authenticate with your Google account. The account you'll be using must have the privileges to access that project.
|
||||
|
||||

|
||||

|
||||
|
||||
6. Once you've logged in, the first thing to do is to specify the project's ID and the region. This is required to correctly identify a resource and list all the related [registries](https://cloud.google.com/iot/docs/concepts/devices#device_registries).
|
||||
|
||||

|
||||

|
||||
|
||||
7. The following step allows you to create a new registry or select an existing one. Whenever you choose a registry, the corresponding topics will be loaded in the dropdown menu. This is required by Google, but it's different from the topics used by the integration to publish payloads to Google Cloud. For further information, [please read this section](https://cloud.google.com/iot/docs/how-tos/mqtt-bridge#publishing_telemetry_events).
|
||||
|
||||

|
||||

|
||||
|
||||
8. The last step allows you to choose the devices you want to integrate and summarises the identifying elements of this integration.
|
||||
|
||||

|
||||

|
||||
|
||||
9. Once you click _Create_,if the operation is successful, you'll be able to see a screen stating the correct integration.
|
||||
|
||||

|
||||

|
||||
|
||||
If you access the registry on Google Cloud, you'll be able to see the newly created device there as well.
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
## Final considerations
|
||||
|
||||
|
Before Width: | Height: | Size: 192 KiB After Width: | Height: | Size: 192 KiB |
|
Before Width: | Height: | Size: 234 KiB After Width: | Height: | Size: 234 KiB |
|
Before Width: | Height: | Size: 143 KiB After Width: | Height: | Size: 143 KiB |
|
Before Width: | Height: | Size: 210 KiB After Width: | Height: | Size: 210 KiB |
|
Before Width: | Height: | Size: 218 KiB After Width: | Height: | Size: 218 KiB |
|
Before Width: | Height: | Size: 211 KiB After Width: | Height: | Size: 211 KiB |
|
Before Width: | Height: | Size: 271 KiB After Width: | Height: | Size: 271 KiB |
|
Before Width: | Height: | Size: 235 KiB After Width: | Height: | Size: 235 KiB |