Data connections and binding

Separate the data source, the data item, UI binding and scene action. A successful request does not mean an object is already driven by its value.

Start with the temperature example and known values 25, 79, 80 and 85. Then connect HTTP, polling or WebSocket as supported by your deployment.

Connection sequence

Define each item's name, type, unit and update frequency. Select or configure a supported project connection. Inspect returned values, timestamps and quality before binding UI or Graph. Configure response paths and field mappings for charts; use the current object's stable identifier for scene actions.

Test normal values, threshold boundaries, missing values, disconnection and reconnection. Label replayed, simulated and live data distinctly. Do not present a stale value as a fresh reading.

Connection errors require checking the address, HTTPS, origin permissions and service availability. Empty output requires checking response paths and types. If the indicator updates but the scene does not, check the action target. Keep long-lived credentials out of shared browser projects; use supported platform service configuration.