NodeState

Processing is suspended by user action; the node exists but is not running.

Informational status — the node is healthy and has a non-alarm message to surface in the UI.

A warning-level condition the operator should see but no immediate intervention is required.

A severe condition — node may still be running but degraded; prompts attention.

A hard error condition — the node failed to execute, connect, or read.

The node is in a pairing / discovery handshake (e.g., a Zigbee device being joined).

Default idle state — the node exists and has nothing noteworthy to report.

The node is actively executing its work (reading a sensor, firing an executor, etc.).

The node just completed a successful execution; often a transient state visible briefly in the UI.

The node is in the middle of being deleted; shown briefly so clients can animate the removal.

The node was just created; shown briefly to allow the UI to fade it in.

The user has opened the node in the editor but has not yet submitted changes.

The user has submitted edits; the node will transition away once the server acknowledges.

A snapshot (historical time-series payload) arrived for this node; used to invalidate cached views on the client side so the next read pulls fresh data.

The caller lacks authorisation to view or mutate this node (missing/invalid API key).

The node is currently being edited by some client; used as a soft lock so concurrent editors can see a Someone else is editing this hint.

Returns a representation of an immutable list of all enum entries, in the order they're declared.

Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)

Returns an array containing the constants of this enum type, in the order they're declared.