Back to changelog
    IoT Logic

    Enrich devices with data from other systems

    This release lets you enrich a device you've already added to a flow with data pushed from another system it reports to, without changing how that device already works.

    A new Software tab on the Data Source node makes this possible. It merges attributes pushed from an external system, for example a separate battery management system tracking the same vehicle, into the data stream of a device already selected in the node's Devices tab.

    Select at least one device in the Devices tab, then open the Software tab, set the connector type to HTTP, and save the flow to generate a push URL. Give the external system an API key to authenticate with, then define a primary key field and add one mapping row per device so incoming pushes reach the right one.

    Pushed fields merge into the mapped device's attribute history, creating a new attribute or updating an existing one, though speed, coordinates, heading, satellite count, and HDOP can never be overwritten this way. If a push's identifying value doesn't match any mapping, it's discarded silently with no error, so check Data Stream Analyzer if pushed data isn't showing up as expected.

    Open IoT Logic from Account settings, then open a flow's Data Source node to explore.

    Learn more in the documentation →

    Improvements

    • The node palette on the canvas is now grouped into four labeled sections, Start with, Process, Action, and End with, in the order you'd typically use them, replacing the previous flat list. Node tiles and canvas visuals are also refreshed for a cleaner look.
    • Device action and Webhook nodes now show a read-only Node ID in their configuration dialog, for example action_1a2b3c4d. Data Stream Analyzer surfaces each node's trigger status as a live attribute named after that ID, 0 when it hasn't fired and 1 when it has, useful for confirming a node executed or telling multiple Action or Webhook nodes apart in the same flow.