Device profile detail management
Device Profile Detail Management
The Device Profile Detail screen can be accessed by selecting the relevant profile from the Device Profiles list. This screen is used to centrally review the selected profile's basic information, data model, remote command structures, and technical configurations.
In this area, profile information can be viewed, edited, managed, or deleted if it is no longer needed. Since changes made to a profile may affect the operation of devices assigned to that profile, modification actions should be performed carefully.
General Overview
The General Overview tab serves as the main summary page of the device profile. Profile name, transport protocol, payload format, assigned device count, description, technical limits, tags, and date information can all be reviewed from this section.
Figure 1. Basic profile information.
Figure 2. Description and technical properties.
Figure 3. Tags and date information.
Basic Information
To understand the purpose of a profile, the basic information should be reviewed first. The profile name, transport protocol, and payload format indicate the type of devices for which the profile was designed.
- Profile Name: The unique identifier of the profile within the platform.
- Transport: Indicates the protocol used by devices to communicate with the platform.
- Payload Type: Specifies the format in which incoming device data is processed.
- Device Count: Displays the number of devices assigned to this profile.
Technical Properties
The Technical Properties section is used to review the profile's data transmission limits and timing tolerances. This area should be examined when troubleshooting payload size restrictions or time synchronization issues.
Tags and Date Information
Tags are used to group and filter profiles throughout the platform. Date information allows administrators to track when the profile was created and when it was last updated.
Information — The General Overview tab is the first summary section that should be reviewed before performing any operation on the profile.
Telemetry
The Telemetry tab in the Device Profile Detail screen is used to define the structure of telemetry data sent by devices assigned to the profile. Telemetry keys, key descriptions, and data structures can be viewed from this screen.
When telemetry definitions are created for a device profile, all devices assigned to that profile use a common data model. This ensures data standardization across the platform and allows dashboards, alarms, reporting, and analytics processes to operate more consistently.
The Telemetry tab can be accessed from the Device Profile Detail screen by selecting the relevant profile from the Device Profiles list. This section is used to understand what data devices are expected to send and to verify the configured data structure.
Figure 1. Screen displaying telemetry keys defined for the device profile.
Figure 2. Section displaying telemetry keys and descriptions.
Telemetry Keys
The Telemetry Keys section is used to define telemetry keys associated with the device profile. If no telemetry keys have been configured at the profile level, the system displays an informational message.
Managing telemetry keys at the profile level is particularly beneficial in large-scale deployments, as it helps establish a consistent data model across all connected devices.
Telemetry (Key–Value)
This section is used to document the meaning of data sent by devices. Descriptive names and explanations can be provided for each telemetry key.
For example, energy meter values, temperature sensor readings, production data, or equipment status information can be documented here to help users interpret the data more easily.
Proper telemetry descriptions significantly improve dashboard design, alarm management, reporting processes, and data analysis activities.
Attributes
The Attributes tab in the Device Profile Detail screen is used to manage attribute definitions associated with the profile. Attributes are used to define device behavior, configuration settings, and static information that should be stored at the profile level.
After selecting a profile from the Device Profiles list, users can navigate to the Attributes tab to view, update, and manage profile-level attribute definitions.
While telemetry data represents continuously changing operational values, attributes are primarily used for device configuration parameters, descriptions, communication settings, and other static profile information.
Figure 1. Screen displaying attribute keys defined for the device profile.
Figure 2. Section displaying profile communication parameters.
Attribute Keys
The Attribute Keys section is used to display attribute definitions configured at the profile level. If no attributes have been defined for a profile, the system displays an informational message to the user.
Defining attributes at the profile level helps ensure that all devices assigned to the same profile operate with a consistent configuration standard, which is especially beneficial in large-scale deployments.
Communication Information
This section provides information about the communication technologies and data formats used by the device profile.
In the example shown, the profile uses the MQTT communication protocol and exchanges data in JSON format. Dashboards, integrations, and data processing services within the platform rely on this configuration.
When a device connects to the platform, the transport protocol and payload format used by the device are determined according to the profile configuration defined in this section.
RPC
The RPC tab in the Device Profile Detail screen is used to manage the remote command mechanism that enables bidirectional communication between the platform and connected devices.
Through the RPC (Remote Procedure Call) framework, commands can be sent to devices, device behavior can be controlled, and specific operations can be triggered remotely from the platform.
After selecting a profile from the Device Profiles list, users can navigate to the RPC tab to review the RPC methods and parameters defined for that profile.
Figure 1. Screen displaying RPC methods defined for the device profile.
Figure 2. Section displaying the RPC JSON configuration.
RPC Methods
RPC methods define functions that can be executed remotely on a device. Each method can accept specific parameters and is expected to complete within the configured timeout period.
In the example shown, the set_power_limit method is used to remotely modify the device's power limit. When this method is executed, thelimit_w parameter is provided.
The same mechanism can be used for operations such as restarting a device, changing operating modes, controlling relays, or updating production limits.
Parameter Management
Parameters and data types can be defined for each RPC method. This helps establish a standardized communication structure between the platform and the device.
Defining parameter schemas in advance helps prevent invalid data from being transmitted and improves the reliability and security of device management processes.
Raw JSON Configuration
RPC definitions are stored internally in JSON format. This structure includes the method name, parameter schemas, data types, and timeout values.
Developers and integration teams can review these JSON definitions to verify communication between the platform and connected devices when needed.
About RPC
The RPC mechanism allows the platform to send commands directly to devices. Unlike telemetry, where data flows from the device to the platform, RPC communication flows from the platform to the device.
RPC is commonly used in industrial automation, energy management, and remote device control scenarios, enabling operational processes to be managed from a centralized platform.
Configuration
The Configuration tab in the Device Profile Detail screen provides a consolidated view of all technical settings and communication definitions associated with the profile in a single JSON structure.
After selecting a profile from the Device Profiles list, users can navigate to the Configuration tab to review the complete profile configuration from a single screen.
This section is primarily used by integration teams, system administrators, and developers to validate profile settings and review configuration details.
Figure 1. Screen displaying the complete JSON configuration of the device profile.
Complete Configuration
This section displays all profile settings in JSON format. Profile name, communication protocol, payload format, telemetry topics, attribute definitions, and RPC methods are all included within the same configuration structure.
Users can review how the settings configured in other tabs are stored and represented by the system.
Configuration Content
The configuration file contains basic profile information, communication parameters, and topic definitions used for data exchange.
Telemetry publishing channels, attribute topics, and RPC method definitions are organized into separate sections within the JSON structure.
Integration Processes
This configuration can serve as a reference when integrating with external systems or developing new devices.
In particular, MQTT topic definitions and RPC methods can be verified from this screen while configuring MQTT clients and integrations.
Copy Configuration
The JSON configuration can be copied to the clipboard using theCopy option located in the upper-right corner of the configuration card.
This feature simplifies configuration sharing, migration to other environments, and technical review processes.
Information — The Configuration tab is not intended for creating new settings. Instead, it is used to review and validate all existing profile settings from a single location.