Central management
Configure your device for Digi Remote Manager support
LR54 User Guide
54
3. Click
Central management
.
The Central management configuration window is displayed.
Digi Remote Manager support is enabled by default. To disable, toggle off
Enable central
management
.
4. (Optional) For
Service
, select either
Digi Remote Manager
or
Digi aView
. The default is
Digi
Remote Manager
.
5. (Optional) For
Management server
, type the URL for the central management server.
The default varies depending on firmware versions:
n
Firmware version 22.2.9.x and newer, the default is the edp12.devicecloud.com. This
server is for device-connectivity only, and uses enhanced security through certificate-
based communication. See
for further infomation.
n
Firmware prior to version 22.2.9.x, the default is the Digi Remote Manager server,
.
6. (Optional) For
Management port
, type the destination port for the remote cloud services
connection. The default is
3199
.
7.
Firmware server
should normally be left at the default location.
8. (Optional) For
Speedtest server
, type the name or IP address of the server to use to test the
speed of the device's internet connection(s).
9. (Optional) For
Retry interval
, type the amount of time that the LR54 device should wait before
reattempting to connect to remote cloud services after being disconnected. The default is 30
seconds.
Allowed values are any number of hours, minutes, or seconds, and take the format
number
{
h|m|s
}.
For example, to set
Retry interval
to ten minutes, enter
10m
or
600s
.
10. (Optional) For
Keep-alive interval
, type the amount of time that the LR54 device should wait
between sending keep-alive messages to remote cloud services when using a non-cellular
interface. The default is 60 seconds.
Allowed values are any number of hours, minutes, or seconds, and take the format
number
{
h|m|s
}.
For example, to set
Keep-alive interval
to ten minutes, enter
10m
or
600s
.
11. (Optional) For
Cellular keep-alive interval
, type the amount of time that the LR54 device
should wait between sending keep-alive messages to remote cloud services when using a