Device Profiles

Device profiles let you centrally define and manage common settings for a group of similar HMI Devices — transport protocol, queue, alarm rules, and provisioning strategy. Instead of configuring each HMI Device individually, you define the profile once and assign it to as many HMI Devices as needed.

1. Navigate to Profiles → Device profiles.
2. Click + and select Create new device profile.
3. Enter a Name (the only required field).
4. Optionally configure the queue, image, description, transport type, and provisioning strategy.
5. Click Add.

1. Click the profile name and the pencil icon.
2. Update the desired settings across any tab.
3. Click Apply changes.

Click the trash icon next to a non-default profile and confirm deletion.

Clicking a profile opens a details panel with the following tabs:

Tab	Contents
Details	Profile name, queue, image, and description
Alarm Rules	Conditions, severity levels, and actions applied to all HMI Devices in this profile
Audit Log	History of user actions performed on this profile

The transport type determines how HMI Devices in this profile communicate with iRis Cloud. See How to Connect Your HMI Device for protocol-specific connection guides.

By default, all messages use the main queue. Assign a custom queue to isolate high-priority HMI Devices (e.g., fire alarms) from high-volume ones (e.g., water meters), or to apply different submit and processing strategies.

Define conditions that apply to all HMI Devices in this profile — for example, trigger a Critical alarm when temperature exceeds 40 °C. Rules defined here are shared across every HMI Device using the profile. See Alarm Rules.

The Device provisioning tab controls automatic registration of HMI Devices on their first connection. iRis Cloud does not use it — HMI Devices are created one at a time with an access token and license code (see Create a HMI Device), so leave the provisioning strategy at Disabled.

Editing a profile’s Queue or Alarm Rules immediately affects every HMI Device already assigned to that profile — there’s no need to touch individual HMI Devices. This is the main advantage of configuring these settings at the profile level instead of per HMI Device.

Moving a HMI Device to a different profile (in Edit a HMI Device) applies that profile’s queue and alarm rules going forward — it does not retroactively change alarms already generated under the previous profile.

Symptom	Cause	Fix
HMI Device can’t connect after switching its profile	New profile uses a different transport type than the HMI Device’s current credentials support	Issue new, compatible credentials for the HMI Device
Alarm rule doesn’t seem to run	It was added on the HMI Device instead of the profile (or vice versa)	Confirm which level the rule was created at — profile-level rules apply to every HMI Device on that profile, HMI Device-level rules apply only to that one HMI Device
Custom queue isn’t selectable when editing a profile	The queue hasn’t been created yet	Custom queues must be configured by a System Administrator before they can be assigned to a profile

• HMI Devices — every HMI Device is assigned exactly one profile, inheriting its transport, queue, and alarm rules
• Alarm Rules — shared logic applied across every HMI Device using the profile
• REST API — query, create, and manage device profiles programmatically