How to Adopt a Device
Adopting a device connects it to your Vesbite tenant so you can monitor its status, send commands, configure settings, and use it as a trigger or action target in your flows. This guide walks you through the full adoption process.
Prerequisites
- A Vesbite account with an active tenant
- An IoT device running Vesbite-compatible firmware (e.g., an Impinj R700 RFID reader)
- The device powered on and connected to the same network (or a network that can reach Vesbite’s servers)
Step 1: Find the Device’s Adoption Code
Every Vesbite-compatible device displays the adoption code on its main page. Simply open a browser and navigate to the device’s IP address:
http://<device-ip>Replace <device-ip> with your device’s IP address. You will see the adoption code displayed prominently on the device’s home screen.
The adoption code has two parts separated by a hyphen:
| Part | Example | Description |
|---|---|---|
| Device ID | Q2ZB | A 4-character identifier unique to this device. It never changes. |
| Rotating code | 332783 | A 6-digit code that refreshes every 30 seconds. |
The full code looks like: Q2ZB-332783
Tip: Keep the device’s adoption page open in a separate tab so you can quickly copy a fresh code if the current one expires.
Step 2: Navigate to Devices in Vesbite
In the Vesbite web app, click Devices in the sidebar to open the devices list. This page shows all devices currently connected to your tenant along with their status.
Step 3: Start the Adoption
Click the Add Device button in the top-right corner of the devices page. This opens the device adoption page with an input field for the adoption code and brief instructions.
Step 4: Enter the Adoption Code
Type or paste the full adoption code from your device into the input field. Make sure to include the hyphen between the device ID and the rotating code (e.g., Q2ZB-332783).
Important: The rotating portion of the code refreshes every 30 seconds. If the code expires before you submit, go back to the device’s main page and grab the new code.
Step 5: Complete the Adoption
Click Adopt Device. Vesbite will verify the code and establish a connection to your device. On success, you are redirected to the device’s detail page.
What Happens After Adoption
Once adopted, Vesbite automatically:
- Loads the device schema — The device reports its capabilities (events it can emit, actions it supports, settings it accepts). Vesbite uses this schema to generate the Actions tab, Settings tab, and flow activity options.
- Starts heartbeat monitoring — Vesbite tracks the device’s connection status in real time. The device list shows a green “Online” badge when the device is connected and a red “Offline” badge when it is not.
- Streams live logs — The General tab on the device detail page shows a real-time log of device events and messages.
- Makes the device available in flows — You can now use this device as a trigger source (e.g., “Device Event” trigger) or an action target (e.g., “Invoke Device Action” node) in your workflows.
Troubleshooting
Device not appearing after adoption
- Verify the device has network connectivity. Try pinging the device from your computer.
- Confirm the device is running Vesbite-compatible firmware. Check the device’s main page in a browser.
- Make sure the adoption code was entered before it expired. Codes refresh every 30 seconds.
Device showing as offline immediately after adoption
- Confirm the device can reach Vesbite’s servers on outbound ports. Check your firewall rules.
- Restart the device and wait 30 seconds for it to reconnect.
- Check the device’s local configuration page for any error messages.
Invalid adoption code error
- The rotating code refreshes every 30 seconds. Go back to the device’s main page and copy the latest code.
- Make sure you are entering the full code including the hyphen (e.g.,
Q2ZB-332783). - Verify you are not accidentally including extra spaces before or after the code.
Device adopted but no events appearing
- Some devices require an action to start emitting events. For example, an RFID reader needs a “Start Reading” action before it will report tag reads. See Trigger Device Actions.
- Check the device’s Settings tab to make sure it is configured for the events you expect.
Next Steps
- Configure Device Settings — Adjust your device’s parameters like TX power and antenna selection
- Trigger Device Actions — Send commands to your device manually or from a flow
- Build a Flow — Create an automated workflow triggered by this device