---
title: "Channel settings"
slug: "channelsettings"
updated: 2025-12-29T15:46:02Z
published: 2025-12-29T15:46:02Z
canonical: "document360.traceablelive.com/channelsettings"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://document360.traceablelive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Channel settings

## Channel settings

The **Channel Settings** section allows users to configure and manage probe channels for the device. This includes renaming probe name, setting minimum and maximum temperature ranges and viewing recalibration dates.

IMPORTANT!

To ensure that your channel settings are saved both on the web application and synced automatically with the device, make sure the device is connected to both Wi-Fi and Power during the process. Without these connections, the changes will only be saved on the web application.

![Image](https://cdn.document360.io/dfe4b53c-b7e1-4f35-a0d5-71d402b5aa27/Images/Documentation/image(151).png)

## Field Insights

### Accessing Channel Settings:

- Login into the TraceableLIVE® account.
- Select a device from the device list.
- From the Settings menu, navigate to Channel Settings.
- Select the desired probe channel to configure its settings.

### Renaming the Probes:

Click on edit icon to update the probe name.

### Setting Min/Max Temperature:

In the Min and Max temperature fields, enter the desired temperature range for the selected channel. Ensure the values are within the valid range (-50.00°C to 60.00°C for temperature). When you are finished making changes, tap the **Update** button.

---

## Confirming Changes to Alarm Thresholds

If any Low Alarm or High Alarm value is modified, a confirmation window appears. ![Image](https://cdn.document360.io/dfe4b53c-b7e1-4f35-a0d5-71d402b5aa27/Images/Documentation/image(147).png)

This window will display:

- The **Channel Name**
- The **Old Min (Low Alarm) value**
- The **New Min value**
- The **Old Max (High Alarm) value**
- The **New Max value**

To **proceed**, do the following:

1. Review the **old** and **new** values shown for accuracy.
2. Enter a mandatory **Reason for Change** describing why the alarm range is being updated.
3. Select **Save Changes** to confirm and apply the new alarm settings.
4. Select **Cancel** if you do not want to proceed with the modification.

---

## Viewing Alarm Change History

![Image](https://cdn.document360.io/dfe4b53c-b7e1-4f35-a0d5-71d402b5aa27/Images/Documentation/image(152).png)

You may view the historical changes made to any channel’s Low or High Alarm settings. To do this:

1. Select **View Alarm History** section.

![Image](https://cdn.document360.io/dfe4b53c-b7e1-4f35-a0d5-71d402b5aa27/Images/Documentation/image(153).png)

1. A table will appear showing all previously modified alarm ranges for each channel, including:
  - Channel Name
  - Old Min Alarm
  - New Min Alarm
  - Old Max Alarm
  - New Max Alarm
  - Unit of Measure
  - Modified By / Modified At
  - Reason for Change

To view the full reason text, select the corresponding **view** icon in the **Reason** column. A separate pop-up will display the complete entered reason.

![Image](https://cdn.document360.io/dfe4b53c-b7e1-4f35-a0d5-71d402b5aa27/Images/Documentation/image(154).png)

---

### Viewing Probe Information:

Under the channel settings, you can view additional details, such as:

- Channel ID: The unique identifier for the channel.
- Factor: The measured factor, typically temperature.
- Probe Number: Indicates the connected probe number.
- Recalibration Date: Displays when the probe is due for recalibration.

---

NOTE

- After making the necessary changes, click **Update** to save all the configurations for the selected channel.
- Wait for 15 seconds to sync the updated settings to the device.
- After 15 seconds, check the updated fields for a green tick mark, indicating that the settings have been successfully updated.
- If a red error icon is displayed, ensure the device is connected to **Wi-Fi** and **Power**, and try updating the settings again.