Merge branch 'main' into jacobhylen/P&M-launch

Author: jacobhylen

.github/workflows/cloudflare.yml

@@ -0,0 +1,137 @@
+name: Preview Deployment
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, labeled]
+
+concurrency:
+  group: netlify-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  run:
+    if: ${{ contains(github.event.pull_request.labels.*.name, 'preview') || github.ref_name == 'main' }}
+    runs-on: ubuntu-latest
+    concurrency:
+      group: netlify
+      cancel-in-progress: false
+    env:
+      REPO_ACCESS_TOKEN: ${{ secrets.REPO_ACCESS_TOKEN }}
+      APP_ENV: prod
+      BRANCH_NAME: ${{ github.ref_name }}
+
+    steps:
+
+      - name: Find PR Preview Comment
+        if: github.event_name == 'pull_request'
+        uses: peter-evans/find-comment@v1
+        id: deploy-preview-comment
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          comment-author: "github-actions[bot]"
+          body-includes: "Preview Deployment"
+          
+      - name: Update Comment if exists
+        if: github.event_name == 'pull_request' && steps.deploy-preview-comment.outputs.comment-id != 0
+        uses: peter-evans/create-or-update-comment@v1.4.5
+        with:
+          comment-id: ${{ steps.deploy-preview-comment.outputs.comment-id }}
+          edit-mode: replace
+          body: |
+            ## Preview Deployment
+            Waiting for deployment to complete...
+
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: "npm"
+          cache-dependency-path: "**/package-lock.json"
+
+      - name: Render Datasheets
+        run: cd ${GITHUB_WORKSPACE}/scripts/datasheet-rendering;./render-datasheets.sh
+
+      - name: Copy Static Files
+        run: |
+          mkdir -p static/resources/datasheets static/resources/schematics static/resources/pinouts
+          find ./content/hardware -type f -name "*-schematics.pdf" -exec cp {} ./static/resources/schematics/ \;
+          find ./content/hardware -type f -name "*-datasheet.pdf" -exec cp {} ./static/resources/datasheets/ \;
+          find ./content/hardware -type f -name "*-full-pinout.pdf" -exec cp {} ./static/resources/pinouts/ \;
+          find ./content/hardware -type f -name "*-pinout.png" -exec cp {} ./static/resources/pinouts/ \;
+
+      - name: Gatsby main cache
+        uses: actions/cache@v4
+        id: gatsby-cache-folder
+        with:
+          path: .cache
+          key: ${{ runner.os }}-cache-gatsby-${{ github.sha }}
+          restore-keys: |
+            ${{ runner.os }}-cache-gatsby-
+
+      - name: Gatsby Public Folder
+        uses: actions/cache@v4
+        id: gatsby-public-folder
+        with:
+          path: public/
+          key: ${{ runner.os }}-public-gatsby-${{ github.sha }}
+          restore-keys: |
+            ${{ runner.os }}-public-gatsby-
+
+      - run: npm install
+      - run: npm run build
+
+      - name: Install Netlify
+        run: npm install netlify-cli@17.23.2 -g
+
+      - name: Deploy to Netlify Preview
+        if: github.event_name == 'pull_request'
+        run: |
+          netlify deploy \
+            --dir public \
+            --site ${{ secrets.NETLIFY_SITE_ID }} \
+            --auth ${{ secrets.NETLIFY_AUTH_TOKEN }} \
+            --json \
+            > deploy_output.json
+
+      - name: Deploy to Netlify Prod
+        if: github.event_name != 'pull_request'
+        run: |
+          netlify deploy \
+            --prod \
+            --dir public \
+            --site ${{ secrets.NETLIFY_SITE_ID }} \
+            --auth ${{ secrets.NETLIFY_AUTH_TOKEN }} \
+            --json \
+            > deploy_output.json
+      
+      - name: Generate URL Preview
+        if: github.event_name == 'pull_request'
+        id: url_preview
+        run: |
+          NETLIFY_PREVIEW_URL=$(jq -r '.deploy_url' deploy_output.json)
+          echo "NETLIFY_PREVIEW_URL=$NETLIFY_PREVIEW_URL" >> "$GITHUB_OUTPUT"
+
+      - name: Create PR Preview Comment
+        if: github.event_name == 'pull_request' && steps.deploy-preview-comment.outputs.comment-id == 0
+        uses: peter-evans/create-or-update-comment@v1.4.5
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          body: |
+            ## Preview Deployment
+            🚀 Preview this PR: ${{ steps.url_preview.outputs.NETLIFY_PREVIEW_URL }}
+            📍 Commit SHA: ${{ github.sha }}
+      
+      - name: Update PR Preview Comment
+        if: github.event_name == 'pull_request' && steps.deploy-preview-comment.outputs.comment-id != 0
+        uses: peter-evans/create-or-update-comment@v1.4.5
+        with:
+          comment-id: ${{ steps.deploy-preview-comment.outputs.comment-id }}
+          edit-mode: replace
+          body: |
+            ## Preview Deployment
+            🚀 Preview this PR: ${{ steps.url_preview.outputs.NETLIFY_PREVIEW_URL }}
+            📍 Commit SHA: ${{ github.sha }}

.github/workflows/preview.yml

@@ -94,7 +94,7 @@ Broken URLs will show an error alert. URL must be in the GitHub domain and must
 
 ## Previewing Changes
 
