RUT241 Data to Server: Difference between revisions
Gytispieze (talk | contribs) (Created page with "{{Template: Networking_rutos_manual_data_to_server <!------------------------DEVICE-----------------------> | name = RUT241 | series = RUT2 <!----------------------SEP...") |
No edit summary |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
<!------------------------DEVICE-----------------------> | <!------------------------DEVICE-----------------------> | ||
| name = RUT241 | | name = RUT241 | ||
| series = | | series = RUT2M | ||
<!----------------------SEPARATORS---------------------> | <!----------------------SEPARATORS---------------------> | ||
| bluetooth = 0 | | bluetooth = 0 | ||
| wifi = 1 | | wifi = 1 | ||
| mobile = 1 | |||
}} | }} |
Revision as of 15:09, 9 April 2024
Main Page > RUT Routers > RUT241 > RUT241 Manual > RUT241 WebUI > RUT241 Services section > RUT241 Data to ServerThe information in this page is updated in accordance with firmware version RUT2M_R_00.07.10.
Summary
The Data to Server feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers.
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.
Data Senders
A Data Sender is an instance that gathers and periodically sends collected data to a specified server. The Data Senders list is empty by default so, in order to begin configuration you must add a new data sender first. To add a new data sender, click the 'Add' button.
After this you should be redirected to the newly added data sender's configuration page.
Sender Settings
Refer to the table below for descriptions on data sender configuration fields.
Note: these tables have coloring schemes to indicate which fields can be seen with different configuration.
General
Field | Value | Description |
---|---|---|
Name | string; default: none | Name of the data sender. Used for easier data senders management purposes only (optional). |
Type | Base | GSM | Lua script | Wifi scanner* | ; default: Base | Source of the data to be sent to server. |
Format type | Json | Custom; default: Json | Arranges the format of the sent JSON segment. |
Format string | string; default: none | Specifies custom format string. |
Empty value | string; default: N/A | A string which will be placed if any value cannot be received. |
Delimeter | string (Maximum length of value is 1 bytes); default: N/A | Specifies delimiters for multiple data segments. |
Segment count | integer [1..64]; default: 1 | Max segment count in one JSON string sent to server. |
Send as object | off | on; default: off | When turned on, sends JSON segment as object and not as an array element. |
Data filtering | All | Name | MAC address | Signal strength; default: All | If Data type: Wifi scanner. Choose which data this sender will send to server. |
Data period | Day | Week | Month; default: Day | If Data type: Mobile usage. Choose for which time period to send info from. |
Current | off | on; default: off | If Data type: Mobile usage. |
* This is additional software that can be installed from the System → Package Manager page.
Collection settings
Field | Value | Description |
---|---|---|
Enabled | off | on; default: on | Enables data to server collection instance. |
Format type | JSON | custom; default: JSON | Data collection objects formatting. |
Format string | Default: Instance name | Specifies custom format string |
Empty value | Default: N/A | A string which will be placed if any value cannot be received |
Period | Default: 60 | Interval in seconds for collecting/sending data to destination. |
Retry | off | on; default: off | In case of a failed attempt, retry to send the same data to destination later. |
Retry count | Default: 10 | Retry to send the same data N times |
Timeout | Default: 1 | Timeout in second between retry attempts |
Server configuration
Field | Value | Description |
---|---|---|
Type | HTTP ; default: HTTP | Interval in seconds for collecting/sending data to destination. |
Server address | Default: empty | Hostname or IP address of the broker to connect to. |
HTTP headers | Default: empty | Allows to add custom headers to the HTTP requests. |
Enable secure connection | on | off; default: off | Enables the use of TLS certificates. |
Enable secure connection | off | on; default: off | Enables the use of TLS certificates. |
Certificate files from device | off | on; default: off | Specify where the certificates will be used from. |
Certificate authority file | .ca file; default: none | Certificate authority is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate. |
Client Certificate | .crt file; default: none | Certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server. If client certificate is not needed, leave both client certificate and client key fields empty. |
Client Private Keyfile | .key file; default: none | File containing private key for this client. This file needs to be not encrypted. |