Page History

...

• Name
  • This is the friendly name of the MQTT Server used to easily identify it
• URL
  • This is the URL of the MQTT server.  Its format is as follows: [protocol]://[location]:[port].  Each of these are shown below
    • protocol - Either tcp or ssl
    • location - The server location.  e.g. localhost, myserver.chariot.io, mydomain.com, etc
    • port - The port the MQTT Server is listening on.  Generally this is 1883 if using TCP or 8883 if using SSL
• Server Set
  • The Set that this server is a member of.
• Username
  • The MQTT username to use in the MQTT connect packet.  This is required if the MQTT Server to connect to requires it.
• Password
  • The MQTT password to use in the MQTT connect packet.  This is required if the MQTT Server to connect to requires it.

TLS Properties

• Certificates
  • The server certificates to use if required.  These are generally only required when connecting using TLS and the MQTT server does not have a genuine certificate issued by a trusted certificate authority.
  • CA certificate must always end in 'ca.pem'
  • If using client side certificates (i.e. a public/private keypair and CA cert), make sure the following naming conventions are followed.
    
    • Edge/Device certificate must end in 'cert.pem'
    • Edge/Device private key must end in 'private.key'
• Password
  • A password associated with the certificate's private key.
• Hostname VerificationEnable TLS Hostname verificationThis configuration for TLS changed between MQTT Transmission v4.0.4 and v4.0.5. See this document for TLS configuration: Secure MQTT Communication (SSL/TLS)

Advanced Properties

• Client ID
  • Optional MQTT client ID to use.  If specified this will be used in the MQTT Engine connect packet when connecting to the server.  If left blank, a random client ID will be create of the form 'IgnitionTarget-xxxxxxxx-xxxx-xxxx
• Keep Alive
  • The MQTT client keep alive time (in seconds).
• Random Startup Delay
  • The Random Startup Delay in milliseconds of the form 'min-max' where min is the low end and max is the high end of the random range. e.g. '10-1000'
• Data Format Type
  • The format of the data to send. This should almost always be Protobuf encoding. The other options is JSON.

...