Appearance
Widget data keys
Widgets read the keys you configure. They do not invent sample values. If a widget shows empty or “No data”, check the key names on the device (Devices → attributes / telemetry keys) match the widget settings.
Common patterns
| Widget family | Typical keys | Notes |
|---|---|---|
| Charts / KPI / LED / gauges | One or more telemetry keys (temperature, voltage, …) | Bind device or alias + key |
| Map / route | Location telemetry (lat/lon or a location object) | Needs a recent stored or live point |
| GPIO control / status | Channel keys or command keys | Status uses latest telemetry; control sends commands |
| Slider / attribute form | Shared attribute keys | Slider writes and reads SHARED attributes |
| Toggle / switch | Telemetry feedback key + command method | Shows “No data” until a value exists (stored latest is loaded on open) |
| Generator monitoring | Generator telemetry set (fuel, RPM, voltage, …) | Must match your generator profile keys |
| Pool water quality | ORP, pH, free chlorine, temperature, … | Must match pool device keys |
| Drilling monitoring | Depth, RPM, pressure, … | Must match drill device keys |
| Factory / machine fleet | Runtime / state keys used by that solution | Follow the solution setup guide |
| Image / HTML / video | URL / HTML content | Not telemetry; bad URL = empty panel |
After open
Widgets that used to wait for a live push now load the latest stored telemetry (and SHARED attributes for slider) when the dashboard opens, then continue with live updates.
