Flow Cards
DataVista provides several flow cards for your Homey flows. Use them to display values in widgets or customize their appearance.
Identifiers you define in these flow cards only become available in widget settings after the card has been triggered at least once. This is because the data is only saved when the flow actually runs.
Text
This card allows you to set a text value that can be displayed in the Label widget.
Boolean
This card sets a true/false value, useful for widgets like the Toggle Switch and Status Badge that visualize on/off states.
Percentage
This card sets a percentage value between 0 and 100, ideal for widgets like the Simple Gauge, Advanced Gauge, or Progress Bar.
Range
This card sets a numeric value within custom min/max bounds, giving you more flexibility than a fixed 0-100 percentage. Compatible with the Advanced Gauge and Progress Bar widgets.
Status
This card sets a status indicator combining a color and text, perfect for the Status Badge widget to show states like "Online", "Warning", or "Error".
Gauge Configuration
This card customizes the appearance of Advanced Gauge widgets by defining color gradients that change based on the displayed value.
Progress Bar Configuration
This card customizes the appearance of Progress Bar widgets by defining color gradients that change based on the displayed value.
Countdown
These cards set a countdown target that can be displayed in the Countdown widget. An optional message is shown when the countdown reaches zero (the widget's completion message setting takes priority if set).
Set countdown
Use the date and time pickers to set a fixed target. The pickers do not accept flow tokens.
Set countdown (duration)
Set the target as a duration from now. All numeric fields (days, hours, minutes, seconds) accept flow tokens.
Set countdown (ISO 8601)
Set the target as an ISO 8601 datetime string. The datetime field accepts flow tokens, making this the right card when the target date comes from another flow card or device.
The accepted formats are:
| Format | Example | Timezone handling |
|---|---|---|
YYYY-MM-DDTHH:MM:SS | 2025-12-25T15:30:00 | Treated as Homey's local timezone |
YYYY-MM-DDTHH:MM | 2025-12-25T15:30 | Treated as Homey's local timezone (seconds default to 00) |
YYYY-MM-DDTHH:MM:SSZ | 2025-12-25T14:30:00Z | UTC — converted to Homey's local timezone before storing |
YYYY-MM-DDTHH:MM:SS±HH:MM | 2025-12-25T16:30:00+02:00 | Offset — converted to Homey's local timezone before storing |
If no timezone suffix is included the value is stored as-is and interpreted as Homey's local time, so most tokens that produce a plain datetime string will work without any conversion.