58
edits
Changes
RMS Product Change Notifications (view source)
Revision as of 10:37, 13 February 2023
, 10:37, 13 February 2023no edit summary
__TOC__
__TOC__
==2023.02.27 Changes to adding RMS devices==
On February 27th, 2023 Teltonika's '''[[RMS|Remote Management System]]''' ('''[[RMS]]''') will receive an update that will change how Teltonika devices are added to RMS.
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |
1. How devices are validated in the platform the first time they connect to an RMS Company.<br>
2. How devices are added via RMS UI.<br>
3. How devices are added via RMS API.<br>
4. Devices will not be able to be added to RMS via Android and iOS applications. '''Important''': The ability to add devices via Android and iOS applications will be reintroduced with future application updates.
|-
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 908px; text-align: left; background: white;" |
'''Summary''':<br>
* Teltonika device must have a "First login" done, i.e. a WebUI login and password change must have been made.<br>
* RMS will ask for the device's password before the device can be added.
-----
'''Extended description''':<br><br>
1. An added device must have already done a "First login", meaning the default password was changed after a successful login. This check will be done the first time a device with active RMS Service attempts a connection to RMS after being registered to an RMS company. After this validation, subsequent reconnects to RMS while the device is in the same company will not trigger any additional validations.
'''2.1. Adding singular devices via RMS UI'''<br>
'''Today:'''<br>
* For RUT/TCR devices - You must input the [Serial number] and [MAC address].
* For TRB devices - You must input the [Serial number] and [IMEI].
'''After these changes:'''<br>
* For RUT/TCR devices - You must input the [Serial number], [MAC address] and the '''[Device's current password]''' (of the "admin" user)
* For TRB devices - You must input the [Serial number], [IMEI], and the '''[Device's current password]''' (of the "admin" user).<br><br>
'''2.2. Adding devices via CSV file'''<br>
In order to add a device to RMS using a CSV file, the file must contain the following columns of information:<br>
'''Today:'''<br>
* Serial number
* MAC address (or IMEI when adding TRB devices)
* Name (optional)
'''After these changes:'''<br>
* Serial number
* MAC address (or IMEI when adding TRB devices)
* '''Password'''
* Name (optional)
----
3. Adding a device through the RMS API will require additional information in the request body of the API call. <br>
For example, the request body for a RUT/TCR device would look like:<br>
'''Today:''' <br>
{
"data": [
{
"company_id": 12345,
"device_series": "rut",
"mac": "00:11:22:33:44:55",
"serial": "0123456789",
"name": "New device",
"auto_credit_enable": true
}
]
}
'''After these changes:'''<br>
{
"data": [
{
"company_id": 12345,
"device_series": "rut",
"mac": "00:11:22:33:44:55",
"serial": "0123456789",
"name": "New device",
"auto_credit_enable": true,
"password_confirmation": "Password123"
}
]
}
Meanwhile, the request body for a TRB device would look like:<br>
'''Today:'''<br>
{
"data": [
{
"company_id": 12345,
"device_series": "trb",
"imei": "123456789012345",
"serial": "0123456789",
"name": "New device",
"auto_credit_enable": true
}
]
}
'''After these changes:'''<br>
{
"data": [
{
"company_id": 12345,
"device_series": "trb",
"imei": "123456789012345",
"serial": "0123456789",
"name": "New device",
"auto_credit_enable": true,
"password_confirmation": "Password123"
}
]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |RMS system changes
|-
| style="text-align: left; background: white;" |Change implementation date
| colspan="2" style="text-align: left; background: white;" |February 27th, 2023
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |1. Any automatic RMS device integration processes will need to be changed to accompany these changes.<br>2. Any currently created CSV files ready for upload will need to be changed according to the new format.
|-
|-
| style="width: 221px; text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="width: 908px; text-align: left; background: white;" |Please contact your sales representative concerning any issues in regard to these changes.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification, Teltonika will presume that the fact of this change has been acknowledged and can implement the change as indicated above.
|-
|}
==2020.09.03 Multiple changes==
==2020.09.03 Multiple changes==
