YuDash
  • Welcome
  • YuDash IoT Devices
    • LYNX User Manual
      • Terminals and Wiring
      • LYNX Configuration
      • Network Settings
      • LYNX Settings
        • Modbus RS485
        • Analog Inputs
        • Data Scaling
        • Advance Feature Settings
        • Cloud and Payload Settings
        • Ethernet Settings
        • Modbus TCP/IP
        • HTML Parser Settings
        • Digital Sensors Settings
    • ZENYX User Manual
      • Terminals and Wiring
      • ZENYX Configuration
      • Network Settings
      • ZENYX Settings
        • Modbus RS485
        • Analog Inputs
        • Data Scaling
        • Advance Feature Settings
        • Cloud and Payload Settings
        • Ethernet Settings
        • Modbus TCP/IP
    • QUBIX User Manual
    • ONYX User Manual
  • Device Configuration
    • Device Configuration
    • Device Features
      • Network
      • Modbus/RS485
        • Modbus Poll Tutorial
      • Modbus TCP/IP
      • Modbus Server
        • Analog to Modbus/RS485 Server (Slave)
        • Analog to Modbus/TCP-IP Server
      • Ethernet
      • Data Logging
  • Firmware
    • Firmware release notes
    • Firmware upgrade
  • YuDash JSON API
    • Modbus Settings
    • Analog Settings
    • Data Scale Settings
  • DEVICE TO CLOUD API
    • YuDash IIoT Stack
    • Cloud Protocols
      • MQTT
      • HTTP
      • FTP
      • SSL/TLS
    • Payload Formats
      • JSON Payloads
      • YuTGT: YuDash Text Generator
    • Network Connectivity
    • Industrial Protocols
      • Modbus
  • YuDash IoT Platform
    • YuReCon
  • Integration Guides
    • IoT Platform Integration
      • Ubidots
      • TagoIO
      • Losant
      • Datacake
      • Eagle.io
      • Boodskap
      • Statstream
      • Qubitro
      • Thingsboard
    • Industrial Instruments
      • Energy
        • SE EM6400NG+
        • Selec MFM376
        • L&T WL 4040
        • Entes MPR-46S
        • Selec EM4M
        • Secure Elite 100
        • Siemens Smart 7KT
        • Selec EM2M
      • Process Control
        • Selec FLEX2MV3 6AII
        • Selec MiBRX 2M PLC
        • Temp+Humidity XY-MD02
        • PPI AIMS 4/8X
    • Environment/Emission
      • Air & Water
      • Weather
    • Industrial PLCs
  • Use Cases
    • Environment
      • Ground Water Compliance
      • Continuous Emission Monitoring System (CEMS)
    • Smart Building
      • IoT based Building Monitoring Solution
      • Tenant Energy Sub-metering and Billing System
    • Asset Management
      • Centralized Monitoring System for Gas Plant OEM
Powered by GitBook
On this page
  • Selection of MQTT As Cloud Protocol in YuDash IoT Device
  • MQTT Credentials
  • MQTT with SSL/TLS secure layer
  1. DEVICE TO CLOUD API
  2. Cloud Protocols

MQTT

PreviousCloud ProtocolsNextHTTP

Last updated 9 months ago

MQTT is the most popular IoT cloud protocol. YuDash IoT device acts as MQTT client which sends data to various IoT platforms in a seamless manner. Two-way communication for receiving command from cloud is also available.

Following are the steps to use MQTT as cloud protocol.

Selection of MQTT As Cloud Protocol in YuDash IoT Device

MQTT Credentials

Following are the settings in LYNX to configure connection to MQTT server:

MQTT Setting
Description

MQTT Server (Broker)

The URL of MQTT broker is accessible on network. Alternately, unique IP address can be provided. This may be required for a local deployment.

MQTT Port

The IP port running MQTT server. Typically 1883

MQTT User name

Client user name for MQTT broker - Based on server, it may be blank or Access Tokens are used as user name.

MQTT Password

Client password for MQTT broker. Based on server, it may be blank or Access Tokens are given in password.

MQTT Client Name

Client name for MQTT broker. It may be simply blank is most cases, unless specified by server.

MQTT Publish Topic

The MQTT topic to publish data to. In many cases, it will contain and API name and may include unique serial number of device or variable.

MQTT Platform Name

MQTT Platform Name: Generic platform name. It is for information or display purpose only. It is not used in communication.

Depending on API and authentication mechanism in MQTT broker of IoT platform, some of entries may be blank.

Following is the example for MQTT integration with popular Tago.io IoT platform:

MQTT with SSL/TLS secure layer

YuDash IoT devices support SSL/TLS based secure communication. Please refer to documentation for enabling the security layer.

SSL/TLS for MQTT