Line 90: |
Line 90: |
| <b>Azure IoT Hub</b> 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. | | <b>Azure IoT Hub</b> 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. |
| | | |
− | {{#ifeq: {{{modem}}} | 1 |
| + | By default, the Azure IoT list is empty. To add a new connection, enter a custom name and click the 'Add' button. |
− | The figure and table below provides explanations for Azure IoT Hub configuration parameters when selected 'Message Type' is <i>GSM values</i>.
| |
| | | |
− | [[File:Networking_rutos_manual_cloud_solutions_azure_iot_hub_modem_1.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_cloud_solutions_azure_iot_hub_add.png|border|class=tlt-border]] |
| + | |
| + | ===Modify Azure IoTHub=== |
| + | |
| + | [[File:Networking_rutos_manual_cloud_solutions_azure_iot_hub_modify.png|border|class=tlt-border]] |
| | | |
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 102: |
Line 105: |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Enable Azure IoT Hub monitoring</td> | + | <td>Enable</td> |
− | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | + | <td>off {{!}} on; default: <b>off</b></td> |
− | <td>Turns the Azure IoT Hub service on or off.</td> | + | <td>Enable Azure IoT service.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Connection string</td> | + | <td>Name</td> |
| <td>string; default: <b>none</b></td> | | <td>string; default: <b>none</b></td> |
− | <td>Unique connection string a.k.a. server address provided by the Azure Iot Hub service.</td> | + | <td>Connection name.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Message Type</td> | + | <td>Enable Direct Methods</td> |
− | <td>GSM values <nowiki>|</nowiki> MQTT messages; default: <b>MQTT messages</b></td> | + | <td>off {{!}} <span style="color:red">on</span>; default: <b>off</b></td> |
− | <td>Values that are to be sent to the Azure server.</td> | + | <td>Enable Direct Method feature set.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Message sending interval (sec.)</td> | + | <td><span style="color:red">Device Model ID</span></td> |
− | <td>integer; default: <b>300</b></td> | + | <td>string; default: <b>dtmi:Teltonika:genericDevice;1</b></td> |
− | <td>Device data sending frequency in seconds. Minimum value is 10 s.</td> | + | <td>Model ID of the Digital Twins Definition Language.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Mobile Interface</td> | + | <td>Connection type</td> |
− | <td>mobile interface; default: <b>mobs1a1</b></td> | + | <td>Shared Access Signature (SAS) key {{!}} <span style="color:blue">Device Provisioning Service (DPS)</span>; default: <b>Shared Access Signature (SAS) key</b></td> |
− | <td>Interface name for which IP address and sent/received bytes should be selected.</td> | + | <td>Connection type to an existing IoT Hub.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>GSM Values</td> | + | <td>Connection String</td> |
− | <td>IMSI <nowiki>|</nowiki> IP Address <nowiki>|</nowiki> RSRP <nowiki>|</nowiki> ICCID {{#ifeq:{{{series}}}|TRB5||<nowiki>|</nowiki> Bytes received }}<nowiki>|</nowiki> Cell ID <nowiki>|</nowiki> RSCP <nowiki>|</nowiki> PIN state <nowiki>|</nowiki> Manufacturer <nowiki>|</nowiki>{{#ifeq:{{{series}}}|TRB5|| Bytes sent <nowiki>|</nowiki>}} RSRQ <nowiki>|</nowiki> Revision number <nowiki>|</nowiki> Serial number <nowiki>|</nowiki> ECIO <nowiki>|</nowiki> SINR <nowiki>|</nowiki>Data carrier type <nowiki>|</nowiki> Network link state <nowiki>|</nowiki> Operator <nowiki>|</nowiki> PIN count <nowiki>|</nowiki> Signal level <nowiki>|</nowiki> Model <nowiki>|</nowiki> Connection state <nowiki>|</nowiki> Temperature <nowiki>|</nowiki> IMEI <nowiki>|</nowiki> SIM card state <nowiki>|</nowiki> Operator number; default: <b>none</b></td> | + | <td>string; default: <b>none</b></td> |
− | <td>Selects the mobile connection values that to be sent to the Azure IoT Hub service.</td> | + | <td>Connection string based on primary key used in API calls which allows device to communicate with IoT Hub.</td> |
| </tr> | | </tr> |
− | </table>|}}The figure and table below provides explanations for Azure IoT Hub configuration parameters{{#ifeq:{{{modem}}}|1| when selected 'Message Type' is <i>MQTT messages</i>|}}.
| |
− |
| |
− | [[File:Networking_rutos_manual_cloud_solutions_azure_iot_hub_modem_0_v2.png|border|class=tlt-border]]
| |
− |
| |
− | <table class="nd-mantable">
| |
| <tr> | | <tr> |
− | <th>Field</th> | + | <td><span style="color:blue">ID Scope</span></td> |
− | <th>Value</th>
| + | <td>string; default: <b>none</b></td> |
− | <th>Description</th>
| + | <td>Unique 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.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Enable Azure IoT Hub monitoring</td> | + | <td><span style="color:blue">Registration ID</span></td> |
− | <td>off | on; default: <b>off</b></td>
| |
− | <td>Turns the Azure IoT Hub service on or off.</td>
| |
− | </tr>
| |
− | <tr>
| |
− | <td>Connection string</td>
| |
| <td>string; default: <b>none</b></td> | | <td>string; default: <b>none</b></td> |
− | <td>Unique connection string a.k.a. server address provided by the Azure Iot Hub service.</td> | + | <td>The registration ID is used to uniquely identify a device registration with the Device Provisioning Service.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Message Type</td> | + | <td><span style="color:blue">Global Device Endpoint</span></td> |
− | <td>{{#ifeq:{{{modem}}}|1|GSM values <nowiki>|</nowiki>|}} MQTT messages; default: <b>MQTT messages</b></td> | + | <td>string; default: <b>global.azure-devices-provisioning.net</b></td> |
− | <td>Values that are to be sent to the Azure server.</td> | + | <td>Destination for messages sent by IoT devices to the Azure IoT Hub.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>MQTT Host</td> | + | <td><span style="color:blue">Attestation mechanism</span></td> |
− | <td>ip | host; default: <b>none</b></td> | + | <td><span style="color:brown">X.509 certificates</span> {{!}} <span style="color:orange">Symmetric Key</span>; default: <b>X.509 certificates</b></td> |
− | <td>MQTT broker's IP address or hostname.</td> | + | <td>Method used to confirm a device's identity in Device Provisioning Service.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>MQTT Port</td> | + | <td><span style="color:brown">X.509 Certificate</span></td> |
− | <td>integer [0..65535]; default: <b>none</b></td>
| + | <td>-interactive button; default: <b></b></td> |
− | <td>MQTT broker's IP port number.</td>
| + | <td>Upload the "leaf" certificate file.</td> |
− | </tr>
| |
− | <tr>
| |
− | <td>Topic</td>
| |
− | <td>string; default: <b>none</b></td>
| |
− | <td>MQTT topic to be used for publishing the data.</td>
| |
− | </tr>
| |
− | <tr>
| |
− | <td>Username</td>
| |
− | <td>string; default: <b>none</b></td> | |
− | <td>Username used for authentication to the MQTT broker.</td> | |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td>Require password</td>
| + | <td><span style="color:brown">X.509 Private Key</span></td> |
− | <td><span style="color:red">on</span> | off; default: <b>off</b></td> | + | <td>-interactive button; default: <b></b></td> |
− | <td>Enables password field.</td> | + | <td>Upload the "leaf" key file.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
− | <td><span style="color:red">Password</span></td> | + | <td><span style="color:orange">Symmetric Key</span></td> |
| <td>string; default: <b>none</b></td> | | <td>string; default: <b>none</b></td> |
− | <td>Password used for authentication to the MQTT broker.</td> | + | <td>The the derived device key from the DPS Primary Key.</td> |
| </tr> | | </tr> |
| </table> | | </table> |