124
edits
Changes
no edit summary
{{Template:Networking_rutx_manual_fw_disclosure
{{Template:Networking_rutx_manual_fw_disclosure
| fw_version = RUTX_R_00.02.01.1
| fw_version = RUTX_R_00.02.01.1
4.1 Set connection type as a '''Device Provisioning Service (DPS)''';
4.1 Set connection type as a '''Device Provisioning Service (DPS)''';
4.2 Enter '''ID Scope''' of your DPS service page on Azure;
4.2 Enter '''ID Scope''' of your DPS service page on Azure;
4.3 Specify the '''Registration ID'''. Remember the "device-01" one? If you followed the Microsoft guide step by step, you need to enter "device-01" in the "Registration ID" field.
4.3 Specify the '''Registration ID'''. Remember the "device-01" one? If you followed the Microsoft guide step by step, you need to enter "device-01" in the "'''Registration ID'''" field.
4.4 Lastly, upload the certificate chain file and the private key file.
4.4 Lastly, upload the certificate chain file and the private key file.
A direct method refers to a process where an action is initiated from the Azure IoT Hub to a specific device identity. The receiving device executes certain actions and returns a response back to the Azure portal. Let's see how this works on our devices.
A direct method refers to a process where an action is initiated from the Azure IoT Hub to a specific device identity. The receiving device executes certain actions and returns a response back to the Azure portal. Let's see how this works on our devices.
By default, all configuration instances will have this option disabled. To enable it, navigate on the router WebUI to Services -> Cloud Solutions -> Azure IoT Hub and press the edit button on the specific instance. There, you will see the "Enable Direct Methods" button, which you need to press.
By default, all configuration instances will have this option disabled. To enable it, navigate on the router WebUI to '''Services -> Cloud Solutions -> Azure IoT Hub''' and press the edit button on the specific instance. There, you will see the "'''Enable Direct Methods'''" button, which you need to press.
[[File:Azure RutOSconf 19.png|border|class=tlt-border]]
[[File:Azure RutOSconf 19.png|border|class=tlt-border]]
[[File:Azure RutOSconf 22.1.png|border|class=tlt-border]]
[[File:Azure RutOSconf 22.1.png|border|class=tlt-border]]
After pressing the "Invoke Method" button, you will see the response from the device.
After pressing the "'''Invoke Method'''" button, you will see the response from the device.
[[File:Azure RutOSconf 21.png|border|class=tlt-border]]
[[File:Azure RutOSconf 21.png|border|class=tlt-border]]
The response you see is a standard response as specified in our API documentation.
The response you see is a standard response as specified in our API documentation.
To determine the appropriate payload and method to use, we provide an additional file currently called "teltonikaGenericDevice.json." This file is written in Digital Twin Definition Language (DTDL). It is similar to SNMP MIB documents by design, as it also describes device capabilities. In this file, you can see that it supports the api_call method, which accepts three values. The request body is optional, as some methods, such as the GET method, may not require it. INSERT FILES!
To determine the appropriate payload and method to use, we provide an additional file currently called "teltonikaGenericDevice.json." This file is written in Digital Twin Definition Language (DTDL). It is similar to SNMP MIB documents by design, as it also describes device capabilities. In this file, you can see that it supports the api_call method, which accepts three values. The request body is optional, as some methods, such as the GET method, may not require it. JSON files can be downloaded by pressing [[Media:Teltonika-dtmi-docs.zip|here]]
The IoT Explorer can be configured to parse DTDL files and display them to the user. Let's configure it:
The IoT Explorer can be configured to parse DTDL files and display them to the user. Let's configure it.
===IoT plug and Play configuration===
===IoT plug and Play configuration===