Flow object structure
Basic Properties:
id: Unique identifier for the flowtitle: Name of the flow for display purposesenabled: Toggle to activate or deactivate the flow
Nodes: The building blocks of the flow, each with a specific purpose:
Data Source Nodes (
type: "data_source"): Define the input sources for dataInitiate Attributes Nodes (
type: "initiate_attributes"): Process and transform dataOutput Endpoint Nodes (
type: "output_endpoint"): Define where processed data is sent
Edges: Connect nodes together to define the flow of data
Node Types in Detail
Data Source Node
Acts as the entry point for data from devices
Contains a list of source device IDs to monitor
Example use: Collect data from vehicle trackers, temperature sensors, etc.
Initiate Attributes Node
Processes data by creating or modifying attributes
Uses expressions to transform raw data into meaningful metrics
Can reference other attributes in calculations
Example use: Convert analog signals to meaningful metrics (fuel level, temperature)
Output Endpoint Node
Defines the destination for processed data
Two main types:
Navixy Output: Sends data to the Navixy platform
MQTT Client Output: Sends data to external MQTT brokers
Examples
Customization for Manufacturers
This template can be customized for different manufacturers by:
Adjusting attribute calculations to match the specific sensor outputs and units of a particular manufacturer's devices
Adding manufacturer-specific attributes that may be unique to certain vehicles or devices
Configuring appropriate endpoints based on the manufacturer's preferred data handling systems
For example, if adapting for a specific truck manufacturer, you might:
Adjust fuel calculations based on their specific tank sizes and sensor characteristics
Add attributes for manufacturer-specific features (e.g., DEF levels, regeneration status)
Configure outputs to integrate with their fleet management systems
Last updated
Was this helpful?