Docs
Widgets / directory

SuperChart

ENHANCED_GRAPH

Historical and live chart surface with multiple streams, periods and annotations.

At a glance

Default8 x 5
Minimum4 x 3
Resizeboth
Pinrequired
Interactiveyes

Behavior

  • Supports multiple graph types and period selectors in the app.
  • Best used for telemetry history, comparisons and trend analysis.
  • Eventually pairs with annotations and AI summaries.

Firmware contract

Write values normally; historical windows are requested separately from the connector.

On the app side this widget snaps to the 8-column square grid and uses both resizing. Its raw type is ENHANCED_GRAPH and the matching icon token in the app is chart.xyaxis.line.

Pin support: One or more data streams, commonly virtual pins but also compatible with mapped hardware streams through connector models.

Transmission: Live writes happen as normal pin updates; historical ranges are fetched through dedicated graph requests and decompressed from binary/zlib payloads.

Canvas preview

docs.widget.preview
SuperChart
050100-24h-12hnow
temphumid
SuperChart

Widget contract

PropertyValue
Raw typeENHANCED_GRAPH
Default size8 x 5
Minimum size4 x 3
Resize modeboth
Pin requirementrequired
Pin supportOne or more data streams, commonly virtual pins but also compatible with mapped hardware streams through connector models.
Interactiveyes
TransmissionLive writes happen as normal pin updates; historical ranges are fetched through dedicated graph requests and decompressed from binary/zlib payloads.

Allowed pin families

One or more data streams, commonly virtual pins but also compatible with mapped hardware streams through connector models.

Transport path

Live writes happen as normal pin updates; historical ranges are fetched through dedicated graph requests and decompressed from binary/zlib payloads.

Operational limits

History is not derived from the live widget alone; it depends on server graph endpoints

Configuration surface

  • dataStreams define per-series color and aggregation
  • period chooses the requested history window
  • showLegend and graph type shape the visual density

Limits and caveats

  • History is not derived from the live widget alone; it depends on server graph endpoints
  • Large charts should respect dashboard density because the minimum footprint is still 4x3

Firmware example

A minimal pattern that matches how this widget usually talks to the board.

superchart.ino
void loop() {  Blynk.virtualWrite(V8, readCurrent());  Blynk.virtualWrite(V9, readVoltage());}

Layout notes

Canvas footprint

8 x 5

Default footprint in the Plynx canvas before user resizing.

Resize floor

4 x 3

The minimum size accepted by the app during drag-resize.

Interaction model

Live input

Whether the user edits state directly or only reads it.

Related widgets

Terminal

Bidirectional terminal for commands, logs and line-oriented interaction.

Map

Live position widget with device points, tracks and board-originated GPS updates.

Table

Dynamic multi-row table fed by firmware commands and row updates.

Eventor

Automation rules widget for conditions, actions, mail and notification flows.