RUT200 Cloud Solutions

Wiki mirrorView source
The information in this page is updated in accordance with firmware version RUT2M_R_00.07.22.1.

Summary

The Cloud Solutions section is used to configure how the device will connect to certain cloud management systems.
This chapter of the user manual provides an overview of the Cloud Solutions page for RUT200 devices.
Note: Each Cloud Solutions service, except RMS, is additional software that can be installed from the System → Package Manager page.

RMS

RMS (Remote Management System) is a cloud system designed by Teltonika and intended for remote monitoring and management of Teltonika-Networks products.
In order to add a device(s) to RMS, get yourself acquainted by watching this instructional video and register an account by clicking here. Each unique device receives a free month-long RMS license when added to RMS for the first time.
The figure below is a screenshot of the RMS section taken from a device which has been connected to RMS:
FieldValueDescriptionProxy settingsValueDescription
Connection typeEnabled | Standby | Disabled; default: EnabledDefines how the device will connect to RMS:
  • Enabled - RMS functionality is always on. When disconnected from RMS, the device will try connecting every 2-5 minutes (every 2 minutes the first hour; then every 5 minutes). If the device is disconnected from RMS for 14 days, it will go into Standby mode. When trying to connect to rms without internet connection, the router will try to reestablish connection every 10 seconds.
  • Standby - The device tries to establish a connection with the server infrequently (6 hours in-between attempts). This is done in order to reduce mobile traffic. In order to start using RMS, user intervention is not necessary from the device's side. Worst case scenario - RMS connection will be established 6 hours after the device was added to RMS.
  • Disabled - RMS functionality is completely disabled; therefore, no connection attempts are made. In order to start using RMS, the user must enable the service on the device's side.
Hostnamehost | ip; default: rms.teltonika.ltRMS server hostname. Unless you are hosting your own RMS server, you should leave the default value.
Portinteger [1..65535]; default: 15009RMS server port. Unless you are hosting your own RMS server, you should leave the default value.
Authentication codestring; default: noneAuthentication code provided by RMS after adding the device.
Enable proxyoff | on; default: offEnable RMS connection through proxy.
Proxy addressdomain names or IP addresses; default: noneSpecify proxy address.
Proxy SOCKS5 portinteger [1..65535]; default: 1080SOCKS5 proxy server port.
Use credentialsoff | on; default: offUse credentials for SOCKS5 proxy connection.
SOCKS5 usernamestring; default: noneSpecify username for SOCKS5 proxy connection.
SOCKS5 passwordstring; default: noneSpecify password for SOCKS5 proxy connection.
The RMS server waits for incoming connections. Since the device attempts to connect at a fixed interval, it may not connect instantly after you add it to RMS. While it is disconnected, you can check how much time is left until the next connection attempt in the Status section:
To speed up the process by initiating an immediate connection attempt, click the Connect button.
If a failure or unknown status occurs, there is an alternative to try to reconnect again, click the Reconnect button.
When the device is already connected a Reset button becomes visible. Use it to terminate the device's connection to RMS.
For more information on Teltonika Networks Remote Management System (RMS) refer to the RMS Manual or RMS FAQ pages.

Azure IoT Hub

Azure IoT Hub is Microsoft's ever-expanding set of cloud services to help your organization meet your business challenges. Azure IoT Hub is compatible with Teltonika Networks devices.
By default, the Azure IoT list is empty. To add a new connection, enter a custom name and click the 'Add' button.

Modify Azure IoTHub

FieldValueDescription
Enableoff | on; default: offEnable Azure IoT service.
Namestring; default: noneConnection name.
Enable Direct Methodsoff | on; default: offEnable Direct Method feature set.
Device Model IDstring; default: dtmi:Teltonika:genericDevice;1Model ID of the Digital Twins Definition Language.
Connection typeShared Access Signature (SAS) key | Device Provisioning Service (DPS); default: Shared Access Signature (SAS) keyConnection type to an existing IoT Hub.
Connection Stringstring; default: noneConnection string based on primary key used in API calls which allows device to communicate with IoT Hub.
ID Scopestring; default: noneUnique identifier that is assigned to an Azure IoT Hub during its creation and is used to uniquely identify the specific provisioning service the device will register through.
Registration IDstring; default: noneThe registration ID is used to uniquely identify a device registration with the Device Provisioning Service.
Global Device Endpointstring; default: global.azure-devices-provisioning.netDestination for messages sent by IoT devices to the Azure IoT Hub.
Attestation mechanismX.509 certificates | Symmetric Key; default: X.509 certificatesMethod used to confirm a device's identity in Device Provisioning Service.
Use certificate files from deviceoff | on; default: offChoose this option if you want to select certificate files from device. Certificate files can be generated here.
Store keys in TPMoff | on; default: onWhen enabled, keys will be stored in TPM2 secure storage if space is available. Note: this option is only available on devices with TPM support.
X.509 Certificate-interactive button; default: Upload the "leaf" certificate file.
X.509 Private Key-interactive button; default: Upload the "leaf" key file.
Symmetric Keystring; default: noneThe the derived device key from the DPS Primary Key.

Cloud of Things

