Node-RED backend online · 1.5 s generator
A workshop flow you can watch, test, and inspect.
Three fictional workshop stations change on fresh Node-RED server ticks. The process values are emulated. The message counts, flow uptime and build timing are measurements from the running application.
- Live-generated simulation
- Real app counters
- No physical devices
LIVE SAMPLEconnecting
NL-00000000
- Generated UTC
- waiting
- Update age
- —
- Scenario
- Normal shift
- Source
- Emulated sensors
INJECT→FUNCTION→HTTP→UI
Running system
Live-generated workshop simulation.
Every changing value below arrives from the Node-RED backend. Scenario choices stay in this browser tab and alter only its next read-only responses.
REAL APPLICATION TELEMETRY
Measured by this running flow
Aggregate software measurements only—no visitor identity, host details or customer metrics.
MACHINING BAY
CNC Cell
—°CWaiting
Power—
Cycle progress—
Comfort margin—
Signal age—
FINISHING BAY
Curing Oven
—°CWaiting
Power—
Batch progress—
Comfort margin—
Signal age—
DISPATCH BAY
Packing Line
—°CWaiting
Power—
Throughput—
Comfort margin—
Signal age—
BOUNDED EVENT HISTORY
What changed and why
- Waiting for a backend event.
Retained validation lesson
Reject bad input without rewriting the last valid result.
This preserves the original Node Lab exercise: fixed same-origin JSON enters a separate validation path and every unsupported value is rejected.
LAST ACCEPTED VALIDATION RESULT
22°C
Normal operation
Comfort margin 8.0 °C
Ready for a bounded sample.
Actual executing path
Follow a sample through Node-RED.
The diagram explains the deployed source; the linked JSON is the evidence. It is not a substitute for the running flow.
Creates a new monotonic sample and three fictional station readings.
sampleKey · generatedAtCalculates temperature, power, process values and aggregate app counters.
live-generated-emulationValidates one of four request-only scenarios without changing shared settings.
GET /api/liveReturns explicit provenance, freshness, health, events and runtime metrics.
JSON · no-storeEmulated workshop signals
Useful fiction, clearly labelled
- Three fictional stations.
- Temperature, power and process values.
- Fault, missing signal and recovery stories.
- No machine, building or customer connection.
Measured application facts
Observed from the real flow
- Monotonic backend tick count.
- Flow message and API-response counts.
- Flow uptime and function build time.
- Exact source revision through the evidence API.
Authentic recorded change
One real request, diff, check and release.
Comfort margin was added to the actual Node-RED response path during the coordinated recording. The evidence view keeps the accepted baseline and deployed after-state inspectable.
Read-only capture evidence
No fake terminal, generated chat or public trigger. These links expose sanitized artifacts from actual source and checks.
- Source revision
- development
- Archive SHA-256
- unavailable
Comfort margin
Configured demo limit minus validated temperature, with positive, zero, negative and unavailable handling in the API and dashboard.
Recorded path: actual Function edit · deterministic fixtures · public same-sample readback
Inspectable public source
Run the same teaching project locally.
The public repository contains the pinned Docker runtime, exported flow JSON, schema, tests, setup guide and a sanitized recording evidence view. Private host topology and production credentials are excluded.