You can write HTTP clients that remotely manage all your devices. Examples of such clients include web pages and programs written in a language such as Python or Java.

These clients send requests to the Remote Manager server using standard HTTP requests to retrieve data and remotely control your devices, as you can do from the Remote Manager web interface.

See ConnectCore Cloud Services web services for more information.

These web services allow you to schedule operations to devices en masse:

  • Monitor all your devices. Remotely retrieve and visualize data to determine your devices' health.

  • Update the device firmware. Update the firmware of one or more devices at the same time.

  • Access the file system. Interact with files on your devices and list, upload, download, or remove files.

  • Manage all your devices. Remotely configure and send specific requests to trigger processes in your devices.

For extended usage and reference information, see the Digi Remote Manager User Guide and Digi Remote Manager API Reference.

Remote Manager Configurations

Use Configurations to automatically manage device firmware, settings, and files. For example, you can automatically provision or update multiple devices with one common configuration which includes firmware, settings, and file systems. In addition to the common settings included in a configuration, you can provide site-specific settings to override one or more settings.

A Remote Manager configuration is a named set of device firmware, settings, and file system options. You use the configuration to automatically update multiple devices and to periodically scan devices to check for compliance with the configuration.

Groups are the organizational unit used to apply configurations:

  1. First, organize your devices into groups.

  2. Then, create configurations for the device types in the group.

You can create multiple configurations for a device type in a group, but only one configuration per device type can be enabled at one time:

  • If you move a device into a group that is managed by an active configuration for that device type, the device is immediately scanned for compliance.

  • If the device is not compliant and you have opted to automatically perform remedial action, the device is automatically updated to match the configuration.

  • If you move a device out of a group that is managed by an active configuration, the device is no longer managed.

Device type and reported firmware version are important values for Remote Manager configurations. Both are defined in the ConnectCore Cloud Services configuration file, cccs.conf. See Configure ConnectCore Cloud Services.

For more information on how to customize ConnectCore Cloud Services configuration, see Set CCCS configuration.

Follow these steps to manage your configurations:

  1. Log in to your Remote Manager account (https://remotemanager.digi.com).

  2. Select Device Management > Configurations on the left bar.

For extended usage and reference information, see the Digi Remote Manager User Guide and Digi Remote Manager API Reference.

Device service status

A device can be In service or In maintenance:

  • When a device is In service, in business hours, Remote Manager is not allowed to perform maintenance tasks on the device.

  • When a device is In maintenance, outside business hours, Remote Manager is allowed to perform maintenance tasks on the device.

See Set maintenance state to change the service status of your device.

The device service status on Digi Remote Manager is used for the application of configurations and the execution of automations:

  • Configurations: If a configuration scan is scheduled but the device is not in its maintenance window, the configuration scan is skipped. When the device enters again in maintenance, the configuration scan starts.

  • Automations: You can trigger automation when a device enters in its maintenance window and configure how to proceed depending on the device service status.

When creating a configuration or an automation, the option Maintenance Window Handling handles the behavior depending on its value:

  • Reject: The process fails at the start if any device is outside of its maintenance window.

  • Allow: The process ignores whether a device is outside its maintenance window.

  • Cancel: The proces fails during any step if a device transitions out of its maintenance window.

For extended usage and reference information, see the Digi Remote Manager User Guide and Digi Remote Manager API Reference.