Changes

no edit summary
Line 289: Line 289:  
     <tr>
 
     <tr>
 
       <td>Format type</td>
 
       <td>Format type</td>
       <td>Json {{!}} <span style="color:red">custom</span>; default: <b>Json</b></td>
+
       <td>JSON {{!}} <span style="color:red">custom</span>; default: <b>JSON</b></td>
 
       <td>Data collection objects formatting.</td>
 
       <td>Data collection objects formatting.</td>
 
     </tr>
 
     </tr>
Line 337: Line 337:  
     <tr>
 
     <tr>
 
       <td>Type</td>
 
       <td>Type</td>
       <td>HTTP {{!}} <span style="color:red">MQTT</span>; default: <b>HTTP</b></td>
+
       <td>HTTP {{#ifeq:{{{MQTT}}}|1|{{!}} <span style="color:red">MQTT</span>}}; default: <b>HTTP</b></td>
 
       <td>Interval in seconds for collecting/sending data to destination.</td>
 
       <td>Interval in seconds for collecting/sending data to destination.</td>
 
     </tr>
 
     </tr>
Line 355: Line 355:  
       <td>Enables the use of TLS certificates.</td>
 
       <td>Enables the use of TLS certificates.</td>
 
     </tr>  
 
     </tr>  
      
+
     {{#ifeq:{{{MQTT}}}|1|
 
     <tr>
 
     <tr>
 
         <td><span style="color:red">Port</span></td>
 
         <td><span style="color:red">Port</span></td>
Line 383: Line 383:  
* 1 - when we want the message to arrive at least once but don't care if it arrives twice (or more),
 
* 1 - when we want the message to arrive at least once but don't care if it arrives twice (or more),
 
* 2 - when we want the message to arrive exactly once. A higher QoS value means a slower transfer.</td>
 
* 2 - when we want the message to arrive exactly once. A higher QoS value means a slower transfer.</td>
     </tr>
+
     </tr>}}
 
     <tr>
 
     <tr>
 
       <td>Enable secure connection</td>
 
       <td>Enable secure connection</td>
Line 390: Line 390:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td><span style="color:blue">On:</span> TLS type</td>
+
       <td>Allow insecure connection</td>
      <td>Certificate based {{!}} Pre-shared key based; default: '''Certificate based'''</td>
  −
      <td>Select type of TLS.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Certificate based: Allow insecure connection</td>
   
       <td>off {{!}} on; default: '''off'''</td>
 
       <td>off {{!}} on; default: '''off'''</td>
 
       <td>Allow not verifying server authentication.</td>
 
       <td>Allow not verifying server authentication.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>Certificate based: Certificate files from device</td>
+
       <td>Certificate files from device</td>
 
       <td>off {{!}} on; default: '''off'''</td>
 
       <td>off {{!}} on; default: '''off'''</td>
 
       <td>Specify where the certificates will be used from.</td>
 
       <td>Specify where the certificates will be used from.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>Certificate based: CA File</td>
+
       <td>Certificate authority file</td>
 
       <td>.ca file; default: <b>none</b></td>
 
       <td>.ca file; default: <b>none</b></td>
 
       <td>'''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.</td>
 
       <td>'''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.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
     <td>Certificate based: Client Certificate</td>
+
     <td>Client Certificate</td>
 
         <td>.crt file; default: <b>none</b></td>
 
         <td>.crt file; default: <b>none</b></td>
 
         <td>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.</td>
 
         <td>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.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
     <td>Certificate based: Client Private Key</td>
+
     <td>Client Private Keyfile</td>
 
         <td>.key file; default: <b>none</b></td>
 
         <td>.key file; default: <b>none</b></td>
 
         <td>File containing private key for this client. This file needs to be not encrypted.</td>
 
         <td>File containing private key for this client. This file needs to be not encrypted.</td>
     </tr>
+
     </tr>{{#ifeq:{{{MQTT}}}|1|
    <tr>
  −
      <td>Pre-shared key based: Pre-Shared-Key</td>
  −
      <td>string; default: <b>none</b></td>
  −
      <td>The pre-shared-key in hex format with no leading "0x".</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Pre-shared key based: Identity</td>
  −
      <td>string; default: <b>none</b></td>
  −
      <td>The identity of this client. May be used as the username depending on the server settings.</td>
  −
    </tr>
   
     <tr>
 
     <tr>
 
       <td>Use credentials</td>
 
       <td>Use credentials</td>
Line 443: Line 428:  
       <td>string; default: <b>none</b></td>
 
       <td>string; default: <b>none</b></td>
 
       <td>Password used in authentication.</td>
 
       <td>Password used in authentication.</td>
     </tr>
+
     </tr>}}
 
      
 
      
 
</table>
 
</table>
    
[[Category:{{{name}}} Services section]]
 
[[Category:{{{name}}} Services section]]

Navigation menu