====== Third-Party Forwarding ====== ---- ===== Third-Party Platform Data Forwarding ===== === Supported Platforms === - **BrewSpy** - **BrewFather** - **Custom HTTP (GrainFater)** ---- ===== BrewSpy Platform Configuration Steps ===== === Step 1: BrewSpy Operations === 1. **Log in to BrewSpy** - Visit [[https://brewspy.app|brewspy.app]] and log in to your account. 2. **Create Device** - Go to the device management page, select **"Add Device"** > **iSpindel**. - Enter the device name and choose a color. 3. **Copy API Key** - Find the **Key** in the **"Configuration"** page of the new device. - Click the **"Copy"** button next to the key to copy it. Warning: The key is the unique credential for the device; do not share it. === Step 2: Cuckoo Platform Operations === 1. **Log in to Cuckoo Platform** - Visit [[https://ckbrew.com|ckbrew.com]] and log in to your account. 2. **Select Device for Synchronization** - Select the device to sync, click **"Enable"** > **"Configure"** > Choose **BrewSpy**. 3. **Configure BrewSpy Sync** - Paste the copied key in the **"Key"** field. Tip: Data will be synced to BrewSpy in real-time after saving. === Verification === 1. **Check Data** - Verify if data from the Cuckoo platform is received on the BrewSpy device page. 2. **Troubleshooting** - If synchronization fails, check if the keys on both platforms match or restart the device. ---- ===== BrewFather Platform Configuration Steps ===== === Step 1: BrewFather Operations === 1. **Log in to BrewFather** - Visit [[https://brewfather.app|BrewFather Website]] and log in to your account. 2. **Enable iSpindel Support** - Go to **"Settings"**, find the **iSpindel** option, and enable it. 3. **Copy Path/URL Link** - Copy the full link after **Path/URL** in the iSpindel configuration page. Example: /ispindel?id=[YOUR_API_KEY] === Step 2: Cuckoo Platform Operations === 1. **Log in to Cuckoo Platform** - Visit [[https://ckbrew.com|ckbrew.com]] and log in to your account. 2. **Select Device for Synchronization** - Select the device to sync, click **"Enable"** > **"Configure"** > Choose **BrewFather**. 3. **Configure BrewFather Sync** - Enter a custom name (e.g., "October IPA") in the **"New Name"** field. - Paste the copied Path/URL link in the **"Path/URL"** field. Tip: Data will be synced within 15 minutes after saving. === Verification === 1. **Check Data** - Verify if the device is online and receiving data on the **"Devices"** page in BrewFather. 2. **Troubleshooting** - If synchronization fails, check if the URL contains the full API key or restart the device to force a refresh. ---- ===== GrainFater Custom Configuration Steps ===== === Step 1: GrainFater Operations === 1. **Log in to GrainFater Platform** - Visit [[https://grainfater.com|GrainFater Website]] and go to the **"My Devices"** page. 2. **Add Monitoring Device** - Click **"Add Device"** > **"Fermentation Monitoring Device"**, select **iSpindel Type**. - Enter a device name (e.g., "Main Fermenter Monitor"). 3. **Get Server Parameters** - Click **"View Instructions"** on the device details page to find the following parameters: - **Server Type**: `HTTP` - **Server Address**: `community.grainfater.com` - **Server Port**: `80` - **Server URL**: `/iot/ABCD-1234/ispindel` Example URL: /iot/ABCD-1234/ispindel === Step 2: Cuckoo Platform Operations === 1. **Log in to Cuckoo Platform** - Visit [[https://ckbrew.com|ckbrew.com]] and log in to your account. 2. **Select Device for Synchronization** - Go to **"Device Management"** > **"Third-Party Push"**, and select the device to sync. 3. **Configure Custom HTTP** - Fill in the parameters provided by GrainFater: - **Server Type**: `HTTP` - **Server Address**: `community.grainfater.com` - **Server Port**: `80` - **Path / URL**: `/iot/ABCD-1234/ispindel` Warning: Parameter formats must match GrainFater documentation exactly; otherwise, synchronization will fail. === Verification & Maintenance === 1. **Verify Data Synchronization** - Check if the **"Latest Data Time"** is updated on the GrainFater device details page. 2. **Troubleshooting** - If synchronization fails, check: - If the server port is open (e.g., `80` must be allowed by the firewall). - If the Path / URL contains the correct device key.