Device Types and Telemetry Flows

A Device Type is the authoritative data contract for all devices of that type. Open Device Types and select the linked name to see status, usage, active Flow, identifiers, metadata, timestamps, and the complete field catalog on one detail page. Editing, Flow creation or opening, parameter management, and deactivation are offered there according to permission. The page also links to the Device list with its Device-Type filter prepared.

The Device Type table shows the exact filtered result count, supports 25, 50, or 100 rows, and keeps search, status, and page size in the URL. Previous and Next traverse stable cursor pages. A successful edit reloads the current page or moves to its predecessor if the page became empty.

Define permitted fields on that detail page or directly from a storage-output inspector while building its telemetry Flow. A Device Type owns at most one Flow, and that Flow cannot be assigned to another Device Type.

For every field, define:

• an immutable technical key;
• name and description;
• Number, String, Boolean, or JSON type;
• an optional unit for Number fields;
• Current values, Timeseries, or both storage targets;
• Gauge, Counter, Status, or Event when Timeseries is selected.

JSON is current-only. Gauge and Counter require Number. After a released Flow or stored data references a field, its technical contract is protected. Storage targets may only be added. Fields are deprecated instead of deleted; their name and description remain editable.

Create and edit the Flow

Select Create Flow on a Device Type without a Flow, or Open Flow once it exists. The global Telemetry Flows view uses the same operation and asks for an available Device Type first. The Flow editor, manual test input, and template-copy form search Device Types on the server. Select Load more to retrieve each additional page instead of assuming that the first response is complete.

The global Flow table shows an exact filtered count and 25, 50, or 100 rows. Its search and page size remain in the URL, while in-session page history survives a switch to another Flow area. Previous and Next navigate stable pages. The Flow selector searches the server in batches of 50 and loads more only after Load more Flows is selected. Version history starts with 25 entries. Load older versions appends the next page without claiming an exact total; a failed continuation leaves all loaded versions available for retry.

The Studio has a block library, canvas, inspector, and diagnostics. Every V2 graph contains two permanent terminal nodes:

The block library always loads the complete built-in catalog. Released Custom blocks use server search and explicit 50-item pages; select Load more blocks for the next page. Fixtures and parameter values show exact filtered counts and 25, 50, or 100 rows. Script blocks, Flow templates, E-mail templates, and recipient bindings use the same counted table controls. Their immutable version histories load 25 entries at a time with an explicit older-page action and never present a partial loaded count as a total. A failed continuation keeps already loaded entries available for retry.

• Current values stores one latest value per Device and field.
• Timeseries stores every valid measurement point.

Their input ports are generated from the Device-Type field catalog. They can be moved but not deleted or duplicated. Select either output node to keep the canvas visible while editing the Device Type or adding a field in the inspector. A new field initially selects the clicked output as its storage target; select the other target as well when needed. Successful field changes refresh both output nodes in the current canvas. Save a new draft to persist that refreshed graph. Port schemas must match exactly. An unconnected prepared field is a warning. A field configured for both targets must connect both ports to the exact same block output.

Select any regular block to remove it with Delete node in the inspector; all of its connections are removed at the same time. The two storage nodes stay permanent. Raw Input exposes payload, connection data, message type, and the gateway array. Connect connectionData to Netmore Connection Data to use battery level, frame counter, RSSI, SNR, data rate, spreading factor, and frequency as Number values.

Use Focus mode for a near-fullscreen three-column workspace. Closing it with the button or Escape preserves the same unsaved graph state. Focus mode contains only the block library, canvas, and inspector; diagnostics and the test bench remain in the normal Studio view.

Test, release, and activate

Preview accepts a retained Raw row, fixture, or manual input. It uses the same engine and script sandbox as live processing, but writes no execution, current value, measurement, or Action job. The result separates planned Current-Value writes and Measurements and shows the normalized Netmore timestamp used as observedAt.

Release rechecks the current Device-Type contract and pins the field snapshots. Release alone does not process live data. Activation selects the released version used for new Raw messages; Raw rows stored before activation require an explicit replay. Parameters still resolve in the order Device, Device Type, Tenant, default; Device-Type Flow context now contains parameter overrides only.

Templates and Actions

V2 templates store field requirements by key, schema, unit, measurement type, and target without Device-Type UUIDs. Copying requires a target Device Type with compatible fields and creates its single independent Flow. Legacy V1 template versions are deprecated and read-only.

Send-Email remains an asynchronous Action. The former Save Measurement and Update Device Attribute blocks no longer exist; persistence is exclusively represented by the two system output nodes.

Template, script, recipient, and E-mail searches run on the server. Previous and Next move through counted tables; version-history controls append older entries. The Action pause control is a single Tenant setting and therefore has no list navigation.

Open Actions → Jobs & Dead Letters to investigate operational history. Flow and Organization selectors search the server, while separate status filters apply to Executions and Dead Letters. Each list loads 25 records and reports only how many are currently loaded. Load older keeps the fixed investigation anchor and every filter; Refresh clears both lists and starts at a new anchor. A failed continuation leaves the current evidence visible and can be retried with the same button. No exact total is claimed.