The Cloud of Things is an IoT cloud platform which provides the possibility to remotely monitor, manage and control your connected devices and machines – plug-and-play, without extensive installation.
FieldValueDescription
Enableoff | on; default: offTurns the Cloud of Things service on or off.
Cloud of Things statusstate; default: -Cloud of Things status.
Server Addressip | host; default: noneCloud of Things server IP address or hostname.
Intervalinteger [0..32767]; default: nonePush connection interval in minutes.
Reset Auth- (interactive button)Resets authentication data so that device could be re-registered on the Cloud of Things Device Management platform.
Portinteger [1..65535]; default: 8883Cloud of Things server port.
QoSAt least once (1) | At most once (0) | Exactly once (2); default: At least once (1)Quality of Service.
Keepaliveinteger [0..2147483647]; default: 60Keepalive time in seconds.

Cumulocity

Cumulocity IoT is a cloud-based, real-time IoT management platform that's also compatible with Teltonika-Networks devices.
The figure and table below provide explanations for Cumulocity configuration parameters available on the device. For a detailed configuration guide, click here.
FieldValueDescription
Enableoff | on; default: offTurns the Cumulocity service on or off.
Use SSL/TLSoff | on; default: offTurn SSL/TLS protocol support on or off.
Server Addresshost; default: noneHostname of your Cumulocity server. It should match the Environment name from the Cumulocity registration.
For example: teltonika-networks.eu-latest.cumulocity.com
Intervalinteger; default: noneConnection push interval in minutes. This field defines how often the device will try to connect to the Cumulocity server.
Reset Auth- (interactive button)Resets authentication for this device. If you click this, you'll have to authorize this from Cumulocity dashboard before it can successfully connect to the server.
Portinteger [1..65535]; default: 8883Cumulocity server port.
QoSAt least once (1) | At most once (0) | Exactly once (2); default: At least once (1)Quality of Service.
Keepaliveinteger [0..2147483647]; default: 60Keepalive time in seconds.

ThingWorx

FieldValueDescription
Enableoff | on; default: offTurns the ThingWorx service on or off.
Server Addressip | host; default: noneThingworx server IP address or hostname.
Server Portinteger [0..65535]; default: noneThingworx server's port number.
Thing Namestring; default: noneThing name defined in ThingWorx CP.
Application Keystring; default: noneApplication key generated in ThingWorx CP.
Mobile Interfacenetwork interface; default: mob1s1a1Interface whose GSM parameters will be sent to the ThingWorx server for monitoring.

AWS IoT Core

AWS IoT Core is a utility meant to interact with Amazon Web Services cloud platform. It provides AWS IoT Core Jobs support and AWS Provisioning that lets the device be controlled from AWS IoT Core platform by using device's API.

AWS Job

To add new 'AWS job', press Add button and enter Thing's name:
After that you will be redirected to AWS jobs thing configuration:
FieldValueDescription
Enableoff | on; default: offTurns the thing instance on or off.
Thing's namestring; default: noneThing's name on AWS IoT Core platform.
Endpointdomain; default: noneAWS IoT Core platform endpoint used to determine AWS account to connect to.
Use certificate files from deviceoff | on; default: offChoose this option if you want to select certificate files from device. Certificate files can be generated here.
CA file.ca file; default: noneAWS CA certificate obtained from AWS IoT Core platform.
Provisioningprovisioning configuration; default: Basic provisioningAWS provisioning configuration to use. It can be configured in AWS provisiong page. If basic provisioning is used, Thing's certificate and private key must be uploaded.
Store keys in TPMoff | on; default: onWhen enabled, keys will be stored in TPM2 secure storage if space is available. Note: this option is only available on devices with TPM support.
Thing's certificate.crt file; default: noneThing's certificate obtained from AWS IoT Core platform.
Thing's private key.key file; default: noneThing's private key obtained from AWS IoT Core platform.
Portinteger [1..65535]; default: 8883MQTT port number.
QoSAt most once (0) | At least once (1); default: At least once (1)MQTT Quality of Service. Allowed values:
  • 0 - when we prefer that the message will not arrive at all rather than arrive twice
  • 1 - when we want the message to arrive at least once but don't care if it arrives twice (or more).
Keepaliveinteger [30..65535]; default: 120MQTT keepalive time in seconds.
Max loopsinteger [10..200]; default: 50MQTT max loops - during initial subscription to topics the service has to wait for a successful subscription acknowledgement. The service performs mosquitto loops to wait for the answer. This option determines how many loops can be performed while waiting for subscription acknowledgement.

AWS Provisioning

To add new 'AWS provisioning' template, press Add button and enter Template name:
After that you will be redirected to AWS provisioning configuration:
FieldValueDescription
Templatestring; default: Name of Fleet provisioning template in AWS service.
Fleet provisioning typeProvisioning by claim | Provisioning by trusted user; default: Provisioning by claim
Creation typeCreateKeysAndCertificate | CreateCertificateFromCsr; default: CreateKeysAndCertificateSpecifies the AWS API to be used for certificate creation.
Use certificate files from deviceoff | on; default: offChoose this option if you want to select certificate files from device. Certificate files can be generated here.
Store keys in TPMoff | on; default: onWhen enabled, keys will be stored in TPM2 secure storage if space is available. Note: this option is only available on devices with TPM support.
Provisioning claim certificate.crt file; default: noneProvisioning claim certificate
Provisioning claim private key.key file; default: noneProvisioning claim private key
Access keystring (Values of 20 symbols are accepted. Following characters are accepted: A-Z0-9); default: noneTrusted user's access key.
Secret keystring (Values of 40 symbols are accepted); default: noneTrusted user's secret key.
Parametersstring (Following characters are accepted: a-zA-Z0-9:%_-); default: noneParameters which will be sent along with the certificate creation request. They will be formatted as JSON values ("Key": "Value").