How to Configure Device Settings

Device settings control how your IoT device behaves — transmit power, antenna selection, tag filtering, report grouping, and more. You can configure settings from the Vesbite web UI or push them programmatically from a flow.

Prerequisites

• An adopted device in your Vesbite tenant (see Adopt a Device)
• The device should be online for settings to be pushed immediately. If offline, settings are queued and applied when the device reconnects.

Configuring Settings from the Web UI

Step 1: Navigate to Your Device

Click Devices in the sidebar, then click the device you want to configure.

Step 2: Open the Settings Tab

Click the Settings tab at the top of the device detail page. Vesbite generates the settings form dynamically from the device’s schema, so the fields you see depend on your device type.

Step 3: Understand the Settings Layout

Settings are organized into tabs that group related options. For an RFID reader, you might see:

Click on a tab to switch between setting groups.

Step 4: Adjust Settings

Each setting field has a type appropriate to the value it accepts:

• Sliders — For numeric ranges (e.g., TX power from 10 to 30 dBm)
• Dropdowns — For selecting from a list of options (e.g., antenna port, session mode)
• Toggles — For on/off settings (e.g., enable/disable an antenna port)
• Text fields — For string values (e.g., tag filter patterns)
• Number fields — For precise numeric input (e.g., report interval in milliseconds)

Step 5: Save and Push Settings

Click Save Changes in the top-right corner. Vesbite saves the configuration and immediately pushes it to the device over the real-time connection. The device applies the new settings without requiring a restart.

Note: If the device is offline when you save, the settings are stored and automatically pushed the next time the device connects.

Common RFID Reader Settings

TX Power

Controls how much radio energy the reader emits. Higher power means longer read range but also more interference and potential for reading tags in unintended areas.

Antenna Selection

Most RFID readers have multiple antenna ports (commonly 4). Enable only the ports that have antennas physically connected. Running an enabled port with no antenna attached can damage the reader over time.

Tag Report Grouping

Controls how the reader batches tag observations before reporting them:

• Individual — Every single tag observation is reported separately. High volume but maximum detail.
• Grouped by EPC — Observations for the same tag are deduplicated within a configurable time window. Reduces volume while still capturing all unique tags.
• Summarized — Reports unique tags with read counts and timestamps at intervals. Best for inventory scenarios.

Filtering

Tag filters allow you to limit which tags the reader reports. Common filters:

• EPC prefix — Only report tags whose EPC starts with a specific pattern (e.g., 3034 for a certain manufacturer)
• EPC mask — Include or exclude tags matching a bit mask
• RSSI threshold — Ignore tags below a signal strength threshold to limit read range in software

Configuring Settings from a Flow

You can push settings to a device programmatically using the Update Device Settings action node in a flow. This is useful for scenarios like:

• Changing TX power based on time of day
• Enabling specific antennas based on which zone is active
• Adjusting filter rules based on the current operation

Adding the Update Device Settings Node

1. In the flow builder, click the + button or drag from the activity picker
2. Search for Update Device Settings under the Devices category
3. Add it to your canvas

Configuring the Node

Double-click the node to open its settings panel:

Example settings expression:

{
  "txPower": 25,
  "antennas": {
    "port1": { "enabled": true },
    "port2": { "enabled": false }
  }
}

You can also use Vex expressions to make settings dynamic:

{
  "txPower": {{ variables.targetPower }}
}

Troubleshooting

Settings not applying to the device:

• Verify the device is online. Settings are queued for offline devices but only applied on reconnect.
• Check the device’s live logs on the General tab for errors related to settings.

Setting field not appearing:

• Settings are generated from the device schema. If a setting is missing, the device firmware may not expose it. Check the device documentation or update the firmware.

Settings reverted after device restart:

• Vesbite always pushes the saved settings when a device reconnects. If settings appear to revert, check whether another user or flow has changed them.

Next Steps

• Trigger Device Actions — Send commands to your devices
• Build a Flow — Automate settings changes as part of a workflow
• Settings Reference — Full reference for all settings fields