See it in the Viewer

Everything so far you did as an author. This step you do as an operator — the person who never opens Scenes Studio and only ever sees what has been published.

Switch to the Viewer.

Open the scene

The Viewer lists the scenes published to you. Your scene is there; your drafts and your uncommitted work are not.

Open it. What you are looking at is the revision you published, assembled from the frozen snapshot — not the draft you left behind in Scenes Studio. If you had kept editing after publishing, this screen would be unchanged until you published again.

Read the value

The widget shows your reading, formatted the way the interpretation said: the right number of decimals, the unit, and a colour if the value fell into one of your bands.

The Viewer re-reads live values every few seconds, so you can watch the chain work end to end. Send another sample with a new timestamp and a noticeably different value:

curl -X POST "$ONTWINS/api/v1/agent/ingest" \
  -H "Authorization: Bearer $CRED" \
  -H 'Content-Type: application/json' \
  -d '{
    "datasetId": "ds_paste_the_id_here",
    "samples": [
      { "signal": "temp", "at": "2026-10-01T09:10:00Z", "value": 29.5 }
    ]
  }'

Within a few seconds the widget changes. If you crossed a band boundary, its colour changes with it.

That is the whole path, running: your request, the dataset, the wiring, the entity, the interpretation, the widget. Nothing between them is scheduled or batched.

Move the time bar

A screen in OnTwins has two independent time axes, and the time bar is where you move along them.

The data axis — which moment of the data you are looking at. It has three positions:

• Live — the latest values, refreshing as they arrive. This is where you have been.
• A moment in the past — the screen as the data stood at one instant.
• A replay of a range — the screen playing back a window of time at a chosen speed.

The configuration axis — which version of the screen you are looking at. Normally it follows whatever is currently published, so operators always get the newest published screen. It can also be pinned to one specific revision, which is how a link can keep showing the same screen even after the scene is rebuilt.

Keeping these apart is what makes a question like “what did this screen look like last Tuesday, with last Tuesday’s layout?” answerable at all.

Try moving back

Move the data axis to a time before you sent your first sample.

The widget goes blank or grey rather than showing an error. That distinction is deliberate: there genuinely was no value then, which is a legitimate absence, not a failure. OnTwins keeps “there is no value here” and “something went wrong” visually separate, so an operator is never left guessing which one they are seeing.

Return to live, and the current value comes back.

---

You have taken one value from outside OnTwins to a screen somebody can act on, and seen every link in that chain. Next steps points you at where to go from here.