Graph
Plots one entity over time. This is where you see trends — a temperature climbing, a battery draining, a value that spikes every few hours.
Settings
| Field | What it does |
|---|---|
| Entity | The value to plot |
| Graph Title | Heading above the chart |
| Chart Type | Line |
| Is Stepped | Square steps between points instead of sloped lines |
| y-axis Min / Max | Fix the vertical scale. Leave empty to fit the data |
| Border width | Thickness of the line |
| Point Radius | Size of the dot on each reading. 0 hides them |
| Width (px) / Height (px) | Size of the chart |
| Color | The line colour |
| Show y-axis ticks | Show or hide the value labels up the side |
| Admin only | Hide it from everyone who isn’t an admin of the device — see Sharing a device |
It needs stored history
A graph draws saved data points, not just the live value. Your device decides when to store one:
sc.sendStatusWithSocket(true); // report and storeIf your firmware never does this, the graph will be empty even though the device is online and other elements show values. See Entities.
Store a point when a reading meaningfully changes, or on a sensible interval. Saving on every loop fills the graph with thousands of identical points and makes it slower to draw and harder to read.
Tips
Stepped suits values that jump between fixed states rather than drifting — a mode, a setpoint, an on/off reading. A smooth line implies values in between that never existed.
Fixing the y-axis is worth doing for anything you compare across devices or over time. On an automatic scale a flat reading with tiny fluctuations looks dramatic, because the axis zooms into the noise.
Point radius 0 is cleaner when you have many readings; keep the dots when readings are sparse, so you can see where the actual measurements are.
To compare several entities at one moment rather than one entity over time, use a Bar graph.