-Whenever you create a Pull Request (PR) GatsbyCloud will create a preview deployment in which you can see how your changes look when rendered on the website. The link to the preview will appear in the comments of the PR. This also works with Draft PRs, but not for PRs created from a fork.
+Whenever you create a Pull Request (PR) and the label `preview` is assigned to it, a preview is created and updated for every commit, as explained at: https://github.com/arduino/docs-content/pull/1931
 
 ## License
 

README.md

@@ -100,7 +100,7 @@ You can run the simple flow shown below using Node-RED's default nodes:
 - drag the **"debug"** node into the workspace
 - connect the two nodes by dragging a wire from the message node to the debug node
 - click on the debug menu from the sidebar on the right
-- press **Depoly** from the header on the top
+- press **Deploy** from the header on the top
 - finally, press on the checkbox of the message node
 
 ![Creating a simple flow](assets/nodered-02.gif)

content/arduino-cloud/01.guides/07.node-red/nodered-intro.md

@@ -0,0 +1,132 @@
+---
+title: 'Google Home'
+description: 'Learn how to connect the Arduino Cloud with Google Home™.'
+tags:
+- Google Home
+author: 'Hannes Siebeneicher'
+featuredImage: 'cloud'
+---
+
+## Introduction
+
+This tutorial guides you on how to connect the Arduino Cloud to your Google Home™ allowing you to interact with your devices, simply through your Google Home Assistant: use voice commands, the Google Home app, or create new routines integrating Arduino solutions.
+
+It requires your board to be [compatible with the Arduino Cloud](https://docs.arduino.cc/arduino-cloud/hardware/devices/).
+
+## Goals
+
+The goals of this tutorial are:
+
+- Create a Google Home compatible variable.
+- Control the built-in LED with Google Home.
+
+## Hardware & Software Needed
+
+- [Arduino Cloud](https://cloud.arduino.cc/).
+- [A Cloud compatible Arduino board](https://docs.arduino.cc/arduino-cloud/hardware/devices/).
+- [Google Home™](https://home.google.com/welcome/).
+
+To familiarize yourself with the Arduino Cloud check out our [getting started guide](https://docs.arduino.cc/arduino-cloud/guides/overview/).
+
+## Cloud Setup
+
+Before we start, make sure you have an Arduino Cloud compatible board.
+
+Then, we need to configure a Thing in the [Arduino Cloud](https://app.arduino.cc/things) consisting of one CloudSwitch variables called `led`. Follow the instructions below to do so.
+
+### Thing & Device Configuration
+
+1. Create a new Thing, by clicking on the **"Create Thing"** button.
+2. Click on the **"Select Device"** in the **"Associated Devices"** section of your Thing.
+3. Click on **"Set Up New Device"**, and continue to set up your device.
+
+If you need more information on how to set up your device check out our [getting started guide](https://docs.arduino.cc/arduino-cloud/guides/overview/#2-configure-a-device).
+
+### Create Variables
+
+The next step is to create a Cloud variable, which we will later interact with via Google Home.
+
+1. While in Thing configuration, click on **"Add Variable"** which will open a new window.
+2. Name your variable `led`, select `Smart home`, and select it to be of a `Switch` type.
+
+![Create Variable](./assets/thingConfig.png)
+
+3. Click on **"Add Variable"** at the bottom of the window.
+4. Make sure the **Smart Home Integration** is set to Google Home.
+
+![Smart Home Integration](./assets/smartHomeIntegration.png)
+
+***Most Cloud variables are compatible with both Alexa and Google Home but there is an icon on the right side of the type that indicates the compatibility***
+
+Your Thing should look something like this when you are finished:
+
+![Finished Thing interface.](./assets/thing.png)
+
+***Learn more about how variables work in the [Variables documentation](/arduino-cloud/cloud-interface/variables)***
+
+### Upload Sketch
+
+Navigate to the Sketch tab and upload the following sketch to your Arduino board.
+
+```arduino
+
+
+#include "thingProperties.h"
+
+void setup() {
+  // Initialize serial and wait for port to open:
+  Serial.begin(9600);
+  // This delay gives the chance to wait for a Serial Monitor without blocking if none is found
+  delay(1500); 
+
+  // Defined in thingProperties.h
+  initProperties();
+
+  // Connect to Arduino IoT Cloud
+  ArduinoCloud.begin(ArduinoIoTPreferredConnection);
+  
+  /*
+     The following function allows you to obtain more information
+     related to the state of network and IoT Cloud connection and errors
+     the higher number the more granular information you’ll get.
+     The default is 0 (only errors).
+     Maximum is 4
+ */
+  setDebugMessageLevel(2);
+  ArduinoCloud.printDebugInfo();
+}
+
+void loop() {
+  ArduinoCloud.update();
+  digitalWrite(LED_BUILTIN, led);
+  
+}
+
+
+/*
+  Since Led is READ_WRITE variable, onLedChange() is
+  executed every time a new value is received from IoT Cloud.
+*/
+void onLedChange()  {
+  // Add your code here to act upon Led change
+}
+
+```
+
+Your board setup is now complete and you can continue to the Google Home app.
+
+### Detect Your Device with Google Home
+
+- **Network Connection:** Ensure the board is connected to the network.
+
+- **Google Home App:** Open the app, navigate to Devices, and click "Add Device."
+
+- **Integration Method:** Select "Works with Google Home" and then choose the "Arduino" action.
+
+![Setup Device](./assets/googleHome_1.png)
+
+- **Device Pairing:** Link your Arduino account if requested and proceed to add your devices (one for each variable) by associating them with a room.
+
+![Link Accounts](./assets/googleHome_2.png)
+
+**Congratulations!** Your device is now successfully configured to work with Google Home.