Hosted Node-RED for real hardware
From a physical node to a live client experience.
Production measurements appear only when they arrive from the physical Battery Node. This portal has no simulator or synthetic fallback.
Node-RED 5Docker isolatedOne-time access
MQTTTelemetry
FLOW 01Normalize
CLIENTDashboard
BATTERY NODE
Live production telemetry
Battery Node telemetry
CONNECTING LIVE
- Mode
- —
- Cycle active
- —
- Elapsed
- —
- Stop reason
- —
- Delivered
- —
- Energy
- —
- Charged
- —
- Discharged
- —
- Target
- —
- Max time
- —
- Max voltage
- —
- Min voltage
- —
- Start
- —
- Stop
- —
- Cycle current
- —
- Cycle power
- —
Power historyLast 48 seconds · W
-48snow
Output control—
Demo lampState unavailable
Control is locked until demo-lamp isolation, maximum-on timeout, output-off-before-OTA and restart behavior are physically verified.
No fresh physical telemetry has been received. This portal never substitutes simulated values.
A platform, not a one-off dashboard
One pattern. Many node types.
Each node template brings its own real telemetry contract, dashboard and approved command set. Hosting, access and audit stay consistent.
Isolated runtime
Each project runs in a persistent, resource-limited Node-RED container with a versioned flow package.
Live-only production
Missing hardware data is shown as unavailable, never replaced with synthetic measurements.
Scoped client access
Single-use invitations become two-hour sessions with Viewer, Operator or Service permissions.
Remote service bridge
An outbound-only bridge reaches nodes on private networks without exposing the customer LAN.
Client access
Use it once. Control only what was granted.
A client code can be redeemed once, expires unused after 24 hours and opens a two-hour session scoped to one node and one role.
ViewerOperatorService