The Devices page in JFrog Connect shows a list of devices and takes you on a deep dive into the device you choose. You can edit device details, get logs, and send commands to the device.

List of Devices

To view a list of devices and details about each device, go to the Devices page. The devices appearing in the list are according to the passive filter set at the top. If you do not see the device you are looking for, you can try the following:

• Change the passive filter.

• Page through the list using the arrows below the list.

• Use the Search bar to search by ID, name, group, application, tag, description, or MAC address.

Device Details

To drill down into the detailed device information, click a device in the table of devices and a side panel will appear. The side panel shows information about the device and in some cases, enables you to edit information or run commands:

• General Details: Shows ID, Name, Group, Last Seen, Location, Description, Update Trigger, Agent Version, Registration Time (UTC), and the Device-Project Pairing Token ID. If you click Edit, you can edit some of these.

• Technical Details: Shows a list of the IP Address, Hostname, OS, Node Name, Kernel Release, Kernel Version, Hardware, System Information, and MAC Addresses.

• Monitoring Information: Lists the processes monitored and shows basic parameters such as CPU, RAM, and disk space used on the device.

• Log Details: Provides information about the Update History.

• Application Details: Enables you to configure a new application on the device or edit an existing one.

• Alerts: Shows a shortlist of the latest alerts. You can also click Alerts and go to the full list.

• Commands: Run commands directly on the device.

Edit Device Details

You can change some of the general configuration settings of the device. In General Details, click Edit.

• Name: Change the name of the device.

• Group: Choose a group name from the list. This will cause the device to belong to a different group.

• Description: Enter a brief description of the device or change the existing description.

• Update Trigger: This creates a flag that determines if the device is available to receive updates. When the trigger is On, the device cannot receive updates. The device can receive updates only when the switch is turned Off.

• Delete: See Delete a Device.

Location

Choose the method by which the device location is determined:

• Automatic Location: Google Maps geolocation determines the location of the device based on the device’s public IP address. The location could change if you refresh locations.

• Manual Location: The device location is the location that you enter manually in this field. Google Maps validates the location when you enter it, and then it will not change if you run a refresh.

Save

After making your edits to the General Details, click Save.

What’s Next?

Learn more about how to set alerts.

Removing a device completely from your fleet in JFrog Connect requires the following procedures:

1. Uninstall Connect Agent from Device

2. Delete Device from Connect Server

In both steps, which are described below, ensure that the device chosen is the device you intend to remove.

Step 1: Uninstall Connect Agent from Device

To remove the Connect Agent from the device, run the command below by physically accessing the device terminal or by using the Remote Commands feature from the Connect web UI.

systemctl disable upswift --now 2>/dev/null ; systemctl disable connect --now 2>/dev/null ; rm -rf /etc/upswift/ /etc/connect/ /etc/system/systemd/upswift.service /etc/system/systemd/connect.service 2>/dev/null ;

Step 2: Delete Device from Connect Server

To delete a device from the Connect server, do the following:

1. Go to Devices in the left navigation tree and ensure that the filter at the top is set correctly. Choose the device from the list of devices. If you do not see the device name in the list, enter the name in the Search box.

1. In General Details, review the information to ensure that this is the device you want to delete, and click Edit.

1. Click Delete. If you are sure that you want to delete this device, click Delete Device in the confirmation popup.

What’s Next?

Learn how to send remote commands to your IoT device.

JFrog Connect provides different methods for you to control the timing of software updates, including the following:

• Start a software deployment at a time that you specify in the deployment configuration.

• Block or allow software updates to a single device by setting the update trigger in the Connect UI.

• Use the Update Trigger API to create update windows and update blocking windows for device groups in your fleet.

Set Update Trigger

The Update Trigger creates a device-based server flag that determines whether or not the edge device is available for updates. The On status indicates that the device will not receive updates. In the Off status (Connect’s default), the device can receive updates.

To block updates to a specific device, do the following:

1. Go to Devices in the left sidebar and click a device in the table of devices. If the device you want does not appear in the table, use the search box to find it.

1. Scroll down to the General Details panel and click Edit.

1. Click Update Trigger and Save.

Create an Update Window

When you deploy OTA updates to edge devices, there may be time periods when it is inappropriate or risky to send new updates. If, for instance, your device is in use by the end-user, a new update at that time might interfere with the user experience. Using the Update Trigger API call, you can manage from within your application when the device can receive updates, and when it can’t.

After setting the update trigger, your device will not receive new updates until you or your application unsets the trigger. By setting and unsetting the trigger at various times, you can create update windows that allow updates only during specific periods of time.

Example Use Case

A sample use case is a fleet of kiosk screen devices that are in use throughout the day, but are not used during the night. When the app is out of use, it goes into standby mode and comes out of standby upon first use in the morning.

When the app comes out of standby, it uses the Update Trigger API call to set the update trigger to On, so that it will not receive updates. When it goes to sleep again, the app unsets the update trigger so that it can receive updates while in standby mode. In effect, this creates an update window in which updates are allowed, and a blocking window in which the device will not accept updates.

For this use case to work, the Update Trigger API call would be used in the code of the kiosk app.

What’s Next?

Learn how to set the update trigger in the Deploy Update API request in the Connect API Reference.